OpenCode · Updated 2026-10-09
Reduce OpenCode Token Usage: Compress Tool Output
OpenCode sessions grow with every shell run, file read and MCP result. Here is where OpenCode tokens go and how SuperCompress lets the agent keep only the lines that answer your question.
/compact when a session gets long, short AGENTS.md. Then run npm install -g supercompress-proxy && supercompress setup to add the SuperCompress MCP server and instructions to OpenCode.
Where OpenCode tokens go
- Session history. Earlier tool results go back with later requests.
- Shell output and file reads. Full logs and full files.
- MCP servers and
AGENTS.md. Added to the session.
Habits that cut OpenCode token usage for free
- One task per session.
- Compact long sessions with
/compact. - Keep
AGENTS.mdshort. - Only enable the MCP servers you use.
These habits shrink what goes in. They don't help when the agent genuinely needs to run a test suite or read a large file and only a few lines of the output matter. That is the part SuperCompress handles.
How SuperCompress works
SuperCompress is hosted, extractive and query-aware. Your agent sends a large block of context (a log, a diff, a file read, an MCP result) together with the question it is working on. Our Neural Keep model scores the lines against that question, keeps the original lines that answer it, and drops the rest. It never rewrites or summarizes, so file paths, error messages, IDs and code come back exactly as they were. The question itself is never compressed.
Every compress call reports original_tokens and kept_tokens, so you can see what was dropped on your own work instead of trusting a headline number. The usage_summary MCP tool shows totals per agent for your account.
What supercompress setup adds to OpenCode
| What | Where | What it does |
|---|---|---|
| MCP server | ~/.config/opencode/opencode.json (mcp block) | Gives the agent the compress_context, connect_account and usage_summary tools. |
| Instructions | ~/.config/opencode/AGENTS.md | Tells OpenCode to compress bulky dumps with compress_context and never to compress the request itself. |
Install
npm install -g supercompress-proxy && supercompress setupSetup links your SuperCompress account in the browser, detects the coding agents on the machine and wires each one. Restart the agent so it loads the new MCP server. Then check what is wired up:
supercompress doctordoctor prints a per-agent health check. supercompress uninstall removes only the entries SuperCompress added. Setup backs up each config file before it edits it.
When to skip it
- Short sessions with small tool results. There is little to drop.
- Files the agent is about to edit line by line. It needs those in full.
- Work where every byte must be passed through unchanged for compliance reasons.
FAQ
Does SuperCompress change how I sign in to OpenCode?
No. You keep your normal OpenCode login and models. SuperCompress adds an MCP server and instructions to OpenCode; it does not route OpenCode's model traffic through a proxy.
Does SuperCompress summarize what OpenCode reads?
No. It is extractive. The lines it keeps are copied from the original output, so file paths, error messages and code stay exactly as they were.
How do I undo the OpenCode setup?
Run supercompress uninstall. It removes only the entries SuperCompress added, so your other MCP servers, hooks and instructions stay as they were.