main.js · part 115

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

File contents and all parts · All files

[summarization-adopt] Pending summary prefix mismatch; falling back to normal behavior

[summarization-adopt] Adopted pending summary

[summarization-adopt] Pending summary passed validation but was not persisted

[summarization-adopt] Failed to adopt pending summary; falling back to normal behavior

Failed to persist checkpoint after step

stateHandler.mode must be set before building tool execution context

No turns in conversation state

Expected last turn to be an agent turn

Rejected deferred split-step tool call outside model-visible tool allowlist

Rejected deferred split-step subagent preparation outside model-visible tool allowlist

Tool not found: ${c}

Tool does not support subagent preparation: ${c}

Expected last turn to be an agent turn

Running model-only step

Mid-loop background summarization trigger (model-stream-only): checking persist threshold

Model sample preempted by pending steer

Invocation ID mismatch. Bug in executeModelStreamOnly

Setting token details for client token ring (model-stream-only)

User aborted request

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

The beginning of the above subagent result is already visible to the user.

 Perform any follow-up actions (if needed). DO NOT regurgitate or reiterate its result unless asked. If multiple subagents have now completed and none are still running, briefly summarize the findings and conclusions across all of them. Otherwise, if no follow-ups remain, end your response with a brief third-person confirmation that the subagent has completed.

Perform any necessary follow-up actions in response to the subagent completion above.

 If no follow-up work is needed, no further action is required.

 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]`.

 Don't repeat the same confirmation every time.

A worker agent sent you a message mid-turn.

 The worker's turn may still be running — do NOT treat this as the worker finishing. Take any coordination action the message calls for (reply via SendToAgent if the worker needs input). If no action is needed, no further response is required.

A worker agent is paused waiting for the user to respond.

 Its turn is paused, not finished — do NOT treat this as the worker completing. Tell the user which worker is blocked and what it is waiting on (the notification detail has the question or authentication request), so they can respond to the worker directly. Do NOT answer the question or approve the authentication yourself, do NOT reply via SendToAgent on the user's behalf, and do NOT start polling the worker. The user may have already responded — the worker resumes on its own once they do, so simply inform the user and end your turn if nothing else is pending.

The user is actively driving this Project child.

 Record the completion for coordination, but do not message the user or take over the child thread. If no coordinator bookkeeping is required, end without further action.

Briefly inform the user about the task result and perform any follow-up actions (if needed).

<user_query>${Zke} If there's no follow-ups needed, don't explicitly say that.</user_query>

${n}
${r}

 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.

 If you mention an agent or subagent in your response, link it with the `[label](id)` format using the agent_id or task_id from the notification instead of printing the raw ID.

 A status of `aborted` means the subagent's turn was deliberately stopped (for example, the user pressed stop); treat the stop as intentional, not as a failure or accidental interruption, and do not resume, restart, re-dispatch, or send new instructions to it unless the user explicitly asks you to.

 Entries marked `reason: worker_message` are mid-turn messages from workers whose turns may still be running — they are NOT completions; do not treat those workers as finished, and take any coordination action their messages call for.

 Entries marked `reason: worker_needs_attention` are workers paused waiting for the user to respond — they are NOT completions; tell the user which worker is blocked and what it is waiting on, and do not answer on the user's behalf.

The following worker agent is paused waiting for the user to respond. Its turn is paused, not finished — this is not a completion.

The following worker agents are paused waiting for the user to respond. Their turns are paused, not finished — these are not completions.

The following worker agent sent you a message. Its turn may still be running — this is not a completion.

The following worker agents sent you messages. Their turns may still be running — these are not completions.

The following task has notified. If you were already aware, ignore this notification and do not restate prior responses.

The following tasks notified. If you were already aware, ignore this notification and do not restate prior responses.

The following task has finished. If you were already aware, ignore this notification and do not restate prior responses.

The following tasks finished. If you were already aware, ignore this notification and do not restate prior responses.

kind: ${function(e){switch(e){case F.aZc.SHELL:return"shell";case F.aZc.SUBAGENT:return"subagent";case F.aZc.UNSPECIFIED:return"unknown";default:return e}}(e.kind)}

status: ${oTe(e.status)}

reason: worker_reparented

reason: worker_message

reason: worker_needs_attention

task_id: ${oce(e.taskId)}

title: ${oce(e.title)}

tool_call_id: ${oce(e.toolCallId)}