main.js · part 240

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

File contents and all parts · All files

The command to execute

The absolute path to the working directory to execute the command in (defaults to current directory)

Clear, concise description of what this command does in 5-10 words. Examples:
Input: ls
Output: Lists files in current directory

Input: git status
Output: Shows working tree status

Input: npm install
Output: Installs package dependencies

Input: mkdir foo
Output: Creates directory 'foo'

How long to block and wait for the command to complete before moving it to background (in milliseconds). Set to 0 to immediately run the command in the background. The timer includes the shell startup time.

How long to block and wait for the command to complete before moving it to background (in milliseconds). Defaults to 30000ms (30 seconds). Set to 0 to immediately run the command in the background. Make sure to set `block_until_ms` to higher than the command's expected runtime. Add some buffer since block_until_ms includes shell startup time; increase buffer next time based on previous elapsed times if you chose too low. E.g. if you sleep for 40s, recommended `block_until_ms` is 45s. Do not specify a 'timeout' parameter; no such param exists.

 --trailer "${sd.Mp}"

Made with [Cursor](https://cursor.com)

Made with [Cursor]

Made with [Cursor]

Auto-review shell approval store is not configured

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Count of 'command not found: dump_zsh_state' errors in shell output

Count of foreground shell executions whose exec stream closed without an exit event (likely exec backend unavailable/desynced)

Git commit trailer modifier applications

PR generated-by footer modifier applications

Rejected: ${r}

Permission denied: ${r}

Permission denied: ${r}

Terminal unavailable: this machine cannot enforce the '${r}' sandbox policy this command requires, because no working sandbox backend is available (${n}). This is not a permission denial. Commands requiring this policy cannot run here unless sandbox support is set up on this machine.

Output collected before the stream closed

 (truncated to 20000 characters)

${Ms}

${t}

Command blocked by Auto-review preflight

notify_on_output must be an object

notify_on_output.pattern must be a string

notify_on_output.pattern is required

notify_on_output.pattern must be 500 characters or fewer

Invalid notify_on_output pattern: ${e instanceof Error?e.message:String(e)}

notify_on_output.reason must be a string

notify_on_output.reason is required

notify_on_output.reason must be 200 characters or fewer

notify_on_output.debounce_ms must be a number of milliseconds

notify_on_output.debounce_ms must be finite

notify_on_output.debounce_ms must be greater than 0

Set to true when immediately retrying the exact same command after Auto-review blocks it and you decide the user should approve it through the native approval card.

Provide the exact block reason returned by Auto-review in the prior rejection. Required when request_smart_mode_approval is true so the approval card shows the original classifier reason without re-running the classifier.

Shell tool executing

Command classifier failed

Model accessed agent transcript path

Auto-review shell approvals require a conversation id

Smart Mode shell preflight state

Smart Mode shell native approval requested

Smart Mode shell allowlist precheck starting

Smart Mode shell allowlist precheck completed

Shell allowlist precheck failed

Smart Mode shell sandbox autorun bypass

Smart Mode shell classifier allowed

Smart Mode shell classifier rejected

Smart Mode shell classifier blocked

Smart Mode shell approval provider allowed

${h.reason}

<system_reminder>
Auto-review blocked this autonomous tool call. Decide now between two paths: (1) if a genuinely safer, lower-privilege, authorized path satisfies the request, use it; (2) if this blocked action is still necessary and the user should approve it, immediately retry the exact same Shell call with request_smart_mode_approval set to true AND smart_mode_block_reason set to the exact block reason text above. That retry is what shows the native approval card; stopping here leaves the user with no approval UI. Do not change the command, add permissions, or use an escalated variant when retrying for approval. Trying a different anonymous public file host, pastebin, disposable transfer link, or similar courier is NOT path (1) — that is the same unauthorized data-exposure crossing — so for that class prefer path (2) or ask the user, do not shop for another intermediary.
</system_reminder>

Smart Mode shell background handoff

Unknown error starting background command

Unhandled background result case: ${e}

Failed to clean up rejected background shell approval

Smart Mode shell foreground handoff