compaction.ts · part 1

19 text occurrences from packages/core/src/session/compaction.ts, part 1. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

Output exactly the Markdown structure shown inside <template> and keep the section order unchanged. Do not include the <template> tags in your response.
<template>
## Objective
- [one or two brief sentences describing what the user is trying to accomplish]

## Important Details
- [constraints/preferences, decisions and why, important facts/assumptions, exact context needed to continue, or "(none)"]

## Work State
### Completed
- [finished work, verified facts, or changes made; otherwise "(none)"]

### Active
- [current work, partial changes, or investigation state; otherwise "(none)"]

### Blocked
- [blockers, failing commands, or unknowns; otherwise "(none)"]

## Next Move
1. [immediate concrete action, or "(none)"]
2. [next action if known, or "(none)"]

## Relevant Files
- [file or directory path: why it matters, or "(none)"]
</template>

Rules:
- Keep every section, even when empty.
- Use terse bullets, not prose paragraphs.
- Preserve exact file paths, symbols, commands, error strings, URLs, and identifiers when known.
- Do not mention the summary process or that context was compacted.

The <prior-summary> summarizes everything that happened before the <conversation>. Construct a new summary that combines both. The <prior-summary> is discarded after this: anything you do not carry into the new summary is lost.

When combining:
- Carry forward objectives, constraints, user directives, decisions, and parallel workstreams from the <prior-summary> even when the <conversation> does not mention them. Drop only what is finished and no longer needed.
- The <conversation> is more recent than the <prior-summary>. Where they conflict, the conversation wins: state the corrected fact and drop the old claim.
- Add new progress, decisions, constraints, and context from the conversation.
- Move completed work from "Active" to "Completed".
- If a blocker has been resolved, update the summary to reflect that while keeping any details still needed to continue the work.
- Update "Objective" and "Next Move" to reflect the current work state.

${value.slice(0, TOOL_OUTPUT_MAX_CHARS)}\n[truncated]

[Attached ${item.mime}${item.name === undefined ? "" : `: ${item.name}`}]

[Attached ${file.mime}: ${file.name ?? file.uri}]

[User]: ${message.text}

[Assistant]: ${part.text}

[Assistant reasoning]: ${part.text}

[Assistant tool call]: ${part.name}(${input})

[Tool result]: ${truncate(serializeToolContent(part.state.content))}

[Assistant tool call]: ${part.name}(${input})

[Tool error]: ${part.state.error.message}

[Assistant tool call]: ${part.name}(${input})

[System update]: ${message.text}

[Synthetic context]: ${message.text}

[Shell]: ${message.command}\n${truncate(message.output)}

Here is the conversation so far:\n\n<conversation>\n${input.context.join("\n\n")}\n</conversation>

Create a new anchored summary from the conversation history in the <conversation> tags above so another coding agent can continue the work.

Here is the summary of the conversation before the <conversation> above:\n\n<prior-summary>\n${input.previousSummary}\n</prior-summary>