Tau

Tau is one of those projects that feels useful because it stays honest about what agent development actually looks like. There’s a lot of talk around coding agents, but the important parts are usually the parts people skip over: where tool calls come from, how the transcript grows, what happens when a session outlives the process, and how you keep the whole thing from collapsing into callback spaghetti.

Tau answers those questions by separating the pieces on purpose.

The provider layer turns model responses into provider-neutral events, so the rest of the system doesn’t have to care which model is behind it. That sounds small. It isn’t. Once you start treating the agent as a stream of events instead of a pile of branching logic, testing gets cleaner, exporting gets easier, and the code stops feeling like a trap you built for yourself.

The reusable harness is where the real structure shows up. Messages, tools, transcript state, cancellation, queued prompts, sessions, all of that lives in one place, and it stays independent from the terminal, file paths, or Rich rendering. Those things wrap the harness. They don’t get to live inside it. That boundary is the lesson, and it’s a good one.

Then there’s the coding environment, which gives Tau its practical edge. Files, shell access, durable sessions, skills, slash commands, and a Textual TUI make it usable as a real terminal agent while you study the code behind it. That mix matters because educational projects often stop at the diagram. Tau keeps going.

It also borrows a clear architectural idea from Pi, keeping the harness, environment, and UI apart instead of blending them into one hard-to-read mass. That separation is what makes the project a useful map if you’re building your own agent. Start with events. Add the loop. Wrap it in a harness. Then give it tools and a UI.

There’s a nice contrast with hands-on-deck, which focuses on agent-native file editing, while Tau zooms in on the structure underneath the agent itself.

That’s the kind of project that sticks with you. Not because it promises magic, but because it shows the machinery clearly enough that you can actually build with it.