BUILD LOG 001 · 2026-10-06
Lights on
If you run more than one coding agent, you already know the problem. Each one lives in its own terminal. Each one has its own idea of what it is doing. You end up as the human message bus, tabbing between windows and losing the thread.
SoloFleet puts every agent and every task on one deck. The map shows what is running, what finished, and what is waiting on you. You give the orders, the agents fly, and you review what comes back.
It is local-first. The deck runs on your machine and adds no cloud of its own between you and your agents. SoloFleet itself never sends your repositories off your machine.
And it plays like a strategy game, on purpose. Progress comes from runs on your real projects, never from grinding. A quiet fleet is a quiet map.
I am logging the build here as it happens. Expect irregular logs like this one, honest numbers when there are numbers, and no roadmap theater.
Windows first. If your agents live on the same machine as your GPU, you are exactly who this is for.
Ranger // NULLBRIGHT