Repo dump vs Hexum
Last updated 3 September 2026
| Repo dump | Hexum | |
|---|---|---|
| What the model sees | The repository, or a large slice of it | This turn, after hexum_shrink |
| 24-task context tokens | 220,393 | 27,352 |
| You keep | The editor | The same editor, plus MCP |
Numbers and method: how MBPP and HumanEval were run. Tiny prompts may save little.
FAQ
How does Hexum reduce tokens?
The agent calls hexum_shrink before it reads widely. The model is sent this turn, not the repository. On MBPP, measured context dropped about 85% with the same tests passing. Example turn: 18.2k → 3.1k tokens, 41 files → 6. See /benchmarks and /methodology.
What is Hexum?
Hexum is the control plane for coding agents. One hexum_live_ key authorizes hosted MCP on hexum.dev and on efficient, arch, review, control, and loop subdomains. hexum_shrink sends this turn instead of the repository. hexum_check fails a forbidden import without calling a model. On MBPP, context dropped about 85% with the same tests passing.
What is tokens saved?
Tokens in minus tokens out, when that is positive. Stripe is billed on tokens saved. Calls that do not save tokens still increment calls and the in/out counters.