Working setup, four steps
The short answer
Install the extension, sign in from the panel, connect your agent, ask it something about your repository. Syncing needs no configuration: signing in starts it. The only step that needs a decision from you is which repositories to connect.
1. Install
One extension for VS Code, Cursor and Devin. From the command palette:
> ext install codemesh.vscode-codemeshOpen CodeMesh from the activity bar and you get the panel shown here. Offline builds and the full detail are on install the extension.
2. Sign in from the panel
Click Sign in, authorise in the browser that opens, and you are back in the editor. No password is typed inside your editor.
3. Let it sync, and pick your repositories
The repository open in that window starts syncing immediately. Everything else is a choice you make in the repositories view: what is connected, and which repositories your agent may read from this window. Files in .gitignore are skipped unless you include them for that repository.
The console shows the same information as the panel, plus what it is costing you. These are the screens you will actually live in.
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.
Example workspace (Northgate Systems). The reduction shown is the published benchmark's 95.1%.
4. Connect your agent and ask
Click Connect next to your agent. CodeMesh writes its MCP entry, installs its instructions and proves the connection with a handshake. Then ask your agent something it would previously have had to go reading for.
Good first questions are the ones with a single correct answer buried somewhere annoying: where a value is configured, what calls a function, which module owns a behaviour. The replies beside this are that shape.
Where to go next
How sync works
The daemon, the re-parse and the graph update, from your save to your agent's answer.
Connect your agent
What Connect writes, how the handshake proves it, and notes for each agent including ones the panel does not list.
Data policy
What is read, where it lands, what is recorded about your use, and what never happens.
FAQ
The questions that come up once people are past setup and into using it daily.
How long does this take?
Do I need a paid plan to try this?
How will I know it is working?
Start with a free account
One repository and one agent is enough to see whether it changes anything for you.