See what a change breaks before your agent makes it.
Wingbox builds the code graph of your repository on your machine and tells an AI coding agent, in a few hundred tokens, what a change will break before it edits. Open source (MIT), ten languages.
$ pipx install wingboxSee it in action
One command, one exact answer. The agent asks which files depend on the one it is about to edit; Wingbox answers from the code graph instead of reading the repository.
Your architecture, in 3D layers
The build also writes an interactive map: one HTML file that opens in a browser without a network connection. The layers view stacks API, services, domain and infrastructure; click a file and its blast radius lights up across the layers.
What it answers
What could break if I change this file?
Which modules depend on this service, class or type?
Does this dependency cross an architecture boundary?
Which two or three files should I read before fixing this bug?
Run it on your repository
- 1
$ pipx install wingboxInstall the command. Claude Code and Codex can also load it as an agent skill: npx skills add aileron-tech/wingbox.
- 2
$ wingbox build .Build the graph. The report and the map land in wingbox-out/.
- 3
$ wingbox impact path/to/file 2Ask what a change to one file reaches within two hops.
How it works
- Everything runs on your machine: no LLM call, no embeddings, no network access to build or query the graph
- Deterministic static parsing: the same code gives the same graph
- Python, TypeScript, Rust, C#, Java, Go, Ruby, Rails, Free Pascal and Lazarus
- An agent skill for Claude Code and Codex, and a plain command for people
Wingbox is the engine behind Agent Control, our fixed-price audit of agent-written code.
