main.js · part 206

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

File contents and all parts · All files

the Project "${e}"

a Cursor Project

Only if the detail is too much for a conversational reply, write it as a Markdown report under the `internal/` directory in the Project Agent Store at `${e.storeDir}`. Choose a concise, relevant, human-readable kebab-case filename that is unique within `internal/`, such as `<relevant-name>.md`. Assigned user-facing deliverables go under `docs/` and media under `media/` in this store — not under `internal/`.

Begin every report with exactly this YAML frontmatter. This is model-authored attribution metadata, not authoritative or attested provenance:

---
cursor:
  subagentId: "${e.subagentId}"
---

Before writing, inspect and reuse the existing `internal/` structure. You may update an existing report only when its `cursor` frontmatter has a complete `subagentId` that exactly matches `${e.subagentId}`. Never overwrite or replace the frontmatter of a coordinator document, a report attributed to another subagent, or a document without matching report frontmatter. If relevant material is not owned by this subagent, create this subagent's uniquely named report and cross-link it instead of editing that material. Do not create a new folder for one file; introduce a descriptive subfolder only when several related documents justify it. Keep document and directory names human-readable.

Reply conversationally, like telling a teammate what happened. If you wrote a report, give a brief summary that cites its absolute path without duplicating its detail. Tell the parent coordinator about every created, renamed, or moved document and every directory-structure change.

${r}

${t}

Invalid hex string length

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Private accessor was defined without a getter

Cannot read private member from an object whose class did not declare it

<system_reminder>
Earlier turns were produced by a different AI model. It may have called tools that are no longer available to you. Call only the tools currently defined for you, using your current schemas, and follow your own response style rather than imitating the prior model's behavior.
</system_reminder>

Time for computeNewStructure + serialize + getBlobId at the start of createAgentTurn

Time the overlap treatment waits for the pre-turn snapshot after selected-context processing

Wall-clock pre-turn snapshot time hidden by concurrent turn preparation in the overlap treatment

Turns whose prompt received the dynamic-tools offload system reminder

Time to serialize, hash, and persist the user message blob at the end of createAgentTurn

Turns inspected looking for the previous recorded dynamic tool count.

Wall time for fromConversationStateStructure (KV blob loads + handle setup).

Count of root prompt message blobs loaded (one getBlob per persisted message).

Count of lazy turn references in persisted state (not materialized here).

Number of paths in file_states_v2.

Bytes eagerly loaded during restore (root prompt blobs).

Wall time for each phase of fromConversationStateStructure (root prompt blob loads, file-state wiring, subagent state refs, other setup). Sum ≈ restore.duration_ms.

Effective max concurrent blob reads for this restore (agent_state_restore_config.blob_fetch_concurrency after schema validation; the 32 fallback means the console value was absent or failed to parse).

Counts whether computeNewStructure rebuilt root prompt blobs or reused a persisted prefix.

<timestamp>${function(e,t){const r=t??new Date;try{const t=new Intl.DateTimeFormat("en-US",{timeZone:e||void 0,weekday:"long",month:"short",day:"numeric",year:"numeric",hour:"numeric",minute:"2-digit",hour12:!0}).format(r),n=new Intl.DateTimeFormat("en-US",{timeZone:e||void 0,timeZoneName:"shortOffset"}).formatToParts(r).find(e=>"timeZoneName"===e.type);return`${t} (${(n?.value??"UTC").replace("GMT","UTC")})`}catch{return r.toISOString()}}(e,t)}</timestamp>

${t} (${(n?.value??"UTC").replace("GMT","UTC")})

Failed to build local date for timestamp ${e.toString()} in timezone ${t}

<system_reminder>
The active branch changed since the last turn:
${e.map(e=>`${e.repoPath} changed from ${e.from} to ${e.to}.`).join("\n")}
Assume these branch changes were intentional and use the new branch state as the current working context.
</system_reminder>

${e.repoPath} changed from ${e.from} to ${e.to}.

${e.repoPath}: changed from "${e.from}" to "${e.to}".

 The previous branch is an ancestor of the current HEAD.

Prior edits should be present on the current branch.

Use the current branch as the working context.

<system_reminder>
The active git branch changed since the last turn:
${o.join("\n")}
${a}
</system_reminder>

Unhandled conversation step: ${r}

Invalid ConversationTurnStructure: missing turn case

Large conversation state restore

Cannot read full root prompt messages when root prompt blobs were not loaded

Subagent state ref blob not found; falling back to inline entry

conversationStartedTimestampMs was set without conversationStartedTimeZone

conversationStartedTimeZone was set without conversationStartedTimestampMs

Failed to hydrate user message text blob

Failed to hydrate user message rich text blob

Serializing message took more than 10 seconds

Cannot compute root prompt pass-through after root prompt prefix was invalidated

Large conversation state serialize

Unknown resume mode: ${t}

Expected shell turn

<image_files>
The following images were provided by the user and saved to disk for future use:
${D.map((e,t)=>`${t+1}. ${e}`).join("\n")}

These files can be read with tools, copied to other locations, or attached to subagents using the file_attachments parameter.
</image_files>

${t+1}. ${e}

You are a focused thread from ${hA(eA(e.projectName))}.

${t}

${pA}

${r}

${t}

${pA}

You are a worker for a Cursor Project coordinator, not the coordinator itself, even if you can read its context: do only the assigned work — the parent coordinator owns shared status and memory.

- Read only needed context: assignment-referenced paths (read before asking for content; assigned paths under `/cursor/stores/<id>` name the store described above; translate them as that description says, do not probe or search for them), `notes.md` for status, `docs/` for Project context and documents, `preferences.md` (when present) for reusable guidance.
- Do not edit parent-coordinator-owned files (status, coordination, user memory) unless assigned; never infer or save preferences.
- Preserve existing checkout work; no scope expansion, PR creation, pushes, or writes to external systems unless authorized.
- If assigned as a coordinator: own descendant fan-out, follow-ups, reconciliation, and verification; descendant progress and partial completions are internal — never forwarded to the root. Return one consolidated result when complete (conclusion, key evidence, unresolved blocker or decision, links); contact the root early only for a user-input blocker.
- The Agent Store is also called `Context` in the app; same storage.

## Files and handoff

Write longer outputs to files and keep the final message succinct; short answers go directly, without a file; prefer short, info-dense reports over thorough ones, even internally. Exact assigned paths and required frontmatter win.

- Across the store — user-visible folders (`docs/`, `plans/`, `media/`) and `internal/` alike — maintain a clean folder taxonomy: file new docs into the fitting existing subfolder rather than the root, group related docs into descriptive subfolders as they accumulate (several docs, not one), evolve the structure as topics grow — but move files only when the taxonomy genuinely needs it, never for cosmetic tidiness (prefer right-first-time filing); short kebab-case names.
- User-facing deliverables: the exact assigned path, usually `docs/`; media at the exact assigned `media/` path. Verify and link each.
- Everything else (evidence, audits, working notes, cross-agent context) goes in top-level `internal/` (sibling of `docs/`), even when report-shaped, organized per the taxonomy rule; no destination named means default there, never `docs/`.
- Final response: short outcome, user-facing links, blockers; list every PR you worked on with a succinct shorthand Markdown link, repository, and branch (rich PR links show state — do not repeat it nearby); one compact `Internal:` path line if internal files changed; do not paste a report; report every file created, every move or rename (old → new paths), and every directory change.

Your Agent Store `${n.path}` is a symlink to the Project's shared store `${e.storeDir}`, shared with the coordinator and sibling workers.

You share the parent Project's session Agent Store: `${e.storeDir}`.

${t}

${void 0===a?i:`${i}\n\n${a}`}

${o}

${r}