I pay for more AI coding tools than any reasonable person should, and for a couple of months I’ve been tinkering with one question: what if they worked together, and none of them could do anything I hadn’t agreed to?
Not “agreed to” in the sense of clicking Accept four hundred times until my finger goes numb. Agreed to in the sense that the operating system itself won’t let them do anything else.
That idea now has a name, a public repository, a website, and as of tonight a first release candidate. It’s called GovernCode. It’s free, it’s open source, and it will stay that way.
One boss, a few contractors, and a building inspector
GovernCode lets you pick one AI tool to lead a project. That’s the Controller. It keeps the big picture and hands small, bounded jobs to the others, the Runners, the way a contractor hands a room to a subcontractor. Each job gets written down first: what to do, which files it may touch, how much of my usage it may burn, and what “done” means.
Every one of them runs inside a sandbox that Linux enforces. Not a polite instruction in the prompt asking the AI to behave. The kernel’s own locks (Landlock and seccomp, if you want the names) decide which folders it can read, which it can write, and where on the network it can go. If my machine can’t enforce those rules, GovernCode refuses to start any AI tool at all and tells me why. There is no “just this once” switch, on purpose, because I know myself.
When a tool wants to run something that matters, it stops and shows me exactly what will run, byte for byte. Not a friendly summary. The actual command.
The part where I nearly gave up on my own demo
The first time I tried to show it off, I spent more time clicking Allow than watching the AI work. Every npm test, every file edit, every harmless ls. It was secure the way a locked filing cabinet at the bottom of a lake is secure.
So now I can say yes once, yes for the rest of this job, or yes for this project, and the plain read-only stuff just runs. The sandbox doesn’t move an inch when I do that. It only stops asking me the same question forty times. Deleting things, git, the network, and handing work to another AI still ask every single time.
I let the AIs audit the AI babysitter
Before putting a release candidate out, I had other AI tools try to break it. They found real holes. A tool could start a background process, “finish”, and leave that process running. A cleverly placed shortcut in a folder could have widened what a later job was allowed to write. A carefully worded command could sneak past the “this is just a harmless read” check.
All of that is fixed, each fix has a test, and the sandbox now proves its rules on your machine every time it starts, including against those exact tricks. I’d rather find out from a robot at my desk than from someone’s bug report.
Local models, because quota is money
Small jobs can go to a model running on my own graphics card. It gets no tools and can’t run anything. It reads the files it’s given and proposes changes, GovernCode checks every file it wants to touch, and I review it like anyone else’s work. The first real one wrote a usage section for a README in six seconds and cost exactly zero of my subscription.
The rule I care about most
GovernCode makes building software with AI a lot more approachable. It does not make anyone less responsible for what they ship. If I accept a change, it’s mine. I read the diff, I understand the code, I run the tests. The AI can write it. Only I can answer for it.
That’s written into the project’s philosophy as rule number two, right after “you hold the controls”, and it’s staying there.
Where it stands
It’s a release candidate for Linux, for people who like poking at things from a terminal. macOS and Windows are next, together, same priority, because I’m not making either one wait for the other. I’m dual-booting my laptop with Windows tonight so I can actually test it there.
None of this would exist if Omarchy hadn’t made my computer fun again and dragged a passion I’ve had forever back out of the drawer where time had shoved it. So: thank you, DHH, and everyone behind Omarchy.
GovernCode is at governcode.com. It’s free forever. If it saves you an afternoon, there’s a coffee button. My AI crew runs on tokens. I run on coffee. Only one of us has a button.