daemon.cjs · part 311

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

File contents and all parts · All files

Subagent type to use for this task. Must be one of: ${configNames.join(", ")}.

Subagent type to use for this task. Available types are listed in the initial user-info message${catalogUpdateSuffix}.

Optional array of file paths to images or videos to attach to the subagent. Files are read and attached to the subagent's context. Use to forward relevant media to any subagent (e.g. pass a user-attached image's saved file path so the subagent sees the actual image rather than a prose description).

Optional execution environment for the subagent. Use "local" (default) for normal local subagents, or "cloud" to run the subagent as a cloud agent (i.e. in its own separate worktree). ONLY set to cloud if the user explicitly requests a cloud subagent. DO NOT set to cloud if user does not request cloud. Cloud subagents will work on their own git branch on their own VM. After subagent completion, follow user instructions on whether to merge that branch into your own branch, check it out, or neither.

 If you mention an agent or subagent in your response, link it with the `[Name](id)` Don't use generic label such as `[agent]`, `[worker]`, or `[subagent]`.

 For cloud subagents, when the agent has edited code, link to `[Review](bc-id#changes)`, or, if you know the exact added and deleted line counts, `[Review +A −D](bc-id#changes)`, replacing A and D with those counts. Never write A or D literally. Use `[Try Live](bc-id#desktop)` only when the agent used computer use.

Base branch for the cloud subagent's branch to start from. Default is current branch. Uses remote version of branch; uncommitted or un-pushed branches will fail. Only specify this parameter if environment equals cloud.

Exact environment build id (e.g. bld-YYYYMMDD-<uuid>) for the cloud subagent's VM to boot from, instead of the environment's latest successful build. Use to test a specific environment build in an isolated cloud subagent. Only specify this parameter if environment equals cloud. The build must belong to the same team and environment; an invalid or inaccessible build fails the subagent.

Run the agent in the background (returns output_file path to check later).

Run the agent in the background. A background subagent cannot be polled or awaited; after spawning it, continue other work or end your turn, and its final result will be delivered to you automatically when it completes.

 Defaults true.

 If this is false, you will be blocked until the agent completes.

 If the user is currently in Multitask Mode, always set this parameter to True.

 When true, the background subagent will send a notification when it completes.

 When true, the background subagent will send a notification when it completes. That notification includes a user-visible summary portion; do not summarize or restate a completed background subagent's result unless the user asks, multiple background subagents need synthesis, or a background subagent reports a blocker requiring parent action outside of the user-visible high level summary.

This retired subagent type can only resume an existing child

subagent_type is required when creating a new subagent

cloud_base_branch may only be specified when environment equals cloud

cloud_requested_environment_build_id may only be specified when environment equals cloud

A short, user-friendly title for the subagent. This appears in the UI as the subagent's name. Make it concrete and distinct, consider recent titles to avoid reuse. For resumed subagents which you are prompting to work on a separate task, give an updated description based on the latest work the subagent is performing. (Do not rename if the subagent is continuing work on the same high-level task.)

  - If you want to read a specific file path, use the ${readToolName}${globToolName ? ` or ${globToolName}` : ""} tool instead of the ${toolLabel} tool, to find the match more quickly

 or ${globToolName}

  - If you are searching for code within a specific file or set of 2-3 files, use the ${readToolName} tool instead of the ${toolLabel} tool, to find the match more quickly

  - If you are searching for a specific class definition like "class Foo", use the ${globToolName} tool instead, to find the match more quickly

${includeExploreProactiveRecommendation ? `
VERY IMPORTANT: When broadly exploring the codebase to gather context for a large task, it is recommended that you use the ${toolLabel} tool with subagent_type="${EXPLORE_SUBAGENT_TYPE}" instead of running search commands directly.
` : ""}
If the query is a narrow or specific question, you should NOT use the ${toolLabel} and instead address the query directly using the other tools available to you.

Examples:
- user: "Where is the ClientError class defined?" assistant: [Uses Grep directly - this is a needle query for a specific class]
- user: "Run this query using my database API" assistant: [Calls the MCP directly - this is not a broad exploration task]
- user: "What is the codebase structure?" assistant: [Uses the ${toolLabel} tool with subagent_type="${EXPLORE_SUBAGENT_TYPE}"]

If it is possible to explore different areas of the codebase in parallel, you should launch multiple agents concurrently.

VERY IMPORTANT: When broadly exploring the codebase to gather context for a large task, it is recommended that you use the ${toolLabel} tool with subagent_type="${EXPLORE_SUBAGENT_TYPE}" instead of running search commands directly.

- When the agent is done, it will return a single message back to you. Specify exactly what information the agent should return back in its final response to you.

- When the agent is done, it will return a single message back to you. Specify exactly what information the agent should return back in its final response to you. Background subagent completion messages already include a user-visible summary portion; do not summarize or restate a single background subagent's result by default. Respond only when the user asks, multiple background subagents need synthesis, or the background subagent reports a blocker requiring parent action outside of the user-visible high level summary.

- When the agent is done, it will return a single message back to you. Specify exactly what information the agent should return back in its final response to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.

This sends a follow-up message after the agent has completed, preserving existing context. If the agent is still running, the request fails unless `interrupt` is true. Set `interrupt` to true only when the user explicitly wants to interrupt the running agent.

This sends a follow-up message after the agent has completed, preserving existing context. If the agent is still running, the request fails; wait for completion before resuming.

When resumed, the agent continues with its full previous context preserved.

- Agents can be resumed using the `resume` parameter by passing the agent ID from a previous invocation. ${resumeBehavior}${allowResumeSelfFork ? ` You can also set \`resume\` to "${TASK_RESUME_SELF_SENTINEL}" to fork the current parent agent into a new child subagent.` : ""} When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.

 You can also set `resume` to "${TASK_RESUME_SELF_SENTINEL}" to fork the current parent agent into a new child subagent.

Launch a new agent to handle complex, multi-step tasks autonomously.

The ${toolLabel} tool launches specialized subagents (subprocesses) that autonomously handle complex tasks. Each subagent_type has specific capabilities and tools available to it.

When using the ${toolLabel} tool, you must specify a subagent_type parameter to select which agent type to use.${exploreRecommendation}

When NOT to use the ${toolLabel} tool:
- Simple, single or few-step tasks that can be performed by a single agent (using parallel or sequential tool calls) -- just call the tools directly instead.
${doNotUseExamples.length > 0 ? `- For example:
${doNotUseExamples}` : ""}

Usage notes:
- Always include a short description (3-5 words) summarizing what the agent will do
- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses.
${resultVisibilityNote}${resumeUsageNote}
${enableAgentChatLinks ? hideAsyncSubagentTaskNotifications ? "- If you mention an agent or subagent in your response, link it with the `[Name](id)` Don't use generic label such as `[agent]`, `[worker]`, or `[subagent]`. For cloud subagents, when the agent has edited code, link to `[Review](bc-id#changes)`, or, if you know the exact added and deleted line counts, `[Review +A \u2212D](bc-id#changes)`, replacing A and D with those counts. Never write A or D literally. Use `[Try Live](bc-id#desktop)` only when the agent used computer use.\n" : "- In user-facing responses, you may link to agents and subagents with markdown chat links in the `[label](id)` format, using the agent ID as the link target. Do not print raw agent IDs separately.\n" : ""}- When using the ${toolLabel} tool, the subagent invocation does not have access to the user's message or prior assistant steps. Therefore, you should provide a highly detailed task description with all necessary context for the agent to perform its task autonomously.
- The subagent's outputs should generally be trusted
- Clearly tell the subagent which tasks you want it to perform, since it is not aware of the user's intent or your prior assistant steps (tool calls, thinking, or messages).
- If the subagent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
- If the user specifies that they want you to run subagents "in parallel", you MUST send a single message with multiple ${toolLabel} tool use content blocks. For example, if you need to launch both a code-reviewer subagent and a test-runner subagent in parallel, send a single message with both tool calls.
- Avoid delegating the full query to the ${toolLabel} tool and returning the result. In these cases, you should address the query using the other tools available to you.

- For example:
${doNotUseExamples}

- If you mention an agent or subagent in your response, link it with the `[Name](id)` Don't use generic label such as `[agent]`, `[worker]`, or `[subagent]`. For cloud subagents, when the agent has edited code, link to `[Review](bc-id#changes)`, or, if you know the exact added and deleted line counts, `[Review +A −D](bc-id#changes)`, replacing A and D with those counts. Never write A or D literally. Use `[Try Live](bc-id#desktop)` only when the agent used computer use.

- In user-facing responses, you may link to agents and subagents with markdown chat links in the `[label](id)` format, using the agent ID as the link target. Do not print raw agent IDs separately.

 (Auto-resumes most recent agent of this type; `resume` arg is ignored)

 (Auto-resumes most recent agent; `resume` arg is ignored)

- ${name17}: ${description3}

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

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

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

use strict

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

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

Provider error:

Not found error:

API Error:

Unhandled interaction query type: ${query.query.case}

Run on this machine, sharing its checkout and branch. The default.

Worker to run on, from cursor-cloud-list-self-hosted-workers. Only your own machines can be targeted this way; use self_hosted_pool for a team pool worker. Check that tool's sharedAssignmentAllowed first: a shared worker runs this subagent alongside others, otherwise the subagent waits for the worker to free up.

Run on one specific self-hosted worker of your own. The subagent uses that machine's existing checkout and branch, so it cannot be given a base branch.

Pool to draw a worker from. Defaults to the team's default pool.

Key/value labels a candidate worker must all match.