Case study
samnexus
Gives your AI coding agents a full map of your codebase, so they know what a change will break before they make it.
- Status
- Live, internal tool
- Owner
- Papi Labs Ltd
How it works
A schematic of how samnexus works, drawn in the browser.
Summary
- Context
- Papi Labs is one engineer and a large number of AI agents, working across several live codebases at once.
- Problem
- An agent that cannot see who calls a function will still edit it confidently. The damage shows up later, in a file nobody opened.
- Constraints
- It runs on your machine. Your code never leaves it, and every answer carries a label saying how far it can be trusted.
- Approach
- It builds a map of your codebase on your own machine and lets the coding agent consult that map before it edits anything.
- What is new
- Before a change, the agent gets one briefing: what the code is, what uses it, what depends on it, what tests cover it, and how risky the change looks.
- Outcome
- Agents stop making confident edits to code that something else was quietly relying on, and the person supervising can see why a change was judged safe.
- Evidence
- Papi Labs builds all of its products with it, on live codebases, every working day.
- Status
- Live and in daily use inside Papi Labs, on several codebases at once.
About samnexus
What you give it, and what you get
You point it at a project and run one command. It reads the code, builds a map of it, and gives that map to the coding agent you already use.
After that you work with the agent as usual. The agent checks the map before it edits, and you can see it do so.
The result is fewer edits that break code elsewhere in the project, and fewer bugs that show up a week later.
Why it is different
A coding agent that searches by name finds the same word in unrelated places and misses code that is connected in other ways. samnexus answers from a map of the code, so the agent knows what a change will affect before it makes it.
Before a change, the agent gets a short briefing: where the code is defined, what uses it, which tests cover it and how risky the change looks.
Each answer says how far it can be trusted and what it cannot see.
It runs on your machine, and your code never leaves it.
Where it stands
samnexus is live and in daily use inside Papi Labs, on several codebases.
It reads the code as written, so it can miss a call that only happens while the program runs. If it says nothing uses a piece of code, check before you delete it.