Interactive demo · macOS App
A whole day of agents, without hovering over them
DevoCode is the Mac app I use to work with coding agents like Claude or Codex: I hand them tasks in my projects, answer when they ask and review what they do. It is a fork of T3 Code, with what I was missing added on top so they can keep working on their own from morning to the small hours. Scroll down and you will see an ordinary day, hour by hour.
The captures are DevoCode running for real, with agents working in four projects of this portfolio. The interface is in English, like T3 Code’s. DevoCode’s code is private.
Every project with its threads, and every thread with its status: working, waiting, asking for something or done. That comes from T3 Code. DevoCode arranges it its own way, with a single list by project, subagents folded under the thread that launched them and idle projects set aside at the bottom.
T3 Code’s diff shows files and lines. DevoCode adds a summary on top, with each thing waiting to be committed in one sentence and the files it touches underneath. Three separate changes read as three changes, not as four files.
Next to the chat a panel opens with whatever you need: browser, terminal, files, diff, pull requests or the phone simulator, each on its own key. DevoCode adds Docker, with the project’s containers and their live stats.
A message can wait for other threads to finish, even ones in another project. Here the Wiselet README waits for the Kyloq rename, and starts on its own as soon as that ends, even with no window left open.
A sequence spreads several prompts across several threads, each with its own model, and sends them on its own one after another. While it runs the Mac does not sleep, and DevoCode shows what is keeping it awake. You choose how long: until you stop it, until the thread ends or whenever any thread is working.
The project journal notes every step forward of the day with its time, project and branch, and sums it up on its own once the project has been quiet for a while. It reads as a timeline or a table, and it stays even if you delete the threads.
If a thread’s model runs out of usage in the middle of the night, T3 Code can wait for the reset and carry on. DevoCode does not wait. It moves the thread to another model by your rules, say from Claude Opus to GPT, and hands it back to the first one once it has usage again.
A fork goes stale unless someone looks after it. DevoCode does not chase every change in the original. It only moves when T3 Code ships a stable release, and every jump is made by hand, feature by feature. 1.0 was built on v0.0.45 and 1.1 on v0.1.0, which brought a new orchestrator and meant redoing the additions one by one.
Nightly and preview builds come out several times a day. They are not followed, because a fork built on something half finished inherits its bugs.
Wherever DevoCode touches T3 Code’s code it leaves a marker, and a script checks they are all there before every update. That is how each jump says what needs reviewing.
Claude reads the new T3 Code releases, sums them up and gives a verdict. It is right there in the command palette.
