Commit

herdbot is public: https://github.com/slogsdon/herdbotslogsdon/herdbot since the post earlier, it runs as a launchd daemon, imported all nine grok bots, and passes messages between them. every message waits in a queue until the receiving bot is idle, because prompting an agent mid-turn steers it and throws away the answer it was working on. pi taught me that one. the phase 1 bar was herdbot building herdbot, and it cleared it tonight, sort of. i gave the dev bot a one-line fix. it handed the work to a codex subagent, codex dropped the prompt, and the bot retried on claude without me. that run built, passed tests, and told me what it couldn't check. cursor is still against its weekly limit. herdbot read the error, benched cursor for 24 hours, and restarted the bot on claude. that was the first real failover, and i didn't plan it. what's still missing is grok's schedules, which only live on its servers, along with group bots, computer use and the ui. it's macos only, mit licensed, and very early.