main.js · part 120

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

File contents and all parts · All files

Available subagent_types and a quick description of what they do:
${e}

Available subagent_types and descriptions are listed in <available_subagent_types> in the initial user-info message at the start of this conversation${b}.

No alternative models are available. Subagents will inherit the parent model.

If the user explicitly asks for the model of a subagent/task, you may ONLY use model slugs from this list:
${t?"- inherit (default; required unless the user explicitly requested another model)\n":""}${[...e.modelsBySlug.keys()].sort().map(e=>`- ${e}`).join("\n")}

If the user isn't asking for a specific version, prefer the latest version of the model family. As an example, if the user just says "gpt" or "claude", use the latest available version of GPT or Claude.

IMPORTANT: If the user requests a model that is NOT in the list above, do NOT substitute a different model or guess. Instead, skip launching the subagent with that model and tell the user which model was unavailable and which models are available.

When speaking to the USER about which model you selected for a subagent, do NOT use the kebab-case model names unless the user requested the model using that format. Ue the same naming scheme the user used to discuss the model when they requested it.

- inherit (default; required unless the user explicitly requested another model)

Available model slugs for subagents are listed in <available_subagent_models> in the initial user-info message at the start of this conversation${b}.

When an agent runs in the background, you will be automatically notified when it completes after you end your own turn - do NOT ${R?`${e} or poll it`:`${e}, poll, or proactively check on its progress`}. Continue with other work or end your turn instead. Don't mention this to the user.

${e} or poll it

${e}, poll, or proactively check on its progress

When an agent runs in the background, you will be automatically notified when it completes after you end your own turn - do NOT ${R?"poll it":"poll or proactively check on its progress"}. Continue with other work or end your turn instead. Don't mention this to the user.

poll it

poll or proactively check on its progress

IMPORTANT: Do NOT use this tool unless the user has explicitly asked you to use subagents, delegate to agents, or use the ${ne} tool. You should perform tasks directly using your own tools instead of delegating to subagents. Only use this tool when the user specifically requests it.

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

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

Getting Task tool config

Failed to get Task tool config

Error executing subagentStart hook

Invalid arguments:
Self-hosted machine placement requires server-side first-class subagent execution and is not supported by a fresh client-executed Task.

Invalid arguments:
Unsupported machine placement for a fresh client-executed Task: ${JSON.stringify(t)}.

Using client-side subagent execution

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.

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

Output collected before interruption

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

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

User message is required