Comparison · Updated 2026-10-31
SuperCompress vs claude-token-efficient
Short answer: claude-token-efficient is instruction file (CLAUDE.md rules). Where it runs: Inside Claude Code, as a project file. SuperCompress is hosted, query-aware compression that keeps the original lines answering the current question. Pick claude-token-efficient if you want the lightest possible experiment in Claude Code with nothing to install. Pick SuperCompress if your agent keeps pulling big tool results, logs or retrieved docs and only a few lines matter for the question at hand, and you want those lines kept verbatim.
Side by side
| claude-token-efficient | SuperCompress | |
|---|---|---|
| What it optimizes | Model output style | Input context (tool output, logs, files, MCP results, RAG) |
| How it decides | Instruction file (CLAUDE.md rules) | Query-aware extraction of original lines |
| Where it runs | Inside Claude Code, as a project file | Hosted API, plus an MCP tool and hooks for coding agents |
| Setup | Copy CLAUDE.md into your project root | npm install -g supercompress-proxy && supercompress setup |
| Licence | Open source | Hosted service |
claude-token-efficient
A. claude-token-efficient
Best if you want the lightest possible experiment in Claude Code with nothing to install.
A drop-in CLAUDE.md with compact behaviour rules that suppress filler, restated questions and over-engineering in Claude Code replies.
- How it works: Instruction file (CLAUDE.md rules)
- Runs: Inside Claude Code, as a project file
- Setup:
Copy CLAUDE.md into your project root - Licence: Open source
Strengths:
- Nothing to install or audit
- Easy to tweak or remove
- Free
Limitations:
- Claude Code only
- The file itself adds input tokens every turn
- Does nothing about file reads, command output or MCP output
SuperCompress
B. SuperCompress (our product)
Best if your agent keeps pulling big tool results, logs or retrieved docs and only a few lines matter for the question at hand, and you want those lines kept verbatim.
Hosted, query-aware context compression. Your agent or app sends a bulky block (tool output, a log, a diff, a file read, an MCP result, retrieved docs) with the current question, and the hosted Neural Keep model keeps the original lines that answer it, word for word, and drops the rest.
- How it works: Query-aware extraction of original lines
- Runs: Hosted API, plus an MCP tool and hooks for coding agents
- Setup:
npm install -g supercompress-proxy && supercompress setup - Licence: Hosted service
Strengths:
- Keeps original lines verbatim, so error messages, paths, IDs and code survive exactly
- Query-aware: what is kept depends on the current question, not only on the content type
- One setup command wires an MCP tool into each detected coding agent (Claude Code, Cursor, Codex, Windsurf, Cline, Gemini CLI, OpenCode and more), plus hooks where supported
- HTTP API returns original_tokens and kept_tokens so you can measure on your own traffic
- Works with any model provider because the output is plain text
Limitations:
- Hosted: the context you compress is sent to the SuperCompress API
- Compresses input only; it does not change how verbose model replies are
- Not a code index or retrieval system; it shrinks what is already being sent
How to test any of these fairly
Every tool here, including ours, publishes its own numbers. Fewer tokens do not always mean a smaller bill once prompt caching, retries and extra agent turns are counted. Run the same tasks with and without a tool, check the tasks still succeed, and compare cost per finished task on your provider bill.
Disclosure: SuperCompress publishes this page and is listed first because it is ours. Every claim about other tools comes from their own docs or repositories as of 2026-10-31; tell us if anything is out of date and we will fix it.
See also: claude-token-efficient alternatives, all comparisons.
FAQ
Is SuperCompress better than claude-token-efficient?
They solve different parts of the problem. Best if you want the lightest possible experiment in Claude Code with nothing to install. Best if your agent keeps pulling big tool results, logs or retrieved docs and only a few lines matter for the question at hand, and you want those lines kept verbatim.
What is the main difference between SuperCompress and claude-token-efficient?
claude-token-efficient works on model output style and runs inside claude code, as a project file. SuperCompress works on input context and is hosted.
Can I use both?
Usually, if they act on different tokens. Measure cost per finished task with each on and off.