Home › Graphify + Claude Code Integration

Graphify + Claude Code Integration

The deepest integration Graphify ships with is for Claude Code. One command installs both a CLAUDE.md directive and a PreToolUse hook, so Claude consults the knowledge graph before every file-search tool call — not after.

One-command install

pip install graphifyy
graphify install
graphify claude install   # from inside your project

That second command does two things:

The effect: Claude navigates by structure — god nodes, communities, surprising connections — instead of grepping every file. See why a graph beats flat search.

Other assistants

Codex, OpenCode, OpenClaw and Factory Droid don't support PreToolUse hooks, so Graphify writes the same rules to AGENTS.md in your project root. That's the always-on mechanism on those platforms.

PlatformCommandMechanism
Claude Codegraphify claude installCLAUDE.md + PreToolUse hook
Codexgraphify codex installAGENTS.md
OpenCodegraphify opencode installAGENTS.md
OpenClawgraphify claw installAGENTS.md
Factory Droidgraphify droid installAGENTS.md

Codex users also need multi_agent = true under [features] in ~/.codex/config.toml for parallel extraction. Factory Droid uses its Task tool for parallel subagent dispatch. OpenClaw currently runs sequential extraction.

Always-on vs explicit trigger

The always-on hook surfaces GRAPH_REPORT.md — a one-page summary of god nodes, communities and surprising connections. That covers most everyday orientation.

For precise, hop-by-hop traversals, use the explicit CLI commands: /graphify query, /graphify path and /graphify explain. They read graph.json directly and return edge-level detail with relation type, confidence score and source location.

Keeping the graph fresh

Two options:

Related topics