Release notes

FEATURE

Session handoffs filter out noisy tool injections and correctly deduplicate task history

When you resume a previous conversation, the "what you were recently working on" suggestions will no longer be overwhelmed by giant walls of tool documentation. Previously, the system blindly scooped up every transcript entry marked as a "user" message, failing to realize that some of these were actually long instructions injected by the system itself to expand skills (skill files that help execute specific tasks). This allowed noisy text to masquerade as your real work progress. Furthermore, because the system only checked for duplicates against the very last message, a single real request interrupted by one of these noise entries would get counted twice, wasting your precious three handoff slots. The system now correctly skips these system-injected metadata entries (isMeta) and checks for duplicates against the entire list. It's like asking an assistant to summarize yesterday's meeting: they used to copy down an entire 100-page manual you happened to read aloud as if it were a decision, and if you repeated a point twice they logged it as two separate tasks. Now, they know to extract only the actual action items and merge repeats into a single line.

Original changelog

Original changelogSession handoffs filter out noisy tool injections and correctly deduplicate task history
**Session-resume handoff could surface skill-expansion noise and duplicate the same request**: `usage_session_resume.py`'s `_parse_session` collected every `type: "user"` transcript entry as a candidate "recently working on" request without checking Claude Code's `isMeta` flag, so skill/command expansions injected into the transcript (e.g. a full `SKILL.md` body) could show up as if they were a real request. Dedup also only compared against the immediately preceding request, so the same request separated by one of these injected entries counted twice, wasting handoff slots that are capped at 3. `isMeta: true` entries are now skipped, and dedup checks against every request seen so far, not just the last one. (Reported in #46 by @apple8409.)