Before knowing about Clawdbot, I designed an always-on "life-coach" bot that uses your file system as persistent memory, is reachable via Telegram, and acts proactively via cron jobs.

x.com/Nil053/status/2005409639983431915

Before knowing about Ralph, I wrote: "Spec-based development ties nicely into what's coming next: orchestration. For example, it's straightforward to turn [...] into a loop that goes on until the agent is sure that the implementation matches the design."

x.com/Nil053/status/2008279223379915240

The Next Thing is probably the orchestration layer, which is just a fancy way of saying, "Tool that helps devs go from 1 Claude Code to 4+ in parallel."

The way subscription plans are set up incentivizes it: the $20 plan is not enough to run a single agent, and the $100 plan feels wasteful running only one.

It seems to me like no tool has captured this space yet.

I used tmux; and then cmux.

But I spend all day in the agent management layer. It had to be... friendlier.

In the past, when I had intuitions about where AI was headed, I didn't act.

This time, I'm building isomux.com.