Featured · 2 Min Read
Run CLI Agents In Parallel With Git Worktrees
Two agents sharing one working tree is a stash fight waiting to happen. Here is the model we use instead.
What we are building, what broke along the way, and what we changed our minds about.
Featured · 2 Min Read
Two agents sharing one working tree is a stash fight waiting to happen. Here is the model we use instead.
2 Min Read
The case for building around the CLIs you already use instead of wrapping one provider's chat in an Electron shell.
3 Min Read
Closing a window should never kill a three-hour agent run. The trick is who owns the PTY, and it is not the UI.
4 Min Read
Tabs full of agents are useful until they need to coordinate. How orchestration protocol v2 adds ownership, gates, and a real coordinator.
2 Min Read
Hitting a provider limit mid-run is the worst way to learn your quota. We put Claude, Codex, Kimi, Grok, Cursor, and more in the status bar.
2 Min Read
We did not want to invent another agent protocol. If it runs in a terminal, it runs in Alera - and the big ones get first-class treatment.
3 Min Read
Five agents in parallel and the fans spin up. The Resource Manager names the culprit per tab - including the time it blamed us, 26 times over.
3 Min Read
Every new worktree needs the same ritual: copy the .env, install dependencies, bootstrap. We made the repo describe it once.
2 Min Read
Review belongs next to the work. How the Pull Requests panel keeps GitHub, GitLab, and Azure DevOps scoped to the worktree that produced the branch.
2 Min Read
A chatty agent can stream output for an hour straight. That is a frame budget problem, and on Linux it is worse than you think.
2 Min Read
The mobile companion is honest about what it is: a window into your runtime host, not a phone IDE. Here is what it does today.
2 Min Read
Why we bet on Flutter and Rust instead of shipping another Electron shell around CLI agents.
2 Min Read
Why we started building a native workbench for CLI coding agents, and what you can do with it today.