LIFEHUBBER
Theme

AI Resources

CodeGraph

GitHub stars: 69.1K GitHub forks: 4.4K Declared license: MIT: MIT Last pushed August 31, 2026: Pushed 1d ago
Stats from GitHub

CodeGraph is a local codebase knowledge graph for coding agents.

The repository presents CodeGraph as a local, auto-updating code intelligence layer for coding agents, with a Rust parsing engine, MCP tools, symbol relationships, call graphs, framework-aware routes, and a SQLite-backed index. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.

What it is

Local semantic code context

CodeGraph builds a local index of a repository so coding agents can ask for code structure, related symbols, callers, callees, and impact information instead of repeatedly scanning files from scratch.

Why it stands out

Agent-oriented repository understanding

The installer can connect CodeGraph to several coding agents, while each project keeps its own local graph and updates it as files change.

Availability

Standalone and npm setup paths

The public materials include standalone installers that do not require Node.js, an npm option, agent wiring, documentation, tests, language notes, and benchmark methodology.

Why it matters

What makes it useful

Coding agents need repository context before they can make useful changes. CodeGraph gives them a local map of symbols, call paths, routes, and likely impact, then keeps that map in step with file changes.

Notable points

What stands out

The current project uses a native Rust parsing engine, supports more than 20 languages, auto-syncs file changes, and publishes benchmark details. Its own measurements also warn that dense graph results can leave more context in a long-running chat even when total processing falls.

Before using

What to review

How the installer changes agent configuration files, how to reverse those changes, and which project folders will receive a local index.

The benchmark methodology and project-reported savings before applying the cost, token, time, or tool-call numbers to a different repository.

The extra context that graph results may leave in a long session, especially when the available context window is small.

Which languages, frameworks, routes, and code-search patterns match the repositories the reader actually works with.

Reader fit

Who may find it relevant

Readers using coding agents such as Claude Code, Codex, Cursor, OpenCode, or Hermes Agent.

Builders who want local codebase context, call graphs, impact analysis, or route-aware repository maps for agent work.

Less relevant for readers looking mainly for a general chatbot, hosted coding assistant, or non-code RAG system.

Editorial note

Why LifeHubber lists it

CodeGraph is included for its local, auto-updating map of repository symbols, call paths, routes, and likely impact. For readers working in large repositories, the decision is whether that persistent graph context is worth adding to the workflow.

Source links

Source materials

Reader note

Before relying on this entry

LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.

What to explore next

Compare how coding agents map a repository.

CodeGraph uses a local database and MCP tools. These alternatives show a file-based graph and another persistent code-map approach.

Advertisements

Advertisements

For project maintainers

Listed here? You can use the badge.

If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.

See what’s moving