kodo

The one we stopped.

A minimal web GUI for driving coding agents, built on top of T3 Code. Somebody else shipped the same idea faster and better, so we put it down instead of racing them.

Current state Stopped
Built on T3 Codepingdotgg/t3code
Our fork noxire-dev/kodo

Racing somebody to their own idea is a bad use of a small team.

This page exists because a shop that only shows its wins is not telling you anything. kodo is here, struck through, with the reason attached.

Why we stopped

We were building a GUI on top of T3 Code. T3 kept shipping, and the gap between what we could add and what they were already adding kept closing from the wrong direction.

Use T3 Code instead. It is the same idea, further along: a minimal web GUI for Codex and Claude, running as npx t3 or as a desktop app on winget, Homebrew and the AUR. There is no version of this page where we pretend otherwise.

T3 Code
What we had

A working fork

Codex and Claude both driving, the web GUI running locally, keybindings, an observability pass. Nothing exotic, and nothing that justified a second one of these existing.

What we learned

The GUI was never the hard part

Driving an agent is the easy half. Giving it something true to read before it starts is the half nobody had done, and that is where everything else in this shop went.

The one way back

Not planned, and not on a roadmap. Written down because it is the only version of kodo that would be worth restarting.

Idea

A GUI for our own harness

A build with first-class pi and toka integration rather than another generic front end. A general GUI has to treat every harness the same; one that only has to drive two can expose what makes them different — toka’s REPL and stashed tools, live, instead of flattened into a chat log.

Condition

Only after toka is real

There is no point building a window onto a harness that is still pre-1.0. If toka gets finished and benchmarks well, this becomes worth doing. If it does not, kodo stays exactly where it is.

Left up on purpose

The repo stays public and the label stays stopped. Dead projects with the reason written on them are more useful to read than a shop window with the failures quietly removed.

If you want the thing kodo was trying to be, the link above is the honest answer.

Want to take it somewhere?

It is open. If the pi and toka angle is interesting to you and you would rather not wait for us, say so.

hi@mirako.computer