Overview
Tokens Kompactor kept out of Claude's context, turn by turn.
Saved per turn
Each bar is one Claude reply; the latest is highlighted. Hover for before and after.
Biggest wins
Commands whose output shrank the most
Where savings come from
Tokens saved by feature
Replay your history
Run your past Claude Code sessions through the current settings. Nothing leaves this machine.
Quality vs tokens
One level sets everything. Toward quality, Claude sees more raw output; toward savings, less.
Live preview
Exactly what Claude would receive for realistic Python, Go, React and TypeScript output
In Claude Code
How savings are shown. These don't depend on the level.
Show savings after each turn
A one-line summary after every Claude reply, such as "−8.2k tokens this turn".
Status line
Running savings in the Claude Code terminal status line. Never replaces a status line you already have.
Keep history for
Savings history and stashed raw outputs older than this are deleted.
days
Code graph
Functions, classes, imports and calls, indexed on this machine so Claude finds code without reading whole files.
Projects & languages
Give a repo its own level, and choose how languages are detected.
Languages
Profiles decide which files open as outlines, which count as generated, which stack frames are library noise and which lock files collapse in diffs.
Detection
Auto-detect reads pyproject.toml, go.mod, package.json and tsconfig.json in each repo.
Projects
Every repo used with Kompactor. A project can override the global level.
Setup
The Claude Code CLI and the VS Code extension read the same settings file, so one switch covers both.
Self-test
Runs every installed hook exactly as Claude Code would, in an isolated folder
Not run yet.