Codegraph Explorer

Lightweight VS Code navigation for projects that already use Codegraph. Search symbols, indexed file text, file paths, callers, callees, and impact from the dashboard, side bar, or graph view without leaving VS Code.

Install from the Visual Studio Marketplace or open VS Code Extensions and search for Codegraph Explorer.

Korean README

Why Install It

Codegraph Explorer is for developers who already have a .codegraph index and want to use that context without leaving VS Code.

• Search indexed symbols, file names, and text matches from the Activity Bar, dashboard, or graph view.
• Open results at exact file, line, and column positions.
• Inspect callers, callees, impact, files, and graph relationships.
• Use Graph Explorer to pan, zoom, focus, and inspect Codegraph relationships.
• Copy exact locations or agent-ready prompts when handing context to coding agents.
• Stay lightweight: this extension reads your existing Codegraph index instead of replacing your parser, indexer, MCP server, or agent workflow.

What's New in 0.0.62

• Search now supports Symbols, Text in files, File names, Callers, Callees, and Impact in the dashboard, side view, and Graph Explorer.
• The dashboard and side view now include clearer empty states with fast actions for sample search, indexed files, and file graph browsing.
• Graph Explorer controls now use consistent icon buttons and add a quick Copy location action for selected nodes.
• The update-history command was removed from the command palette and side view so the extension stays focused on search, graph, refresh, and bundled skill workflows.

Install

Marketplace:

datanewbie-labs.codegraph-index-explorer

VS Code:

1. Open Extensions.
2. Search Codegraph Explorer.
3. Choose the extension by DataNewbie Labs.
4. Click Install.

Quick Open:

ext install datanewbie-labs.codegraph-index-explorer

If this extension helps you move around Codegraph projects faster, please install it from the Marketplace and share Codegraph Explorer with other developers who use Codegraph.

Initial Setup

Codegraph Explorer activates when the opened workspace contains a .codegraph directory.

Requirements:

• VS Code 1.92.0 or newer.
• A trusted VS Code workspace.
• Node.js with npm, if the Codegraph CLI is not installed yet.
• The codegraph CLI available on PATH, or configured with codegraph.cliPath.
• A workspace initialized with Codegraph.

Install the Codegraph CLI first if codegraph --version is not found.

If npm is not found, install Node.js and npm first. Minimal Linux containers often do not include them.

Debian/Ubuntu:

apt-get update
apt-get install -y nodejs npm

Alpine:

apk add --no-cache nodejs npm

Fedora/RHEL:

dnf install -y nodejs npm

Windows PowerShell:

node --version
npm --version
npm install -g @colbymchenry/codegraph
codegraph --version

If PowerShell blocks the npm script shim, verify with codegraph.cmd --version and set codegraph.cliPath to the full codegraph.cmd path shown by where.exe codegraph.

macOS/Linux:

node --version
npm --version
npm install -g @colbymchenry/codegraph
codegraph --version

For a Debian/Ubuntu-based Dockerfile:

RUN apt-get update \
  && apt-get install -y --no-install-recommends nodejs npm \
  && npm install -g @colbymchenry/codegraph \
  && rm -rf /var/lib/apt/lists/*

If global npm installs need elevated permissions, prefer a user npm prefix over sudo:

mkdir -p ~/.npm-global
npm config set prefix ~/.npm-global
export PATH="$HOME/.npm-global/bin:$PATH"
npm install -g @colbymchenry/codegraph
codegraph --version

Basic setup:

codegraph --version
codegraph init

Then reopen the workspace in VS Code, or run Codegraph: Refresh from the Command Palette after the .codegraph directory exists.

If your CLI is not available as codegraph, set the path in VS Code settings:

{
  "codegraph.cliPath": "/absolute/path/to/codegraph"
}

Optional agent MCP setup:

codegraph install

For non-interactive agent setup, use:

codegraph install --target auto --location global --yes

The VS Code extension can read a local .codegraph index without MCP, but MCP setup lets supported coding agents call Codegraph tools directly.

MCP PATH Troubleshooting

If MCP logs say:

Connection failed: Executable not found in $PATH: "codegraph"

then Codegraph may be installed, but the MCP process cannot find it. For example, the binary may be at /root/.local/bin/codegraph while MCP is configured as "command": "codegraph" and the active PATH does not include /root/.local/bin.

Confirm:

printf '%s\n' "$PATH"
ls -l /root/.local/bin/codegraph 2>/dev/null || true
command -v codegraph || true

Ask before changing the environment. Then choose one fix:

# Option 1: symlink into a directory already on PATH
ln -s /root/.local/bin/codegraph /usr/local/bin/codegraph

# Option 2: add ~/.local/bin to future shells
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
export PATH="$HOME/.local/bin:$PATH"

Alternatively, edit the MCP config to use the absolute binary path, such as /root/.local/bin/codegraph. Restart or refresh the agent after changing PATH or MCP config.

Screenshots

Usage

Open a workspace that contains .codegraph, then use one of these entry points:

• Activity Bar: Codegraph
• Status Bar: Codegraph
• Command Palette: Codegraph: Open Dashboard
• Command Palette: Codegraph: Open Graph Explorer
• Command Palette: Codegraph: Search Symbols
• Keyboard: Ctrl+Alt+G on Windows/Linux or Cmd+Alt+G on macOS

The dashboard and side view show index status, indexed files, search results, and related Codegraph actions. Selecting a result opens the source file at the indexed location.

Search modes:

• Symbols searches Codegraph symbols and supports the kind filter.
• Text in files searches text inside files listed by the current Codegraph index.
• File names searches indexed file names and paths.
• Callers, Callees, and Impact search relationships for a symbol.

Graph Explorer opens in a separate panel and renders Codegraph relationships with pan, zoom, node dragging, focus mode, minimap, hover previews, and detail actions.

Commands

Settings

Index Freshness

The extension reads whatever the local Codegraph CLI reports. If your Codegraph setup automatically re-indexes code changes and writes updates into .codegraph, the extension can pick up those updates without rebuilding the index itself.

• Graph Explorer watches .codegraph/** while the panel is open. When index files change, it clears extension-side caches, refreshes index metadata, shows the index freshness label, and records activity.
• Graph Explorer shows freshness labels such as Index just now and Index 5m ago based on the newest known .codegraph database timestamp.
• Dashboard, side view, command palette search, and status bar reads use short CLI caches. Status and file caches live for about 5 seconds; search and relationship caches live for about 2 seconds.
• Codegraph: Refresh clears extension caches and reloads status/sidebar data.

The extension does not start or manage Codegraph auto-sync. That remains the responsibility of your Codegraph CLI, MCP, or daemon setup.

Positioning

Many CodeGraph-style extensions include their own parser, indexer, language server, MCP server, memory layer, or AI summary workflow. This extension is deliberately narrower:

• It activates only when a workspace already contains .codegraph.
• It calls the local codegraph CLI and renders the returned JSON.
• It focuses on fast navigation, indexed file discovery, callers, callees, impact, and graph browsing inside VS Code.
• It helps hand selected Codegraph results to coding agents by copying exact locations or a structured prompt.
• It stays small enough to use beside any existing Codegraph setup instead of owning the whole indexing pipeline.

This project is best described as a Codegraph index explorer and agent handoff tool, not an official Codegraph sub-extension.

Development

Install dependencies and copy the packaged webview dependency:

npm install
npm run sync:vis-network

Common development commands:

npm run compile
npm test
npm run test:extension
npm run package

Open this folder in VS Code and press F5 to launch an Extension Development Host.

Packaging

Create a local VSIX:

npm run package

Install the generated .vsix from VS Code with Extensions: Install from VSIX.

Before publishing publicly:

• Confirm the publisher value in package.json matches the Marketplace publisher account.
• Confirm repository, homepage, and issue tracker metadata point at the public GitHub repository.
• Run npm test.
• Confirm generated .vsix files, local .codegraph indexes, test artifacts, and node_modules are not committed.

Repository Contents

• src/ - extension source code.
• resources/ - packaged extension assets and bundled Codegraph skill.
• scripts/ - maintenance and validation scripts.
• test/ - unit, package, asset, graph, and extension smoke tests.
• CHANGELOG.md - release history.
• README.ko.md - Korean guide for users.

License

MIT