main.js · part 136

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

File contents and all parts · All files

CODE

CODE

CODE

CODE

CODE

SAFE

CODE

CODE

CODE

CODE

CODE

CODE

CODE

SAFE

### Transcript location:
  This is the full JSONL transcript of your past conversation with the user (pre- and post-summary): ${(0,he.join)(e,function(e){const t=`${ja.O2}/`;return e.startsWith(t)?e.slice(t.length):e}(r))}

  If anything about the task or current state is unclear (missing context, ambiguous requirements, uncertain decisions, exact wording, IDs/paths, errors/logs), you should consult this transcript.

  How to use it:
  - Search first for relevant keywords (task name, filenames, IDs, errors, tool names).
  - Then read a small window around the matching lines to reconstruct intent and state.
  - Avoid reading linearly end-to-end; the file can be very large and some single lines can be huge.
  - Files contain one structured json event per line including user/assistant messages. Currently tool calls and results are excluded.
  

### Transcript location:
  - This folder contains full transcripts of past conversations with the user (pre- and post-summary): ${e}
  - Each conversation is stored as a <convoId>/<convoId>.jsonl.

<transcript_location>
${s.replace("\n\n### Transcript location:\n","").replace(/^ {2}/gm,"").trimEnd()}
</transcript_location>

### Transcript location:

<todo_update>
${e}
</todo_update>

10. Current plan mode progress:
   The below plan was previously created in this session. If you are still in plan mode, continue to iterate on the plan with the user given the rest of your context on the current conversation. Otherwise, if there are remaining relevant todos, you should continue to implement them according to the plan.

<file_contents path="${function(e){const t=e.name||"plan",r=t.endsWith(".plan.md")?t:`${t}.plan.md`;return e.composerId?`cursor-plan://${e.composerId}/${r}`:`cursor-plan:///${r}`}(e.currentPlan)}" isFullFile="true">
${t}
</file_contents>

<current_plan>
${t}
</current_plan>

NOTE: This is an automation run. The original trigger info that started this session:
${e.automationTriggerContext}

12. Automation trigger info (this is the original trigger that started this agent):

${e.automationTriggerContext}

NOTE: There was an active todo list in the conversation. Here is the latest update before summarization:
${Ha(e.todoContent)}

No assistant response received

Context summarization on ${e.summarizerModelId} failed (${e.errorKind}); the previous context was kept

request contained too many images or documents

too many images or documents error

too many images and documents

too much media

request contains text fields that are too large

not valid json

invalid json

invalid argument

User API Key Rate limit exceeded

data:${function(e){const t=e?.trim();return void 0!==t&&""!==t?t:"image/png"}(e.mimeType)};base64,${e.image}

[summarization-pipeline] preservedTailMessages shape invariant violated

Additional instruction: Write a shorter summary that focuses on the highest-signal context. Avoid long code snippets and avoid unnecessarily exhaustive detail. Prioritize the most recent user intent, recent implementation work, and unresolved blockers.
IMPORTANT: When listing user messages, you do not need to repeat each message verbatim. Concisely capture user intent.

[summarization-handler] Error getting extended usage

[summarization-handler] Error getting usage

[summarization-handler] Error getting provider metadata

[summarization-handler] Error getting invocation id

[summarization-handler] Error getting response

[summarization-handler] Summarization response contained more than one assistant message; using only the last to avoid duplicated summaries

Summarization returned empty text

${e} ${t.slice(0,Ac)}
[... truncated, ${t.length} total chars]

${e} ${t}

[Thinking] ${e.text}

[Tool call] ${e.toolName}

[Tool call] ${e.toolName} ${r}

[Tool result] ${e.toolName}

[Tool result] ${e.toolName} ${r}

<summarization_request>${dl}${r?.requestShorterOutput?Mc:""}</summarization_request>

${e.role}: ${Dc(e,!0)}

[summarization-handler] Reducing prompt budget due to byte limit

[summarization-handler] Would truncate summarization prompt

[summarization-handler] failed to build summarization prompt

Cannot fit any summarization message within prompt char budget

[summarization-handler] Suspiciously short joined result length for summarization

[summarization-handler] Final prompt exceeded byte budget