main.js · part 98

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

File contents and all parts · All files

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,oe)}
[... 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>${Fe}${r?.requestShorterOutput?ae:""}</summarization_request>

${e.role}: ${de(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

[summarization-handler] Summarization prompt exceeded char budget; truncated

Successful summarizations

Total summarization attempts

Failed summarizations

Per-try summarization attempts within the retry loop

Per-try successful summarization attempts

Per-try failed summarization attempts

Total retries (attempts beyond the first) that actually executed

Summary length in characters

Blocking duration of summarization

Input tokens consumed during summarization

Output tokens generated during summarization

Percentage of tokens removed by summarization: (input - output) / input * 100

Total character length of all messages before summarization

Total character length of all messages persisted after summarization (system + userInfo + summary + preserved tail)

End-to-end compression percentage including preserved tail messages: (1 - persisted/original) * 100

WaitForCompletion summarizations that fell back to deterministic compaction after LLM retries exhausted

Summarization attempts where all summarization models are blocked and the main model is used as fallback

Failed summarizations where all summarization models are blocked and the main model is used as fallback

Time between last two messages in conversation

You are an intelligent assistant, tasked with summarizing the following conversation. You MUST follow the instructions given in the <summarization_request> tags and summarize the conversation. This summary will be provided to another AI assistant to continue the task at hand, so you should align the summary with the task in the conversation.

[Previous conversation summary]:

What you see above is the conversation so far, rendered as a transcript. Previous user messages, previous assistant messages, and tool calls are shown in tags, while the original system prompt has been removed. The content in the tags has been rendered exactly as it was in the original conversation.

Your task is to create a detailed summary of the conversation so far, paying close attention to the user's explicit requests and your previous actions. This summary will be provided to another AI assistant to continue the task at hand, so you should align the summary with the task in the conversation above. So you should NEVER refer to summarization in your summary, just an output that could be used to continue the task.

This summary should be thorough in capturing technical details, code patterns, and architectural decisions
that would be essential for continuing development work without losing context.

1. Chronologically analyze each message and section of the conversation. For each section thoroughly identify:
   - The user's explicit requests and intents
   - Your approach to addressing the user's requests
   - Key decisions, technical concepts and code patterns
   - Specific details like:
   - file names
   - full code snippets
   - function signatures
   - file edits
- Errors that you ran into and how you fixed them
- Pay special attention to specific user feedback that you received, especially if the user told you to do
something differently.
2. Double-check for technical accuracy and completeness, addressing each required element thoroughly.

Your summary should include the following sections:

1. Primary Request and Intent: Capture all of the user's explicit requests and intents in detail
2. Key Technical Concepts: List all important technical concepts, technologies, and frameworks discussed.
3. Files and Code Sections: Enumerate specific files and code sections examined, modified, or created. Pay special attention to the most recent messages and include full code snippets where applicable and include a summary of why this file read or edit is important.
4. Errors and fixes: List all errors that you ran into, and how you fixed them. Pay special attention to specific user feedback that you received, especially if the user told you to do something differently.
5. Problem Solving: Document problems solved and any ongoing troubleshooting efforts.
6. All user messages: List ALL user messages that are not tool results or subagent prompts/results. These are critical for understanding the users' feedback and changing intent.
7. Pending Tasks: Outline any pending tasks that you have explicitly been asked to work on.
8. Current Work: Describe in detail precisely what was being worked on immediately before this summary request, paying special attention to the most recent messages from both user and assistant. Include file names and code snippets where applicable.
9. Optional Next Step: List the next step that you will take that is related to the most recent work you were doing. IMPORTANT: ensure that this step is DIRECTLY in line with the user's explicit requests, and the task you were working on immediately before this summary request. If your last task was concluded, then only list next steps if they are explicitly in line with the users request. Do not start on tangential requests or really old requests that were already completed.

If there is a next step, include direct quotes from the most recent conversation
showing exactly what task you were working on and where you left off. This should be verbatim to ensure
there's no drift in task interpretation.

Here's an example of how your output should be structured:

<example>
Summary:
1. Primary Request and Intent:
   [Detailed description]

2. Key Technical Concepts:
   - [Concept 1]
   - [Concept 2]
   - [...]

3. Files and Code Sections:
   - [File Name 1]
      - [Summary of why this file is important]
      - [Summary of the changes made to this file, if any]
      - [Important Code Snippet]
   - [File Name 2]
      - [Important Code Snippet]
   - [...]

4. Errors and fixes:
   - [Detailed description of error 1]:
      - [How you fixed the error]
      - [User feedback on the error if any]
   - [...]

5. Problem Solving:
   [Description of solved problems and ongoing troubleshooting]

6. All user messages:
   - [Detailed non tool use, non subagent user message]
   - [...]

7. Pending Tasks:
   - [Task 1]
   - [Task 2]
   - [...]

8. Current Work:
   [Precise description of current work]

9. Optional Next Step:
   [Optional Next step to take]
</example>

Please provide your summary based on the conversation so far, following this structure and ensuring precision and thoroughness in your response.

[summarization-handler] Attempt started

[summarization-handler] Stripped non-printable characters from prompt on final input-limit retry

[summarization-handler] Expected prompt truncation after input limit reduction but prompt fit within reduced budget

[summarization-handler] Attempt succeeded

[summarization-handler] prompt guard did not reduce inputs enough

[summarization-handler] Error summarizing messages