Tired of replays to start new agent sessions that eat tokens..150k to 1k open source compressor /acc

\*\*\*Not promoting a commercial product\*\* Built an open source MIT licensed Claude Code skill called \*\*acc\*\* for ending a session and not having to re-explain it to the next one. Long sessions end and the next thread starts cold. Auto-compaction summarizes away the load-bearing parts (the decisions, what you already tried and ruled out), so even a "compacted" replay loses the most expensive context. acc writes a small artifact at the end of a session that the next thread loads as inherited context. Replay isn't necessary anymore. Average run: about 150k tokens of conversation down to about 1k. The artifact is at most 800 words, in five fixed sections: • \*\*Decisions\*\* (what got decided, and why) • \*\*Current State\*\* (files, branches, versions, tests) • \*\*Open Questions\*\* (what's blocked) • \*\*Rejected Approaches\*\* (what was tried and ruled out) • \*\*Next Actions\*\* (ordered, specific enough to execute) That fourth one is the one most handoff tooling drops. Auto-compaction tends to summarize away "we tried X, it failed because Y", and then the next session re-tries X. acc captures that on purpose. Negative knowledge is the most expensive class of facts to rediscover, so it gets a first-class slot. The second bet: a Step 0 necessity gate that aborts production if a plain HANDOFF.md would carry the same load. Most session-handoff skills always produce. This one asks if it should. The worst thing a productivity tool can do is run on momentum and dilute its own archive, so the gate fires often by design. Other tools in this space (mem0, Zep, REMvisual/claude-handoff) are mostly retention-maximalist. acc is the lossy-digest end of that trade-off. If your handoffs already work, you don't need it. That's what the gate is for. <https://github.com/haremantra/acc>