Troubleshooting
“CodeGraph not initialized”
Section titled ““CodeGraph not initialized””Run codegraph init in your project directory first.
Indexing is slow
Section titled “Indexing is slow”Check that node_modules and other large directories are excluded (they are, if gitignored). Use --quiet to reduce output overhead.
MCP hits database is locked
Section titled “MCP hits database is locked”Current builds shouldn’t: CodeGraph bundles its own Node runtime and uses Node’s built-in node:sqlite in WAL mode, where concurrent reads never block on a writer. If you still see it:
- You’re on an old (pre-0.9) install. Reinstall to get the bundled runtime —
curl -fsSL https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.sh | sh(macOS/Linux),irm https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.ps1 | iex(Windows), ornpm i -g @colbymchenry/codegraph@latest. codegraph statusshowsJournal:other thanwal— WAL couldn’t be enabled on this filesystem (common on network shares and WSL2/mnt), so reads can block on writes. Move the project (with its.codegraph/folder) onto a local disk.
MCP server not connecting
Section titled “MCP server not connecting”Ensure the project is initialized/indexed, verify the path in your MCP config, and check that codegraph serve --mcp works from the command line.
Missing symbols
Section titled “Missing symbols”The MCP server auto-syncs on save (wait a couple of seconds). Run codegraph sync manually if needed. Check that the file’s language is supported and isn’t excluded by .gitignore.