daemon.cjs · part 238

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

File contents and all parts · All files

Stage the changes you worked on, commit, and push for this branch.

Stage the changes you worked on and create a commit for this branch.

- Stage the changes you worked on.

- If there are unrelated files or changes, exclude them.

- Write a concise commit message.

- Push after creating the commit.

- Do not push.

- Create a pull request for the branch.

- Do not include unrelated files in the commit.

- Follow the template file at ${pullRequestTemplateContext.pathToTemplateFile} for your PR template

- Follow the most applicable template file within the ${pullRequestTemplateContext.pathToTemplateDir} directory for your PR template

Push this branch to remote.

- Push the existing local commits on the current branch.

- Do not stage, unstage, or create new commits.

use strict

- Create the pull request with `gh pr create` (GitHub) or `origin pr create` (Cursor Origin — Cursor's PR host, not the git remote named `origin`). Prefer those over `gt`. If you use `gt`, you MUST pass `--github` or `--origin` for the intended host. If this conversation already includes preferred-host / create-command guidance, follow that instead.

using the ${taskToolName} tool

using your subagent tool

<system_reminder>
The user clicked Start Multitasking.

Create exactly one async subagent forked from yourself ${subagentToolText} with run_in_background set to true and resume set to "self". Use the prompt "You are the forked subagent; continue executing your task."

NOTE: If you receive the exact prompt "You are the forked subagent; continue executing your task.", then continue executing your task. Do NOT fork yourself again.

Otherwise, if you do not receive that prompt, immediately stop. Do not continue planning or coordinating, do not perform additional foreground work, and do not send a user-visible response after forking yourself into that subagent.
</system_reminder>

By clicking Build in Parallel, the user has entered **Multitask Mode** and has expressed a desire for parallel execution.

By clicking Build in Parallel, the user has expressed a desire for parallel execution.

For the plan execution and all follow-ups until the user exits multitask mode, follow your multitask mode instructions.

These parallelization instructions apply for the plan execution and its follow-ups.

<system_reminder>
The user clicked Build in Parallel.

Implement the plan as specified, it is attached for your reference. Do NOT edit the plan file itself.
Todos from the plan have already been created. Do not create them again. Mark them as in_progress as you work, starting with the first one. Don't stop until you have completed all the todos.

<build_with_multitask_instructions>
${modeStatement}

Rules for multitask plan execution:

When starting subagent(s) for plan execution, DO NOT repeat the plan in your prompt to the subagents. Just reference the plan file in your prompt, specify which steps of the plan the agent should execute, and include any required context which is not self-evident from the plan file.

For each Todo in your plan, decide which other Todos must be completed first. Then, flatten the dependency chains into one or more build phases. Execute each build phase as its own asynchronous (top-level) subagent. Whenever possible, execute independent build phases in parallel. If later Todos can be parallelized after the completion of earlier Todo(s), execute the blocking steps as an initial build phase, then launch parallel build phases after it completes.

IMPORTANT: If your plan includes dedicated testing steps at the end AND you are parallelizing across multiple implementation agents, instruct earlier subagents to not conduct end-to-end testing and use later testing subagents to test the full implementation. On the other hand, if just one agent is implementing, that agent should also do the testing.

${followUpStatement} For the extent of plan execution, these parallelization instructions take precedence over any other instructions about avoiding top-level sibling subagent parallelization.
</build_with_multitask_instructions>
</system_reminder>

use strict

use strict

use strict

... ${numHiddenLines} ${numHiddenLines === 1 ? "line" : "lines"} not shown ...
${result}

${result}
... ${numHiddenLines} ${numHiddenLines === 1 ? "line" : "lines"} not shown ...

 isFullFile="true"

 language="${codeBlock.languageIdentifier}"

 path="${codeBlock.filePath}"

 ${key}="${value}"

<${codeBlock.tag}${pathSection}${isFullFileSection}${languageIdentifierSection}${extraAttributesSection}>
${result}
</${codeBlock.tag}>

${paddedLineNumber}  ${line}

${paddedLineNumber}  ${line.text}

use strict

${result.absPath}${trailingSlash}
... no children found ...

File extension counts do not include files ignored by .gitignore.

target_directory is too large (either too many children or their names are too long). Immediate children were truncated. Try doing more specific search or use terminal tool.

Note: ${notes[0]}

Note:
 - ${notes.join("\n - ")}

${dir.absPath}${trailingSep}

${indent}- ${import_node_path72.default.posix.basename(normalizedPath)}${pathSep}

${childIndent}- ${child.name}

${metaIndent}cwd: ${meta.cwd}

${metaIndent}last modified: ${time3(meta.lastModifiedMs)}

exit: ${v2}

time: ${time3(v2)}

duration: ${v2}ms

${metaIndent}last commands:

${metaIndent}  - ${cmdFmt(cmd)}

${metaIndent}current command:

${metaIndent}  - ${cmdFmt(cmd)}

${count2} *${ext2 || "no-ext"}

${childIndent}- ${child.name}${pathSep}

${childIndent}  [${numFiles} file${numFiles === 1 ? "" : "s"} in subtree: ${sortedExtensions}]

${childIndent}- ${child.name}${pathSep}...

use strict

use strict