Bennch is the workspace for software built with AI. It turns your build into a clear plan your coding agent works from, so you can see what’s planned, what’s being built, what needs your decision and what’s actually been checked.
Live now with Claude Code. Codex and more coming soon.

Ledgerly, an example project in Bennch: the next step, what needs you and where the build stands.
Building fast is the easy part now. Knowing where the project stands is what gets hard.
The plan, your decisions and design links live with the project, so a new session never starts from zero.
Extra ideas come back as proposals. Choices that are yours come back as questions.
Not when the AI says so. Each card shows its commits and tests, and only you can accept it.
Every piece of work is a card. Claude takes them in order, in the same Claude Code session, and hands each one back with proof. You don’t start them one by one.
Up next 4
Claude works down the list
Turn an accepted quote into an invoice
Attach photos of the finished job
Mark an invoice as paid in cash
Monthly income summary
Claude is building 1
One at a time, in order
Today screen: jobs and unpaid invoices
iOSAndroid
2 commits so far
Tests passing
Next up: LD-24, in the same Claude Code session. Nothing for you to start.
Your check 2
Built. Only you can finish these
Sign in with an email link
iOSAndroid
4 commits · tests passed
Remind clients when an invoice is overdue
2 commits · tests passed
1You approve the cards
What each is for and how you’ll know it works. Unapproved cards can’t be started.
2Claude builds them in a row
One card, or as many as you like. Claude finishes one, starts the next, and only stops when something needs you.
3You check the proof
Try it on your own devices. A failed step goes back to its card with your note.
The plan, the decisions, the code and the tests stay connected from the first card to launch.
Take Ledgerly, an invoicing app for tradespeople. It has a phone app, a page where clients pay, and a backend. Each card belongs to one of those parts, sits on a board for its kind of work, such as design, backend or security, and says where it runs: iOS, Android or web.
See the whole product at once, or just the phone app’s next few cards, and have your AI work through them in order.
When a choice is yours, such as how data is stored, payments or security, your AI asks with options and a suggestion instead of deciding.
Your answers stay on record for every later session, and cards link to where their designs live, like a Figma file.
The Overview shows the next step and what’s waiting on you. If a session stops halfway, the next one picks that card up first. Run several AI sessions at once and each card shows which one is building it.
Each card shows its commits, the tests the AI reported, your CI result and which platforms were covered. Work that grows far beyond its card is flagged.
For whole journeys, like sending an invoice and getting paid, the AI writes a step-by-step test guide linked to the cards it tests, so one run on your phone can accept several cards.
Bring Bennch in on day one or halfway through. You don’t choose: your AI looks at your folder and starts the right way.
It asks what you’re building, who it’s for and what the first version must do, plays back a short brief, then proposes the cards.
Claude: “What are we building?”
Your AI maps the repo. What’s already built comes to you to accept in one go, and new cards are only for what’s missing.
Claude: “This folder has code, so I’ll map what’s built and what’s left.”
We’ll email you an invite to app.bennch.co.uk. A short practice project shows you how everything works.
Add Bennch as a custom connector on claude.ai, or run one command. It works for all your projects. No keys to copy.
Open Claude Code in your project’s folder and paste the prompt Bennch gives you. An empty folder: Claude plans it with you. Existing code: it maps it.
claude mcp add --transport http --scope user bennch https://app.bennch.co.uk/mcpWorks from your approved cards over MCP and reports what it did. Bennch runs no AI of its own.
The same cards and checks for OpenAI’s Codex: it builds what you approved and reports back to Bennch.
Commits that name a card appear on it, with their size and your Actions result. If the AI says tests passed but CI failed, the card shows it.
Commits, pipelines and change size on each card, for projects on GitLab.
A new error after a release shows on the card that shipped it, and can become a proposed card for you to approve.
External integrations such as GitHub are read-only.
Claude Code works today, and Codex and other coding agents are coming. Your AI does the building; Bennch holds the plan, the decisions and the evidence.
No. Everything the AI does happens in your own coding tool, under your own account.
Bennch blocks what goes through it: your AI can’t start an unapproved card, approve anything or mark work done. It can’t control what the AI writes in your files, so every commit is linked to a card, unusually large changes are flagged, and nothing counts as done until you’ve checked it.
Yes. Press Build, pick a board or part of the product, and choose one card or several in a row. Bennch shows exactly which cards it will take, in order. You can also run several AI sessions at once.