CodeMesh (VS Code / Cursor / Devin)

CodeMesh makes AI coding agents much cheaper to use.

AI agents normally waste a lot of money. They search your files again and again and read long chunks of code just to answer simple questions. That burns thousands of tokens and drives up your bill.

CodeMesh stops that waste. It builds a live knowledge graph of your real codebase — structure, git history, and current working tree — and keeps it updated automatically. When an AI agent asks a question, CodeMesh sends back only the small pieces that matter. The result is far fewer tokens used and much lower cost.

In normal use this can cut token use by about 95% and cost by about 96% compared with the old way of grepping and reading raw files. Real tests on actual questions have shown savings between roughly 77% and 95% or more, depending on how hard the question is. These are measured numbers, not marketing guesses.

Under the hood, CodeMesh keeps that graph in sync with the files on your machine and serves it to you and your AI agents through MCP.

Getting started

1. Install the extension and open any git repository.
2. Click Sign In in the CodeMesh panel (browser OAuth — no passwords in the editor).
3. That's it. Every git repo you open afterward auto-connects under the same account and starts syncing. The bundled codemesh-sync daemon is started and supervised automatically.

The panel

• Repos — live sync status per repository (branch, commit, errors).
• Add repos — connect more local or GitHub repositories; repos synced from other windows on this machine are listed too.
• Activity — ingestion history with node/relationship counts.
• Graph — what's actually in your graph, by type.
• MCP — connect your AI agents.

Connect your AI agents

The MCP tab has one-click Connect for Claude Code, Cursor, Devin, OpenCode, and Codex. Connect checks the agent is installed, verifies the connection live against your graph, and only then writes the agent's MCP config entry — "Connected" always means a passing handshake. Tokens are rotated automatically while the editor is open.

Any other MCP client can be pointed at the endpoints shown in the same tab.

How sync works

Sync follows your local filesystem: git hooks and editor events wake the daemon, which pushes deltas to your graph. Agents editing files locally (Claude Code, Codex CLI) wake the same daemon through hooks installed at connect time — an MCP connection alone reads the graph but does not sync files.