From 102bed2a8a63a3a4db9ca25e9ccec8b7ce6358a4 Mon Sep 17 00:00:00 2001 From: Zengwenliang0416 Date: Tue, 30 Jun 2026 23:23:07 +0800 Subject: [PATCH] docs: clarify WSL daemon socket fallback --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7b6c33932..256d0dddc 100644 --- a/README.md +++ b/README.md @@ -759,7 +759,7 @@ Framework routing is validated the same way, on a canonical app per framework: E **MCP server not connecting** — Your agent starts the server itself, so you don't launch it by hand. Make sure the project is initialized and indexed (`codegraph status`) and that the path in your MCP config is correct. If it still won't connect, re-run `codegraph install` to rewrite the config. -**MCP tool calls fail with `Transport closed` while `codegraph status`/`sync` are healthy** — almost always WSL2 with the project on a Windows drive (a `/mnt/c` or `/mnt/d` path), where the local socket CodeGraph uses to share one background server across sessions is unreliable. CodeGraph now falls back to serving the session in-process instead of dropping the connection, but if you still hit it, set `CODEGRAPH_NO_DAEMON=1` in your MCP server's environment to skip the shared server entirely (each session runs in its own process). Moving the project onto the Linux-native filesystem (e.g. under `~/` instead of `/mnt/`) restores the shared server. +**MCP tool calls fail with `Transport closed` while `codegraph status`/`sync` are healthy** — first make sure you're on a current build. WSL2 projects on Windows drives (`/mnt/c`, `/mnt/d`, etc.) are the most common trigger: those mounts may not reliably host the local socket CodeGraph uses to share one background server across sessions. Current builds handle the common cases automatically: if the project filesystem cannot host the socket, the shared daemon relocates it to the system temp directory; if a daemon connection still drops, the MCP session falls back to serving itself in-process instead of closing. If failures persist, set `CODEGRAPH_NO_DAEMON=1` in your MCP server's environment to skip the shared server entirely (each session runs in its own process). Moving the project onto the Linux-native filesystem (e.g. under `~/` instead of `/mnt/`) also restores the shared server. **Missing symbols** — The MCP server auto-syncs on save (wait a couple seconds). Run `codegraph sync` manually if needed. Check that the file's language is supported and isn't inside a `.gitignore`d or default-excluded directory (e.g. `node_modules`, `dist`).