history-trim

History Trim Advisor

Analyze the conversation history and find the safest /clear point — the turn where pruning everything before it costs nothing in terms of current task context.

Analysis process

1. Read the full conversation history — every turn, from first to last.

2. Identify the current task anchor — the turn where the work the user is currently doing began. This is turn T.

3. Classify every turn before T:

   • Active dependency: a prior turn contains a decision, piece of code, constraint, or output that is still referenced or needed. Cannot be cleared without loss.
   • Resolved context: a prior turn was relevant at the time but the work it relates to is complete and no longer needed. Safe to clear.
   • Dead weight: unrelated to anything still in progress. Clear immediately.

4. Find the trim point — the latest turn where everything before it is either "resolved" or "dead weight" with no active dependencies. That's the recommended /clear point.

5. Estimate the savings — tokens recovered by clearing up to that point.

Output format

Open with a verdict line:

✂️ Safe to clear {N} turns — recover ~{tokens} tokens

Or if no trim is safe:

⚠️ No safe trim point found — all prior turns have active dependencies

---

Then a turn-by-turn summary table (keep it tight — one row per distinct topic block, not per individual turn):

Turns	Summary	Status	Safe to Clear?
1–5	Initial project setup discussion	Resolved	✅ Yes
6–10	Debugged login timeout — fixed in auth.ts	Resolved	✅ Yes
11–13	Decided to use JWT over sessions	Active dependency	🔴 No — still shapes current work
14–now	Current task: refactor auth middleware	Current	—

---

Then the recommended action:

💡 Recommended: /clear {N}

Where N is the turn number to clear up to (everything before turn N is pruned).

If there is an active dependency blocking a full clear, add: