Blast radius
In the product: open codefundi.app/blast . API: POST /v2/repos/{repo_id}/radius. Blast radius requires a DEV plan or higher. Related map view: /map (dependency map API).
When agents edit a file, they rarely know what else depends on it. That blind spot causes silent regressions. Blast radius maps code structure and flow (not just text similarity) so you see every file that breaks before the edit ships.
How to use it in the web app
Open Blast radius
Go to Blast (/blast) and select an indexed repository.
Choose targets
Pick changed files, dependencies, and/or a GitHub pull request. File and dependency targets take precedence over PR resolution when both are set.
Generate
Run Generate blast radius. Review dependents, data flows, entry points, and call edges in the graph and detail panels.
What you get
- Per-target blast radius (resolved dependents and files)
- Data flows, entry points, and call edges for review and agent workflows
- Optional export to Markdown for agents or PR review
Related product surfaces
- Dependency map (
/map): cross-repo dependency placement for a package or import. - Scope (
/scope): aggregated dependencies, functions, and variables for a repo.
Same capability via API
POST /v2/repos/{repo_id}/radius with files, dependencies, or a PR number. Credits: 3 credits / request. Full contract: V2 Blast radius.