multi-agent-room

<!-- AI-RULEZ :: GENERATED FILE — DO NOT EDIT Content-Hash: blake3:525b3f8031902107da61ff0f2a5e71f24e1e3bc25f8b5a39bcef00c712bc8894 Source-Hash: blake3:7ed98849883ef704c52a25d433f24690fad7148853779dbc1aae4adc63c04a24 Schema-Version: v1 --> # Multi-agent thread orchestration Run a team of NAMED subagents that coordinate in shared THREADS, all driven by one orchestrator. Each subagent has its own identity and inbox, and posts to threads the relevant peers are members of. ## When to use it Orchestrate subagents when: - Multiple reviewers need to see each other's work (code review, audit, cross-validation). - A subagent should hand off findings to a peer for verification. - The team needs a shared narrative (all readable in one thread history). - You want to parallelize independent work (each agent runs concurrently) and then synthesize. ## Setup 1. **Start a thread and name its members.** A thread is addressed by at least two of three coordinates — `{subject, path-glob, members}`. For a private team, list the members explicitly so only they see it; discovery is scoped, never global, so unrelated agents never surface it. ```text thread_start {subject: "review-pr-42", members: ["security", "perf"], title: "Code review panel"} ``` 2. **Assign each subagent a short name.** Pass `as_agent` to every tool call the subagent makes. Names like `"security"`, `"perf"`, `"correctness"` are clearer than defaults. A named member must `thread_join` (or be added via...