Developers

The short answer

Everything needed to get CodeMesh running and to know exactly what it does with your code: setup in four steps, how syncing actually works, connecting any MCP-capable agent, the full data policy, and the benchmark data behind every number on this site.

Set it up

Understand it

The console

Repositories, the graph, the agent connection and the activity log. Every tool call is listed with a preview of its arguments, which is how you find out what your agent has been asking for rather than guessing.

An organisation admin also sees per-member usage, storage and cost, and which repositories were indexed. Never the contents of those repositories.

Where you land. Whether every repository synced clean, how large the graph has grown, how many seats are in use, and which agents currently hold read access.

Workspace

Overview

DW
Workspace pulse

Your graph is healthy: 6 repositories syncing clean

No failed syncs, no drift detected.

Connect agent
Repositories
6
No new repositories this week
Code nodes
159,609
Relationships
267,508
Seats
5 / 8
2 pending
Recently synced

Repositories the daemon has pushed into your graph.

View all repositories →
RepositoryBranchLast syncedNodesStatus
OPopenclawmainjust now18,412OK
REreactmain4m ago31,204OK
DJdjangomain12m ago42,715OK
Connected agents

Applications authorized to read your graph.

Claude Codehandshake passed 2m ago
Connected
Cursorhandshake passed 18m ago
Connected
OpenCodehandshake passed 1h ago
Connected
Manage agents

Example workspace (Northgate Systems). The reduction shown is the published benchmark's 95.1%.

Guides and reference

The numbers

Start with the quickstart

Install, sign in, connect, ask. The free plan covers the whole loop.

Read the quickstartSee the Benchmark