main.js · part 219

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

File contents and all parts · All files

Either file_paths or commit_hashes must be provided

Unhandled version: ${e}

Trace how code was built with AI for files and commits.

Treat this as git blame for AI-built changes: it reveals which conversations produced the code, why it was implemented a certain way, what alternatives were considered, and the intent behind decisions.

When to use this tool:
- The user asks about a file, module, or area of code and wants to understand it deeply -- use this alongside reading the file to add context about how and why it was built.
- Questions about history, evolution, or recent changes to code (e.g. "tell me about this file", "what's changed here recently", "how has this evolved"). For concept-level questions without a specific file (e.g. "how has plan mode evolved?"), first find the relevant files, then use this tool on them.
- Questions about authorship or decision-making (e.g. "who wrote this", "why is it done this way", "what tradeoffs were made").
- Before planning changes to existing code, to understand the intent behind the current implementation and avoid undoing deliberate design decisions.
- When used during planning, surface deliberate design decisions, past reversions, and intentional tradeoffs as constraints. Explain how the proposed changes relate to those prior decisions.

Output includes conversation context depth:
- Conversation title / tldr / overview / summary bullets
- Models used across the conversation and commit-linked sections

Query shape policy:
- File-first (`file_paths`) when the user anchor is code location. Always pass repository-relative git paths (for example `backend/server/src/app.ts`), not absolute workspace paths like `/Users/.../projects/repo/backend/server/src/app.ts`.
- Commit-first (`commit_hashes`) when the user anchor is a change event or narrative.
- Use both when both anchors are known (high precision, less noise).
- Use `file_paths` to compare a bounded set of files; use `commit_hashes` for stack/series narrative.
- For `file_paths`, pass repository-relative git paths (for example, paths shown in `git diff`), not absolute local filesystem paths.

Output strategy:
- Start with `output_mode: "summary"` + modest `max_commits`.
- Pivot to `output_mode: "detailed"` with line ranges once a target section is identified.
- If file query is empty but activity is expected, pivot to commit query.
- If commit query is noisy, add file filters.

Transcript fallback:
- If transcript pointers/context are available and you need deeper decision narrative, inspect transcript snippets after this tool (read in chunks, do not read entire transcript files at once).

Returns commit history with conversation-linked lineage details suitable for code archaeology and implementation-intent analysis.

[ai-attribution] fetching attribution

[ai-attribution] attribution fetched successfully

[ai-attribution] failed to fetch attribution

Failed to fetch AI attribution data. This may be a temporary issue - please try again later.

AI attribution output

Failed to get AI attribution: ${e.result.value.error}

An unknown error occurred.

Failed to fetch AI attribution data. This may be a temporary issue - please try again later.

Canvas validation timed out; if this save targeted a canvas, re-save the file to confirm its status and path.

Canvas TypeScript check: no errors.

Canvas TypeScript check: ${t.length} issue${t.length>1?"s":""} in ${e}:

 (${e.source})

  [${t}] L${n}:${s} - ${e.message}${o}

Canvas save accepted: validation passed; the canvas publishes asynchronously.

Canvas title: ${n}

Canvas path: ${function(e,t){const r=he.posix.resolve(e);for(const e of rW.ur)if(r===(0,iue.vP)(e,t))return r;return(0,iue.Up)(t)}(t,o.value)}

Canvas note: ${s}

Canvas not saved: this is not a valid canvas save path; nothing was published.

Canvas not saved: ${s}

Canvas not saved: the user agent store is unavailable; nothing was published.

Canvas not saved: ${s}

Canvas not saved: the canvas source exceeds the size limit; nothing was published.

Canvas not saved: ${s}

Canvas not saved: the type check failed; nothing was published.

Canvas not saved: ${s}

Canvas not saved: the canvas failed to compile; nothing was published.

Canvas not saved: ${s}

Canvas save state: ${r}.${void 0===s?"":` ${s}`}

${o}

${a}

Eager same-result agent-store conflict barrier outcomes.

Eager store conflict barrier telemetry failed

${n}

${i}

Eager store conflict deferred-path note failed

Eager store conflict release failed

Eager store conflict ack failed

Eager store conflict journal-drain fallback failed

${s}

${o}

${s}

${r}

${s}

${r}

Local-sync eager conflict barrier attributed

Eager store conflict barrier failed

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Cannot edit non markdown files in plan mode

Plan mode can only edit markdown files and canvas files. This edit was blocked because the target is not allowed in plan-mode. If the user wants implementation changes outside markdown or canvas files, use the ${e.SWITCH_MODE?.name??"SwitchMode"} tool with target_mode_id=agent first.

The string to replace was not found in the file.

The model provided an ambiguous search string to replace

${e} is empty

Incorrect tool arguments

old_string and new_string are exactly the same

Incorrect tool arguments

Total performEdit operations

Successful performEdit operations

Failed performEdit operations