CodeMesh (VS Code / Cursor / Windsurf)

CodeMesh cuts the tokens — and the cost — your AI agent burns understanding your codebase. Instead of an agent grepping and reading raw files turn after turn, CodeMesh answers code questions from a live, pre-built context graph of your repo and hands back just what's needed. The Analytics tab's default baseline (tunable, and backed by real usage where it's available — see below) assumes a ~95% cut in tokens and ~96% cut in cost versus that raw-read baseline; independently measured benchmark runs on real questions have landed anywhere from ~77% to ~95%+ depending on question difficulty and how the reduction is averaged — real numbers, not a single marketing figure.

Under the hood, CodeMesh keeps that graph — code structure, git history, and working-tree state — synced continuously from your machine, and serves it to you and your AI agents over MCP.

Getting started

Install the extension and open any git repository.
Click Sign In in the CodeMesh panel (browser OAuth — no passwords in the editor).
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, Windsurf, 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.

Configuration

Setting	Default	Purpose
`codemesh.appUrl`	`https://codemesh.cloud`	The CodeMesh app — sign-in, ingest, MCP, and the dashboard live behind this one origin. Point it at your own deployment to self-host.
`codemesh.daemonUrl`	`http://127.0.0.1:7077`	The local sync daemon (always on your own machine).
`codemesh.autoConnect`	`true`	Auto-connect every git repo opened in the editor.
`codemesh.ignoreRepos`	`[]`	Glob patterns for repos that must never auto-connect.
`codemesh.binaryPath`	bundled	Override the `codemesh-sync` binary (defaults to the platform binary shipped with the extension).

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.

Codemesh for VS Code

Codemesh