Headroom
Headroom is a local context-compression layer for tool outputs, logs and structured data. Its Python library can shorten representations before a separate model call, while optional MCP and proxy integrations expose other entry points. Default compression and the verified lossless agent mode have different retention behavior.
On November 7, 2026, we ran 18 library cases and 12 real stdio MCP tool calls with published version 0.43.1. Repetitive logs and uniform arrays shrank, selected structured outputs decoded to exact canonical JSON, and a dedicated SQLite workspace recovered original Unicode content after process restart. A compact sample of 80 real catalog records saved nothing in either mode, while lossless mode returned an unshortened log.
The release requires Python 3.11+. Our tested environment used x86_64 Python 3.13.1 on macOS and a binary-only dependency install after a native-build failure. Tokenizer vocabularies were prepared separately, the ML compressor was disabled, and runtime used offline settings. We did not measure model answers, provider bills, prompt-cache savings, agent wrapping or TypeScript integration; recoverability depends on the backend and entry lifetime.
Read the full review, verification scope and sources →Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-11-04
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 14
- Latest release
- v0.42.0 (2026-10-26)
- Open issues
- 392
- Recent issues with at least one comment
- 2/7
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Who it fits
- Your actual serialized tool output contains repetitive logs or uniform arrays, and you can compare both compression modes against minified baselines.
- You can retain originals in an appropriate backend, inspect application-level errors and verify the data needed by your task.
- You require demonstrated answer equivalence or a guaranteed billing reduction; this offline review measured neither.
- Your payloads are already compact heterogeneous JSON, or you require permanent recovery from an in-memory session; our controls exposed limits in those cases.
How it differs
Ref trims documentation it fetches from its hosted index. Headroom processes supplied content locally; this review tested logs and structured tool results.
jCodeMunch avoids reading whole code files by fetching symbols. Headroom compresses tool output, logs and JSON after they are produced.
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!