Carthagent
Carth is a development cockpit where named AI agents plan, build and review work in isolated workspaces, and a person approves what ships.
Projects
Carthagent
The problem
AI agents can now write software faster than any team. Speed is no longer the hard part. The hard part is knowing what changed, who allowed it, and being able to stop a change before it reaches production. Without that, a fast agent is a risk rather than a help.
What Carth does
Carth is a development cockpit. You write a brief in plain sentences. A crew of named AI agents comes back with a plan first (the files, the agents, and an estimate) before anything runs. The change is built in its own copy of your code, another agent reviews it and attaches the evidence, and then a person approves it or sends it back.
Not every mission is code. Ask for a report, a deck, or an analysis and the crew hands back a file, kept with the record of the mission.
How it keeps a person in control
- An approval gate: agents never merge, deploy, or publish on their own. A named person approves, and the record of that approval stays attached to what shipped.
- An isolated workspace per company: each company gets its own sealed container on its own private network, and each task is built in its own git worktree, never on the main branch.
- Your own provider keys: bring your own keys and the work goes to your provider on your own contract. Keys are stored write only and encrypted under a key that belongs to your container.
- Self-hosting: on Enterprise, Carth can be installed inside your own infrastructure, against your own model provider.
- An audit trail: approvals, deploys, budget changes, and key rotations are written as they happen, and the record cannot be edited from the interface.
- Budget limits: the plan arrives with an estimate before a line is written, and every budget change is recorded.
- A second brain per workspace: every repository is read into a graph of files, calls, and owners, with a memory that survives each mission and gets better every run.
- A model per role: give each role its own engine, so one model plans, another builds, and a third reviews with different eyes.
My role
I founded Carthagent and built Carth: the crew of agents, the approval gate, and the isolation model behind them.
Status
Carth opens to companies a few at a time through a waiting list, because a person sets up each workspace with the company's repositories and knowledge base.