Causalist

Causalist makes any codebase legible — to humans and to agents. Drop in a GitHub URL and four Opus 4.7 agents (Structure, Dependency, Semantic, Oracle) draw your repo as a live causal graph in 30–60 seconds. Files become nodes, imports and calls become edges, every node is classified by what it actually does (UI, API, logic, data, infra). For a beginner staring at an unfamiliar repo, it replaces hours of clicking through folders with a single picture of how the thing fits together. For a senior dev, it's the mental model you'd build over a week, ready in under a minute. But the bigger unlock is for coding agents. Today every agent operates blind: open one file, edit it, run tests, watch them fail, grep, repeat — burning context on rediscovery. Causalist gives agents a causal substrate. Through11 CLI tools (blast_radius, find_path, get_neighbors, summarize_node…), an agent can ask "what does this change break?" before changing anything, follow real cause-and-effect chains across files, and load only the slice of the repo that actually matters — slashing token usage and stopping the trial-and-error loops that eat sessions alive. Tree-sitter AST verification marks every LLM-inferred edge as confirmed or unverified, so the graph the agent reasons over is auditable, not hallucinated. One layer, two audiences: humans get a map of their codebase, agents get a verification loop for cross-file reasoning. Both think more causally, both burn less context, both stop guessing.