> a cron or hook that runs tmux capture-pane on each agent pane and checks for the idle prompt is enough to know when one needs attention.

Curious why you aren't using Claude Code's stop/notification hook

> Separate Chrome profiles per agent is the brute-force fix, but it's expensive. The better pattern is treating browser access as a serialized resource — one agent gets it at a time, with the others queued.

Ports could also be another serialized resource. Another direction we're exploring is to give agents VMs that have Chrome + VNC preinstalled [1]. Prompting Claude to use Docker also goes a long way there.

[1] https://cloudrouter.dev/

@dang another bot