codegraph

CodeGraph

CodeGraph builds a local semantic graph of a codebase and exposes CLI commands for indexing, symbol search, task context, file structure, call relationships, impact analysis, and affected-test discovery.

Use this tool when a repository has or should have a .codegraph/ index and the task needs structural code intelligence: "where is this symbol", "how does this area work", "who calls this", "what might break if I change it", or "which tests are affected by these files".

IMPORTANT: How to Use This Tool

This is a dedicated built-in tool named codegraph. You MUST follow these rules:

1. Do NOT use shell_command to run CodeGraph commands. The gateway blocks attempts to run codegraph or npx -y @colbymchenry/codegraph through shell_command when this tool is enabled. Always use this codegraph tool.

2. Executing commands (skillToken required):

   • Every exec value MUST start with the codegraph prefix.
   • You MUST include the skillToken returned from reading this document.
   • Example: codegraph({"exec": "codegraph status", "cwd": "D:/project", "skillToken": "<token>"})

3. The gateway runs CodeGraph through npx. You write codegraph ..., and the gateway executes npx -y @colbymchenry/codegraph ... directly without a shell wrapper.

4. This is NOT the CodeGraph MCP server integration. Do not run codegraph serve --mcp. This built-in tool only supports selected CLI commands. Upstream MCP-only tools such as codegraph_trace, codegraph_explore, and codegraph_node are not available through this built-in tool.

Prerequisites

Node.js/npm must be installed so npx is available. The upstream npm package currently requires a supported Node runtime, and the first call may download or refresh the @colbymchenry/codegraph npm package cache.

Always set cwd to the project root or a directory inside the configured allowed directories. CodeGraph stores its local SQLite index under .codegraph/.