I spend my days in terminals. Coding agents, dev servers, log tails, the occasional long-running build, spread across three or four projects at once, most of them talking to a machine that isn't the one in front of me. For a long time the way I kept track of all that was the way most people do, which is to say I didn't. I had a scatter of terminal windows, a browser drowning in tabs, and a running mental note of which agent was working and which had quietly died an hour ago. I alt-tabbed for a living.
Atrium is the thing I built so I could stop.
What it is
It's a single, calm window that holds every project I have running. Each project gets its panes: the agents, the terminals, the commands, all collapsible and fully alive, so I can see the whole shape of my work at a glance instead of rebuilding it from memory every time I sit down. A green dot tells me what's running. A glance tells me what died. That's most of it. That's most of what I wanted.
It began as my own take on Aaron Francis's Solo, built with Tauri, Rust, and a real terminal engine so it feels like a native app and not a browser tab pretending to be one. But the lineage matters less than the intent. I didn't build Atrium to ship a product. I built it because I wanted one calm place to see my work, and no such place existed that fit the way I actually work.
The most important thing it refuses to do
The best decision I made about Atrium was a decision about what it would never do.
There's a version of this app that's far more impressive on paper. It supervises your processes. It restarts the ones that crash. It spins up sixteen agents in parallel and runs them like a little factory floor. I sketched that version. I had it written down in a spec. And then I threw it out, because the impressive version isn't the calm version, and calm was the entire point.
So Atrium organizes what's running; it does not do the running for you. Every pane is the same plain primitive, a single terminal. An "agent" is just a terminal that happens to launch a coding assistant. A "command" is just a terminal that happens to start a dev server. There's no clever supervisor underneath, no orchestration engine, no magic. There's a window, some groups, and a great deal of care spent making that window feel quiet. The restraint is the feature.
Why a window like this is worth building
I think that's the truest thing I can tell you about how I build. The hard part of making software has almost never been the making. It's the deciding: what belongs, and more than that, what doesn't. I'm not drawn to the tool that does the most. I'm drawn to the one that does exactly what I need and then gets out of the way, the one I can lean on without thinking about it, the one that lowers the temperature of the day instead of raising it.
Atrium is a calm window because I wanted a calm place to work, and I've stopped believing that's a small thing to want. The environment you sit inside all day shapes the work that comes out of it, and over enough days it shapes you too. Most of my best decisions as an engineer have been subtractions. This one just happens to be a subtraction I get to look at every morning.
The part that's still mine
None of this would have been worth doing a few years ago. Building a native, cross-platform desktop app to scratch a personal itch, with real Rust underneath and a proper PTY layer, used to be far too much yak-shaving to justify for an audience of one. That math has changed. I built most of Atrium alongside an AI coding assistant, and what that unlocked wasn't speed, exactly. It was permission. Permission to build the exact tool I wanted, in the exact shape I wanted it, for the smallest possible audience: me.
But the assistant never decided what Atrium should be. It couldn't. Ask it to build an orchestrator and you'll get a beautiful orchestrator; it has no opinion about whether the orchestrator should exist. That opinion, the taste to want less and the nerve to throw out the impressive version and keep the quiet one, is the part that's still mine. It's the part that's still yours. In an era where the building is getting close to free, knowing what's worth building is the whole job, and it's the most personal thing any of us brings to the work.
So Atrium isn't really a story about a terminal app. It's the clearest artifact I have of how I want to work and who I am when I build: quietly, deliberately, toward calm, in tools I made to live inside. I built the window I wanted to work in. It turns out that was worth doing.