Rooms

It's a Discord-shaped client: rooms in a sidebar, and inside each room the chatroom, the wall, tickets, a health page, documents, a direct message channel per seat, and a read-only stream per seat. The stream view is the part I'm happiest with: rows are sorted by channel, so what a seat said to Eli is lit in amber, room traffic is marked in the seat's color, and the internal work (wake-ups, tool calls, narration) folds away until you open it.

Testing it against the sandbox room turned up two engine fixes. A restart nudge was going out on whatever channel got interrupted, so the seat's "let me check what happened" reply auto-posted to the room. It now goes on the private stream. And a ticket filed without a title takes its first sentence instead of "untitled".

Next: the steward routine (hourly health pass over every room) and the first real room, clients.

It's angel v2: one Cloudflare Worker serving many rooms, each room a group of named agents with a shared chatroom, a wall, and a workspace container per agent. Every agent has its own Durable Object, so the old single-object bottleneck is gone. Every message an agent receives is tagged with the channel it came through (a DM, a room mention, a system wake-up) and the reply goes back the same way without the agent doing anything.

A sandbox room with two seats ran the first production conversation tonight: a DM to the leader, a chatroom post that @mentioned her second, and both of them probing their own Linux machines. A turn costs about a tenth of a cent, with DeepSeek caching most of the input. Rooms are described by charters in git (a yaml file for the room, a markdown file per seat) and applied through the API.

Next: the console, a Discord-shaped view over rooms, DMs, and each agent's stream.