main.js · part 214

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

File contents and all parts · All files

You've made {idle_count} responses without tool calls. If you're done, respond with exactly: {escape_token}
If not, continue working.

The following background agents have completed:

{summaries}

Review their results. If more work is needed, spawn additional workers. Otherwise, wrap up.

Video attachments are only supported for Gemini models

Could not detect mime type for attachment: ${t}

Steer-driven subagent background handoff failed

Client-side subagent failed or was aborted

Unknown subagent error

Unknown subagent result

Client-side subagent completed successfully

WritableIterable is closed

The subagent's connection closed before it finished (the run was torn down mid-flight). This is usually transient — please try again.

Client-side subagent execution interrupted by stream teardown

Client-side subagent execution threw error

Creating subagent and starting execution

Subagent exceeded execution timeout of ${pe}ms

Spawn local and cloud subagents natively.

Failed to parse arguments

Invalid arguments:
argument: ${t}

${e.path.length>0?e.path.join("."):"argument"}: ${e.message}

Invalid arguments:
${e.join("\n")}

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Failed to record initial checkpoint outcome

Time for initializeConversation (system prompt, rules, turn creation)

Time to resolve the request context (may call executor)

Time to process prepended user messages (sendUpdate + createAgentTurn per message)

Time for system prompt generation, UserInfo, tool generation, and message assembly

Time for the main stateHandler.createAgentTurn call (includes processSelectedContext)

Time for optional computeNewStructure + onStateUpdate after turn creation

 after ${e}ms

Error: Shell command was interrupted by the user${n} before it completed.

Error: Shell command was interrupted by the user${n} before it completed.

${Mz(t,{heading:"Output collected before interruption",truncatedSuffix:" (truncated)"})}

Output collected before interruption

Error: Await was interrupted by the user${sce(e)}.

Error: ${e.toolName} was interrupted by the user${sce(e.elapsedMs)} before it completed.

User message is required

dropped excess prepended user messages

prepending user messages

skipping duplicate prepended user message

${s}

${function(e,t={}){return`<system_reminder>\n${g2(e,t)}\n</system_reminder>`}(t,r)}

<system_reminder>
${g2(e,t)}
</system_reminder>

Failed to persist checkpoint for new turn

Brief final summary of the work you have performed. When helpful, include illustrative examples of completed work.

Major step or phase you are on. Update when the subtask changes. Keep the text concise, high-level, and user-friendly.

Major step or phase you are on. Update when the subtask changes. Keep the text concise, high-level, and user-friendly.

User-facing executive summary succinctly reporting on your work / responding to the user's message; write this as a concise message speaking back to the user, not as a status tag. Typically 1-3 sentences, or a brief lead-in plus bullet points when there are multiple distinct takeaways, decisions, test results, etc. When using bullets, make them pleasant and easy to scan: 2-5 bullets when possible, one useful idea per bullet, ordered by importance to the user, concise but not cryptic, and no nested bullets unless the user requested detail. Use prose instead of bullets when there is only one main takeaway. Include the most relevant takeaways for the user, as implied by the user's original request. No unnecessary details. When answering questions by the user, include the full answer that the user is seeking. Examples of what to include: full answer(s) to user's question(s), high-level root cause while debugging, status update of completed (or in-progress) work, test results for specifically requested testing, blocking questions the user must answer before you can continue, links to newly created PRs, etc. Examples of what NOT to include (unless implicitly or explicitly requested by the user): tool calls / results, code / log / shell command excerpts, long file paths, line numbers, low-level implementation details, etc. Set this field just ONCE per turn, as the last thing you do before your final response, at the same time that you set the completed_subtitle field.

4-6 word, past-tense, final summary of the work you have completed. Will be used as your agent subtitle in the UI. Keep the text concise, high-level, and user-friendly. Set this field ONCE per turn, as the last thing you do before your final response, at the same time that you set the final_summary field.

Action to perform.

Target/start x coordinate; pair with y. Required for move/drag.

Target/start y coordinate; pair with x. Required for move/drag.

Drag destination x coordinate; required for drag.

Drag destination y coordinate; required for drag.

Text; newlines press Return and tabs press Tab; required for type.

Key or shortcut; required for key, e.g. Return or ctrl+a.

Click/drag mouse button; defaults to left.

Keys held during click, drag, or scroll.

Click count for click; defaults to 1.