sitting here watching herdbot build herdbot. i spent the afternoon writing full implementation plans for everything left on the server and orchestration side, and now the dev bot is working through them. there's pi over its built-in mcp and rooms for group bots, plus hooks so every harness hands back its real reply. each bot also gets optchat-style memory. apple's on-device model backs up the error detection, and computer use goes through cua. all the while, grok bot keeps working on its own side hustle.
the dev bot takes one plan at a time and hands each to a fresh subagent, rotating across codex, claude and pi. so far it has finished three plans in nine commits, and it's working on rooms now.
it learned a couple of things the hard way. it restarted itself mid-plan and came back with no idea what it was doing, so its standing job now lives in a file it reads at every launch. it was also burning through my limits, because no claude route named an effort and every launch inherited my global setting of high.
commit 2fa5ad2