cgz is the Rust CLI in this repository. It builds and queries a local CodeGraph database under .codegraph/.

The crate lives at crates/codegraph. The workspace root is now a Rust Cargo workspace; the original TypeScript CodeGraph code is tracked separately on the original-codegraph/main branch.

cgz is a Rust rework of the original CodeGraph project. This repository keeps the upstream project's ideas and history in view while evolving the tool as a local-first Rust CLI and library.

cgz detects and indexes source files for these languages and file formats:

Framework-aware indexing currently includes MoonBit Sol route extraction, Liquid render/include/section references, and Vue/Svelte component and template references. Web framework route resolvers from the upstream TypeScript project are being ported intentionally; see docs/PORT_PARITY_MATRIX.md for current parity.

cgz init creates .codegraph/ in the target project. The database file is .codegraph/codegraph.db.

The default config includes source patterns for common languages plus MoonBit files:

• *.mbt
• *.mbti
• *.mbt.md
• moon.mod.json
• moon.pkg.json
• moon.pkg

The default excludes include .git, node_modules, vendor, dist, build, out, target, .codegraph, .moon, and .mooncakes.

cargo build -p cgz

Release build:

cargo build --release -p cgz

cargo test --all --all-features

cgz init [path]        # create .codegraph/
cgz init -i [path]     # create .codegraph/ and index
cgz uninit --force     # remove .codegraph/
cgz index [path]       # rebuild the index
cgz sync [path]        # sync changed files
cgz status [path]      # print file, node, edge, and DB size stats
cgz status --json      # print status as JSON
cgz query <search>     # search indexed nodes
cgz query <search> -j  # print search results as JSON
cgz files              # print indexed file counts by language
cgz context <task>     # print context for a task
cgz context <task> -j  # print context evidence as JSON
cgz affected <files>   # print affected test files from import dependents
cgz affected <files> -j # print affected test evidence as JSON
cgz serve --mcp        # start the MCP server
cgz unlock [path]      # remove .codegraph/codegraph.lock

Agents should start with cgz status <path> before relying on graph results. If a project is not initialized, cgz init -i <path> is a deliberate workspace-changing operation, not a read-only discovery step.

For day-to-day read-only exploration, use cgz files, cgz query, cgz context, and cgz affected. Treat their output as navigation context and finish with the target repository's normal tests, type checks, or build checks.

See docs/AGENT_WORKFLOW.md for the short playbook. See docs/AGENT_CONTEXT_EVAL.md for the automated context-success fixture used to guard agent navigation quality.

Running cgz with no subcommand currently prints:

Rust CodeGraph installer is not implemented yet. Run `cgz init -i` in a project.

The root justfile defines:

just release-check
just publish-cli
just release-tag
just release

release-check runs Cargo tests, builds the release binary, and runs cargo publish --dry-run for crates/codegraph/Cargo.toml.

Issues are managed locally as markdown files in the issues/ directory, rather than on GitHub Issues.

• Open issues live in issues/
• Closed issues are moved to issues/closed/
• Pending or blocked issues are moved to issues/pending/

File naming convention: {YYYY-MM-DDThhmmss}-{category}-{slug}.md

For the full issue workflow, see AGENTS.md.

This approach is inspired by shiguredo/http3-rs.