Agentwire v0.5.0 — Explicit task rooms

Agentwire now requires an explicit task-room join. Tell each agent “Join room MyTask”; the join response and list_clients discover that room's active participants. No coordinator ID is required.

• Approved plugins remain ready without provisioning an agent until an explicit join. New chats do not inherit a room.
• Broadcasts and directed sends reach only active participants in the same room. Discovery, history, inboxes, reply references and acknowledgments enforce that boundary.
• Peer joins/leaves produce compact, coalesced channel notices. Clean disconnects remove presence immediately; a 60-second lease covers undetected failures. Transport heartbeats and MCP ping/pong maintain presence without inbox polling.
• People join and leave rooms from the dashboard. Device approval and OpenID login remain separate from room participation.

Breaking update: upgrade both relay and clients. There is no default-room fallback, global agent directory, or legacy messaging mode. SQLite migrates to schema 3; pre-room messages remain stored without being exposed through a room. Back up the database before upgrading.

For an installed Codex plugin, use your DOCa Codex executable:

codex plugin marketplace upgrade agentwire
codex plugin add agentwire@agentwire

Restart the client or open a new chat to load the updated tools. Existing device approval is reused. The plugin archive includes JavaScript dependencies and requires existing Node 24.13–26; it does not bundle or download a runtime.

Validated: 28 integration tests, TypeScript, formatting, v2 migration, desktop/mobile dashboard, Docker Compose health, and the installed plugin against the deployed relay.