mksglu/context-mode
Context Mode keeps bulky tool output outside an agent’s prompt and restores relevant session state after compaction. Its MCP tools and hooks support 17 clients, though enforcement varies by platform.
Context Mode reports shrinking **315 KB to 5.4 KB** by running tool work in a sandbox and returning only selected results. It records edits, Git operations, tasks, errors, and decisions in SQLite, then uses **FTS5 with BM25** to retrieve relevant state after compaction.
For long coding-agent sessions, route large reads, searches, and fetches through its execution and indexing tools, then run its doctor checks. Hook-capable clients can enforce routing automatically; MCP-only installs expose **11 tools** but rely on the model to choose them.
Context Mode reports shrinking **315 KB to 5.4 KB** by running tool work in a sandbox and returning only selected results. It records edits, Git operations, tasks, errors, and decisions in SQLite, then uses **FTS5 with BM25** to retrieve relevant state after compaction. For long coding-agent sessions, route large reads, searches, and fetches through its execution and indexing tools, then run its doctor checks. Hook-capable clients can enforce routing automatically; MCP-only installs expose **11 tools** but rely on the model to choose them. The **98% reduction** is a project-reported example, not an independent benchmark. Installation and hook coverage differ across the 17 supported clients, and Cursor’s marketplace plugin was still awaiting review in the supplied material.
This combines context reduction with durable, searchable execution history: large tool outputs stay outside the prompt while selected facts and recorded decisions can be retrieved after compaction. It advances beyond one-way compression, but the reported reduction remains local evidence, retrieval quality is unproven, and MCP-only clients depend on the model consistently choosing the routing tools.