Your agent rereads the same context every turn. You pay for it every time.
Caveman Proxy makes that context smaller on your machine before it leaves. The original bytes stay local, so nothing is lost.
$ caveman wrap claudeGo · BSL-1.1 · local compression is free, no accountOne task, the same bytes, again and again. Instructions, history and tool results ride along on every turn.
By turn five, almost everything in the request is a copy of something you already paid to send.
schematic · the shape of a task, not a measurementThe proxy sits on your machine. Context goes in wide and leaves narrow.
original bytes stored locally before lossy replacement · recoverable
schematic · widths show the idea, not a measured ratio · prompts and responses go to your provider, not to us
One command wraps the agent you already use. Nothing else about your setup changes.
- Claude Code
- Codex
- Gemini
- Aider
Traffic from a registered agent routes through the local proxy. Everything else is left alone.
- Logsrepeated lines, timestamps, stack frames
- JSONkeys and structure kept, bulk shortened
- Tablesrows read as rows, not as prose
- Codesyntax survives; the shape stays readable
- Diffshunks and paths kept intact
- Terminal outputlong runs of build and test noise
It refuses to touch anything it cannot put back. Fail-closed, every time.
- 01If the content will not parsepasses through unchanged
- 02If no recovery entry can be writtenpasses through unchanged
- 03If the result is not smallerpasses through unchanged
Compression only happens when the content parses, a recovery entry is written, and the result is actually smaller. Otherwise the original bytes go through untouched. The proxy can cost you a compression. It cannot cost you a request.
We label an estimate as an estimate.
- inferred
- Local token reductions are estimates. They are labeled inferred, never printed as verified savings.
- recoverable
- Original bytes are stored locally before any lossy replacement, so the agent can retrieve the exact detail later.
- free, locally
- Local compression needs no Caveman account. Signing in adds analytics and team features; it never controls compression.
- your provider
- Prompts and responses go to the provider you already chose. Compression and recovery stay on your machine.