main.js · part 149

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

File contents and all parts · All files

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

Shell state (cwd, env vars) persists for subsequent calls.

 Current directory: ${t}

${(t/1024).toFixed(1)} KB

${t} bytes

${e.filePath} (${n}, ${r} lines)

Exit code: ${e.exitCode}

Runtime: ${e.executionTimeMs} ms

Output written to: ${Os(e.outputLocation)}

Exit code: ${e.exitCode}

Runtime: ${e.executionTimeMs} ms

Output:
${t.output}

Exit code: ${e.exitCode}

Command output has been written to: ${Os(e.outputLocation)}

${qs(t,e.executionTimeMs)}

Exit code: ${e.exitCode}

Command output${r?" (truncated to 20000 characters)":""}:

 (truncated to 20000 characters)

```
${t.output}
```

${qs(n,e.executionTimeMs)}

This command ran outside the sandbox (no restrictions) because it matched the user's command allowlist.

SANDBOXING: This command ran in a sandbox with the following restrictions:

- Filesystem: Read-only access limited to the workspace directory and explicitly allowed paths

- Filesystem: Read-only access to the filesystem (no file modifications allowed)

- Filesystem: Read access limited to the workspace directory and explicitly allowed paths; write access limited to permitted writable paths
- Temp files: /tmp is not accessible; $TMPDIR is a persistent per-project temp dir

- Filesystem: Write access limited to the workspace directory, read access to the rest of the filesystem

- Network access: Limited (allowlist only)

- Network access: Allowed (unrestricted)

- Network access: Blocked

The command likely failed due to sandbox restrictions (permission denied or access error). You should re-run with required_permissions: ["all"] to run outside the sandbox entirely. Don't needlessly ask for permission.

The command likely failed due to network restrictions. You should re-run with required_permissions: ["full_network"] to enable network access. Don't needlessly ask for permission.

If you think the command failed due to sandbox restrictions, re-run with the required_permissions that you need (such as ${`[${e[0]}]`}) or use required_permissions: ["all"] to run outside the sandbox entirely. Don't needlessly ask for permission.

If you think the command failed due to sandbox restrictions, re-run with required_permissions: ["all"] to run outside the sandbox entirely. Don't needlessly ask for permission.

${t.heading}${n?t.truncatedSuffix??" (truncated)":""}:

```
${r.output}
```

${t}

Command: ${e.command}

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

PID: ${t}

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

Background command rejected by user

Permission denied: ${r.value.error}

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

Command: ${r.value.command}

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

Unknown error

Unhandled result case: ${r}

${!0===i?.autoBackgroundedForInterruption?function(e,t){return`The ${"command"} was automatically backgrounded${void 0!==t?` after ${t}ms`:""} because the user interrupted the chat. Consider killing the shell command if it should no longer run after the user's interruption.`}(0,s):function(e,t,r){return`The user manually backgrounded the ${"command"}${void 0!==t?` after ${t}ms`:""}.${!0===r?.discourageAwait?" Do NOT await it; either continue with other work or end your turn.":""}`}(0,s,i)}

The ${"command"} was automatically backgrounded${void 0!==t?` after ${t}ms`:""} because the user interrupted the chat. Consider killing the shell command if it should no longer run after the user's interruption.

 after ${t}ms

The user manually backgrounded the ${"command"}${void 0!==t?` after ${t}ms`:""}.${!0===r?.discourageAwait?" Do NOT await it; either continue with other work or end your turn.":""}

 after ${t}ms

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

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

Shell ID: ${t}

PID: ${n}

The output is being written to ${r}. 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 20000 characters)

No output before backgrounding.