AI agents are building more of your software every week. Lenzon keeps the why, the how, and the what of it true, for every builder on the team.
You wrote the plan. The agents built it, across nine pull requests, three of them while you slept. Six weeks later the plan says one thing and the code does another. Nobody decided that. Nobody noticed.
That is the failure Lenzon exists to catch.Not bad code. Lost context.
Software no longer arrives one typed line at a time. It arrives as combined change: people and agents delivering together, faster than anyone can read.
The scarce skill is no longer writing code. It is staying oriented, knowing why a thing was built, how it actually works now, and what changed while you were looking elsewhere.
Every role on the team is becoming a builder.Builders need to stay up to speed.
Sidecar keeps your planning docs in git, next to the code they describe. Every doc knows exactly which files it was verified against, and when. When the code moves underneath a doc, Lenzon flags it, and AI helps re-read, repair, and re-verify it. Decisions carry their reasons forward, so “why is it like this?” still has an answer in six months.
Lenzon analyzes pull requests one at a time, in series, and in groups, so you see the direction of combined change, not just today’s diff. Focus lenses read the same change for different eyes. One change, every perspective that matters.
Any analysis becomes a narrated explainer: a walkthrough a teammate can watch, not a diff they have to decode. It is how the person who was not in the room catches up in minutes instead of days.
Lenzon reads the repository. It does not live inside anyone’s process, and it works the same whether your team wrote the code or commissioned it.
Sidecar is for your source code. It keeps your planning docs in git, tied to the code they describe. It connects your repo to the Lenzon pipeline, so every plan and pull request can become an explainer.
It runs as a command line tool and as an MCP server. Your coding agent asks the same questions you can. That makes it a natural fit for agentic development.
npx @lenzon/sidecar initView on npmWrite a script and play it in your browser. No account. No server of ours. Your agent can write the script for you.
npx @lenzon/player new my-idea.jsonView on npmThe script type every explainer is made of. Use it to build a tool of your own that makes explainers.
npm i @lenzon/explainer-formatView on npmTwo steps, both live today. Public repos are free while we’re in beta.
A link arrives. No password, no approval queue.
Install the GitHub App on a repo you own. You land back here with it already linked.
Point it at a pull request and watch the explainer, or install the extension and watch it in your editor.
GitHub App
VS Code extension