MCP server that gives Claude Code the rationale behind a symbol before editing - synthesized from git history, PRs, and call-graph context.
This repository also configures its own agents. See what whygraph tells them →
Agent Claude Code
WhyGraph plan executor. Reads a reviewed plan markdown, applies each step in order, runs the per-step Verify, and logs progress back into the plan. Spawned by the /whygraph-implement slash command — do not invoke for unrelated work.
Agent Claude Code
WhyGraph planning orchestrator. Given a code-change task, builds a working set of affected symbols via CodeGraph, warms WhyGraph rationale cache, then either writes a plan (single-pass mode) or fans out to 3 researchers + a synthesizer (deep mode). Spawned by the /whygraph-plan slash command — do not invoke for…
Agent Claude Code
WhyGraph fan-out researcher. Investigates one specific dimension of a planned code change (impact, constraintsrisks, or priorart) using WhyGraph + CodeGraph MCP tools. Spawned in parallel with sibling researchers by the whygraph-planner in deep mode — do not invoke directly.
Agent Claude Code
WhyGraph fan-in synthesizer. Combines reports from 3 fan-out researchers (impact, constraintsrisks, priorart) into a single step-by-step implementation plan in WhyGraph's standard format. Spawned by the whygraph-planner in deep mode after researchers complete — do not invoke directly.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: