Rooms and collaboration
Status: Current for core room commands, planned for room-agile extensions.
Rooms are durable collaboration timelines. They separate transport state, viewer state, participant identity, messages, and tasks.
Basic room flow
Section titled “Basic room flow”foxctl room create alpha --title "Agent Alpha"foxctl room join alpha agent-a --role leadfoxctl room send alpha "Review the retry branch in client.ts"foxctl room inbox alpha --actor agent-afoxctl room status alphaRoom tasks
Section titled “Room tasks”foxctl room task add alpha --title "Refactor retry path"foxctl room task claim alpha --id <task-id>foxctl room task block alpha --id <task-id> --reason "waiting on benchmark data"foxctl room task complete alpha --id <task-id> --notes "Retry ladder flattened"Viewer and relay backends
Section titled “Viewer and relay backends”foxctl room relay alpha --backend tmuxfoxctl room loop alpha --backend zellij --session alpha-roomTmux collaboration
Section titled “Tmux collaboration”foxctl tmux create --session foxctl-collab --panes 3 --attachfoxctl tmux send agent-b "Review internal/storage/mailbox/store.go for lease races." --sender agent-aCurrent vs planned
Section titled “Current vs planned”- Current: room messages, inbox, status, tasks, tmux/zellij relay surfaces.
- Planned: room-agile milestone enforcement, evidence-lane policy, and
workpack templates from
docs/plans/features/room-*. - Room-agile commands exist as a skill protocol surface, but milestone evidence policy must be described as guidance unless exit-policy enforcement is explicitly enabled.
Room-agile examples
Section titled “Room-agile examples”foxctl room epic start <room-id> "Room agile protocol" --goal "..." --owner human-afoxctl room milestone start <room-id> <epic-id> --proposal <proposal-id>foxctl room story validate <room-id> <story-id> review pass "..."