200-message-ticket-thread-overflowed-t-8dbebd27771bcc60listed
Install: claude install-skill Vectle/skills
## TL;DR
A 200-message thread does not fit in the context window, and truncating from the front loses the original problem while truncating from the back loses the latest state. Summarize in chunks: compress older messages into a running summary, keep recent messages verbatim, and always preserve the key facts (ids, decisions, promises) structurally. The agent needs the story of the thread, not every word of it.
## The query
```text
200-message ticket thread overflowed the agent's context window: chunked summaries
```
## Use this when
- Agents fail or degrade on long threads
- Context limits cut off ticket history
- You are building agents that read tickets
- Debugging "the agent missed earlier context"
## Not for
- Configuring model context limits
- Ticket UI pagination design
- Choosing between LLM providers
- Ticket archiving policy
## Steps
### 1. Split the thread into chronological chunks
Divide the messages into chunks that each fit comfortably: older chunks get summarized, the newest chunk stays verbatim. Chronological order preserves the story; arbitrary splits lose it.
Expected output: chunked thread with a verbatim recent tail.
### 2. Summarize each older chunk with facts preserved
Summarize chunk by chunk, carrying forward a running summary. Instruct the summarizer to preserve identifiers, dates, decisions, and promises verbatim: these are the facts the agent will act on, and paraphrasing them introduces errors.
Expected output: running summaries with