Causalist

Surfaces

Causalist ships three ways to invoke it, all backed by the same core library:

Web app

Paste a GitHub URL at causalist.xyz/<owner>/<repo>. Instant previews for hand-curated demos; live analyze for any public repo when you supply your Anthropic key.

CLI

npm install -g causalist
export ANTHROPIC_API_KEY=sk-ant-...
causalist map vercel/next.js --open

Universal shell interface — works with Claude Code, Cursor, Hermes, Aider, or any agent that can spawn subprocesses.

Claude Code plugin

causalist install
# prints: /plugin install --local ~/.causalist/plugin

Drop into Claude Code. You get /causalist:map and an MCP server exposing map_repo, query_node, blast_radius, and simulate.

Live streaming

While Claude Code works on a local repository, the plugin's PostToolUse hook posts every tool-use event to https://causalist.xyz/api/ingest/. The browser viewer subscribes via Server-Sent Events at /api/stream/ and highlights nodes in real time — you can open the repo's graph in another tab and watch Claude work.

The pairing flow (browser shows a 6-char code, CLI calls causalist pair ABC123) is how the browser and local session agree on a sessionId without requiring a user account.

MCP tools (stable)

Tool	What it does
`map_repo(url)`	Fetch + analyze, returns the full graph
`query_node(id)`	Node metadata + summary + language
`get_neighbors(id, direction)`	Incoming or outgoing edges with kinds
`find_path(source, target)`	Shortest causal path between two nodes
`verify_edge(source, target)`	Check the edge exists and return its confidence
`blast_radius(id, depth)`	Everything reachable within $k$ hops via `calls` / `writes`
`simulate(intervention)`	Extended-thinking "what if?" counterfactual

API

The POST /api/analyze route is a public Server-Sent Events endpoint. Pass Authorization: Bearer and a JSON body {owner, repo, commit, tree, files?}; receive agent events as each of the four agents completes, then a done event with the final graph.