main.js · part 218

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

File contents and all parts · All files

Max sleep time to block before returning (in milliseconds). Required. Set to 0 for non-blocking status check. Must not exceed 7140000 (${i} minutes).

Max sleep time to block before returning (in milliseconds). Defaults to ${r}ms. Set to 0 for non-blocking status check. Must not exceed 7140000 (${i} minutes).

block_until_ms must be at most 7140000 (${i} minutes)

Optional shell id to poll. If omitted, this tool sleeps for the full block_until_ms duration and then returns. Required when block_until_ms is 0.

Optional shell or subagent id to poll. If omitted, this tool sleeps for the full block_until_ms duration and then returns. Required when block_until_ms is 0.

Optional shell id to poll. If omitted, this tool sleeps for the full block_until_ms duration and then returns. Required when block_until_ms is 0.

Block until the regex matches stdout/stderr stream (or task completes). Matches anywhere in the shell output, not just new output. Will not match terminal file headers or footers, e.g. exit_code. Accepts JavaScript regex patterns (compiled with the multiline `m` flag). Not supported for awaiting subagents: you MUST leave this argument unset.

Block until the regex matches stdout/stderr stream (or task completes). Matches anywhere in the shell output, not just new output. Will not match terminal file headers or footers, e.g. exit_code. Accepts JavaScript regex patterns (compiled with the multiline `m` flag).

Set this to true if you are waiting for subagent(s) to complete. Remember you should NOT be doing this and instead end your turn or do parallel work.

path must be a path to a terminal file

path must be a path to a terminal file

Use to sleep and check shell progress. Never sleep using shell.

Poll a background shell.

Poll a background ${t?"shell or subagent":"shell"} job. For work that does not have a ${t?"task id":"shell id"}, you can omit the ${t?"task_id":"shell_id"} arg to sleep for the full `block_until_ms` duration (prefer this over sleeping in the shell, because it renders nicely to the user).

Monitor backgrounded jobs as follows:
- Never poll a task whose tool result says it was "manually backgrounded by the user".
- When you spawn a command directly into the background (`block_until_ms: 0`), check status immediately by reading the output file to confirm the command didn't fail to start.
- Poll repeatedly to monitor by using this tool between checks (set `block_until_ms` to control how long to wait). If the file gets large, read from the end of the file to capture the latest content.
- Pick your polling intervals using best guess/judgment based on any knowledge you have about the command and its expected runtime, and any output from monitoring the job. When no new output, exponential backoff is a good strategy (e.g. 2000ms, 4000ms, 8000ms, 16000ms...), using educated guess for min and max wait.${r?"\n- Shell only guidance:\n  - Waiting until a regex matches the output can be useful for e.g. known startup/status/error logs.\n  - HARD STOPPING CONSTRAINT: Don't stop polling until (a) job terminates, (b) the command reaches a healthy steady state (only for non-terminating command, e.g. dev server/watcher), or (c) command is hung - follow guidance below.\n  - Output file header has `pid` and `running_for_ms` (updated every 5000ms).\n  - When finished, footer with `exit_code` and `elapsed_ms` appears (regex only matches the body, not header/footer).\n  - If taking longer than expected and the command seems like it is hung (use judgment based on type of command), kill the process if safe to do so using the pid that appears in the header. If possible, try to fix the hang and proceed.":""}

shell or subagent

task id

shell id

- Shell only guidance:
  - Waiting until a regex matches the output can be useful for e.g. known startup/status/error logs.
  - HARD STOPPING CONSTRAINT: Don't stop polling until (a) job terminates, (b) the command reaches a healthy steady state (only for non-terminating command, e.g. dev server/watcher), or (c) command is hung - follow guidance below.
  - Output file header has `pid` and `running_for_ms` (updated every 5000ms).
  - When finished, footer with `exit_code` and `elapsed_ms` appears (regex only matches the body, not header/footer).
  - If taking longer than expected and the command seems like it is hung (use judgment based on type of command), kill the process if safe to do so using the pid that appears in the header. If possible, try to fix the hang and proceed.

Unhandled version: ${t}

Must pass a task id or wait for a nonzero duration.

Regex awaiting is not available for subagents. Run Await without regex, or await a shell task id instead.

Awaiting subagent tasks requires a non-empty conversationId in the agent context

Awaiting subagent ids is not available in this environment (subagent executor resource is not registered).

Unknown legacy subagent await result

Unhandled legacy subagent result case: ${e}

Subagent not found

Failed to await subagent task

Unknown subagent await result

Unhandled subagent await result case: ${e}

Cannot await shell task: terminals folder is unavailable

Failed to read shell output

No shell found for id ${f}

Pattern matched: ${e.regexMatch??""}

Pattern did NOT match.

Slept briefly.

Slept for ${Math.max(1,Math.ceil(t/1e3))}s.

${t} Sleep released early: a new user message is arriving.

Task completed in ${(e.runtimeMs??BigInt(0)).toString()}ms with exit code: ${void 0!==r?String(r):"unknown"}.

Task complete.

${o} ${t}

${o}
output_file_path: ${e.outputFilePath}
output_length: ${e.outputLength.toString()}

Task still running after ${(e.runtimeMs??BigInt(0)).toString()}ms...

Task still running.

${r} Wait released early: a new user message is arriving.

${t.length>0?`${r} ${t}`:r}
output_file_path: ${e.outputFilePath}
output_length: ${e.outputLength.toString()}

${r} ${t}

Error awaiting task: ${s.value.error}

Unknown error

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

File paths to get AI attribution for. Use repository-relative git paths (for example: backend/server/src/app.ts), not absolute workspace paths.

Optional start line (1-indexed). If not provided, gets AI attribution for entire file. Applies to all files.

Optional end line (1-indexed). If not provided, gets AI attribution to end of file. Applies to all files.

Commit hashes to get AI attribution for. Returns AI conversation summaries for each commit.

Controls output shape and verbosity. Use "summary" for conversation-level rollups and "detailed" for per-commit/per-range output.

Optional cap on commits returned after filtering/de-duplication. Must be between 1 and 200.

When false, omit detailed line ranges from attribution output.