main.js · part 97

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

File contents and all parts · All files

[TransportFactory] Deferring abort of retired HTTP/2 session manager with open streams (retired ${s}s ago)

Retired HTTP/2 session manager abort deferred (open streams)

[TransportFactory] Aborting retired HTTP/2 session manager (state=${n}, retired ${s}s ago)

use strict

unsupported response encoding "${p}"

HTTP ${r}

unsupported content type ${a}

Symbol.asyncIterator is not defined.

Symbol.asyncIterator is not defined.

protocol error: received extra EndStreamResponse

protocol error: received extra message after EndStreamResponse

protocol error: missing EndStreamResponse

use strict

use strict

use strict

Unexpected character at index ${o}

Unexpected character at index ${o}

The "${n}" subprotocol is duplicated

Unexpected end of input

The "${i}" subprotocol is duplicated

use strict

 prober hit error at byte 

use strict

Response status code ${i}${a?`: ${a}`:""}

Response status code ${i}${a?`: ${a}`:""}

Response status code ${i}${a?`: ${a}`:""}

Response status code ${i}${a?`: ${a}`:""}

use strict

use strict

Cursor Agent

Co-authored-by: ${o} <${n}>

Made-with: Cursor

co-authored-by: ${o.toLowerCase()}

use strict

PiBashToolCall|1 args #0|2 result #1

PiBashToolArgs|1 command 9|2 timeout 1?

PiBashToolResult|1 success #0 result|2 error #1 result

PiBashToolSuccess|1 output 9|2 truncation #0?|3 full_output_path 9?

PiBashToolError|1 error 9|2 truncation #0?|3 full_output_path 9?

use strict

use strict

Wall time to compute max-min fair character allocations during prompt truncation

[${e} message(s) omitted due to size limits; omitted content may appear anywhere in the conversation. See transcript file for full history.]

[omitted ${n[e]} message, ${s} chars]

[... truncated, ${s.length} chars]

### Transcript location:
  This is the full JSONL transcript of your past conversation with the user (pre- and post-summary): ${(0,w.join)(e,function(e){const t=`${b.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:
${k(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