daemon.cjs · part 240

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-agent-host/dist/agent-host-daemon/dist/bin/daemon.cjs, part 240. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

The command "${command}" did not complete within the timeout period. The shell has been terminated.

On the next invocation of this tool, a new shell will be started at the project root.

${options2.heading}${isTruncated ? options2.truncatedSuffix ?? " (truncated)" : ""}:

```
${truncatedOutput.output}
```

Output collected before the stream closed

 (truncated to ${SHELL_CHAR_HARD_LIMIT} characters)

${SHELL_MISSING_EXIT_ERROR_MESSAGE}

${partialSection}

 after ${elapsedMs2}ms

 Do NOT await it; either continue with other work or end your turn.

The user manually backgrounded the ${toolNoun}${elapsedText}.${awaitGuidance}

 after ${elapsedMs2}ms

The ${toolNoun} was automatically backgrounded${elapsedText} because the user interrupted the chat. Consider killing the shell command if it should no longer run after the user's interruption.

${options2?.autoBackgroundedForInterruption === true ? formatAutoBackgroundedForInterruptionToolMessage("command", msToWait) : formatUserManuallyBackgroundedToolMessage("command", msToWait, options2)}

The command did not complete in ${msToWait}ms and was sent to the background.

Shell ID: ${shellId}

PID: ${pid}

The output is being written to ${outputPath}. Don't mention Shell ID to the user.

Output collected before backgrounding

No output was collected before backgrounding.

Command exceeded block_until_ms and was moved to background.

Output before backgrounding

 (truncated to ${SHELL_CHAR_HARD_LIMIT} characters)

No output before backgrounding.

Shell ID: ${shellId}

PID: ${pid}

Output will continue to be written to ${outputPath}. Don't mention Shell ID to the user.

${message}

Command: ${timeout2.command}

Background command started successfully.
Shell ID: ${shellId}

PID: ${pid}

Command: ${result.value.command}
Output will be written to ${outputPath}. Don't mention Shell ID to the user.

Background command rejected by user

Permission denied: ${result.value.error}

Error: Command failed to spawn: ${result.value.error}

Command: ${result.value.command}

Error: Command failed to spawn: ${result.value.error}

Unknown error

Unhandled result case: ${_exhaustiveCheck}

Command was aborted by the user.
${formatted}

Error: Command failed to spawn: ${result.value.error}

Command: ${result.value.command}

Error: Command failed to spawn: ${result.value.error}

Rejected: ${result.value.reason}

Permission denied: ${result.value.error}

Unknown error

Unhandled result case: ${_exhaustiveCheck}

${executedCommand}
${result.combinedOutput.replace(/\n+$/, "")}

Exit code: ${result.exitCode}

Command output has been written to: ${formatOutputLocationSummary(result.outputLocation)}

Command output${isTruncated ? ` (truncated to ${SHELL_CHAR_HARD_LIMIT} characters)` : ""}:

 (truncated to ${SHELL_CHAR_HARD_LIMIT} characters)

Command ${result.signal === "SIGTERM" ? "aborted" : "completed"}.

The previous shell command aborted, so on the next invocation of this tool, a new shell will be started at the project root.

The previous shell command ended, so on the next invocation of this tool, you will be reusing the shell.

On the next terminal tool call, the directory of the shell will already be ${currentWorkingDirectory}.

use strict

The shell command returned no exit status, so its result is unknown — do not assume it ran or succeeded. If this repeats, the execution environment may need to be restarted.

use strict

Cursor Slack Tools

Cursor Automation Tools

Your durable memories live in the directory ${memoryDirectory}; use your normal file tools on it.

At the start of a run, inspect ${directoryPrefix} for prior context. Read ${defaultFile} if it exists, along with any relevant topic files.

When you learn something that should persist across runs, update those files with ordinary file edits.

Prefer short, factual notes. Re-read a file before rewriting it if another run may have changed it.