GraphMind Code Graph

What does this agent do, and when should you use it?

GraphMind is a local-first code intelligence system whose Rust core uses tree-sitter to build function- and file-level knowledge graphs stored in SQLite and JSONL. It is delivered as a CLI, a macOS desktop application, and a stdio MCP server for Claude Code, Claude Desktop, Cursor, Windsurf, Cline, Zed, Continue, VS Code, and other MCP clients. Retrieval combines FTS5, optional semantic embeddings, and one-hop graph expansion, with Reciprocal Rank Fusion producing compact ranked symbol results. Beyond source structure, it maintains persistent records of decisions, patterns, conventions, bugs, and context, and it can link multiple registered repositories. The default configuration opens no ports, sends no telemetry, and makes no network calls; embeddings can run through local ONNX or optional OpenAI and Voyage AI services. Core functionality is MIT-licensed, while team graph and shared-memory synchronization are identified as Pro/Team features.

A user registers and indexes a repository with graphmind init. The Rust core parses supported files with tree-sitter, extracts symbols, call sites, and dependency edges, then writes the structural graph and FTS5 index to ~/.graphmind/graphs/<slug>/graph.db with an incremental build cache. When an embedding provider is configured, graphmind build also creates vectors in embeddings.db; graphmind search fuses full-text matches, cosine-similarity results, and neighboring graph nodes with RRF. CLI commands and MCP tools can inspect symbols and full functions, read files, map dependencies, traverse callers, estimate the impact of Git changes, detect cycles and dead code, and export Mermaid, DOT, JSON, or Obsidian output. Its memory layer records decisions, patterns, conventions, bugs, and contextual facts in project or global JSONL files, with automatic recall through Claude Code hooks or MCP instructions. Cross-project commands search all registered repositories, infer shared-symbol relationships, and report dependencies between projects.

1. A maintainer of a large repository checks graphmind fn-impact or graphmind diff-impact before changing a widely used function.
2. A team using Claude Code or Cursor wants assistants to query symbols, call relationships, and architecture without repeatedly reading the whole repository.
3. Engineers responsible for an API, frontend, and shared libraries search symbols across registered projects and trace inter-project dependencies.
4. A developer onboarding to an unfamiliar codebase inspects connected files, hierarchical outlines, dependency cycles, and symbols with no incoming edges.
5. Individuals or teams preserve architecture decisions, coding conventions, known bugs, and business context across separate AI sessions.
6. An architect exports a repository or cross-project graph to Mermaid, Graphviz DOT, JSON, or an Obsidian vault.

How do you install or deploy this agent?

On macOS, download GraphMind-macos-arm64.dmg or GraphMind-macos-x64.dmg from GitHub Releases. The desktop application installs the CLI and provides guided setup for MCP, hooks, the skill, and embeddings.

On macOS or Linux, use the installation script:

curl -fsSL https://raw.githubusercontent.com/aouicher/graphmind/main/scripts/install.sh | bash

Alternatively, install the CLI with Homebrew:

brew install aouicher/graphmind/graphmind

The macOS desktop application is also available through Homebrew:

brew install --cask aouicher/graphmind/graphmind

Linux x64 users can download the CLI directly:

curl -fsSL https://github.com/aouicher/graphmind/releases/latest/download/graphmind-cli-linux-x64 -o ~/.local/bin/graphmind
chmod +x ~/.local/bin/graphmind

Building from source requires Rust and Cargo:

git clone https://github.com/aouicher/graphmind
cd graphmind
cargo build --release -p graphmind-cli
cp target/release/graphmind ~/.local/bin/

Embeddings are disabled by default, so no API credential is required for the initial setup. OpenAI or Voyage AI keys must be added to ~/.graphmind/config.json only if those embedding modes are selected.

How do you use this agent?

Run the global setup once, then initialize each repository:

graphmind setup
cd ~/projects/myapp
graphmind init

setup configures the shell path, Claude Code hooks and skill, and MCP settings for Claude Desktop, Claude Code, OpenCode, and Cursor. init registers the current directory, installs Git hooks, builds the graph, and writes supported project-level MCP configuration. Both commands are documented as idempotent.

After indexing, query the project from the terminal:

graphmind search "authentication flow"
graphmind fn validate_token --include-content
graphmind deps src/services/auth.ts
graphmind diff-impact
graphmind dead-code --kind function
graphmind cycles
graphmind export -f mermaid

Persistent project knowledge can be managed explicitly:

graphmind memory add "Authentication tokens are validated by AuthService"
graphmind memory search "authentication"
graphmind memory list

To enable embeddings without an API key, select the local provider:

{
  "embedding": {
    "mode": "local",
    "model": "nomic-embed-text-v1.5"
  }
}

Then generate the index:

graphmind embed --run

MCP clients launch the stdio server with:

graphmind mcp

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ