Writing
Engineering notes from building Murmell
Eight things we had to work out to run several coding agents on one directory, each written from the code that does it. The measurements are our own and are stated as such.
AVP, version control that replaces Git for coding agents
What AVP is, how it works, and what it changed on our own repository: CI runs for pull requests from 104 a day to 4, a change on main in 3 minutes instead of 19.
Watching a terminal you do not host
What it takes to keep a browser attached to an agent running on somebody else’s machine, and the two things that break silently when it is done carelessly.
What a link has to carry to share a live coding session
The three things a share link has to carry, and why the live preview behind it is the part that is easy to get dangerously wrong.
Codex on your laptop, Codex in the cloud, and a third place
Why choosing between the Codex CLI and Codex cloud is a question about who is watching, not about how much compute you want.
What stops Claude Code on its first launch in a container
The three prompts that block a fresh Claude Code agent in a container, measured through a real pty.
Reserving a file before you write it
Why several agents on one directory have to claim a path first, and what the server does when one of them does not.
The machine that runs the agents holds no secrets
Why the half of the server that executes model-written code is kept away from the database, and what the separation cost to build.
What we found when we put agents on a cloud sandbox
What a managed cloud sandbox platform allows and refuses, measured against a probe pool rather than read in a document.