TeamRoom

Inspiration

Everyone we know now pays for more than one AI - and coordinates them by hand: five tabs, copy, paste, re-explain, repeat. The AIs never meet. We wanted the obvious thing: one room where they work with you and each other.

What it does

TeamRoom is a local-first team chat for one human and a team of AI personas. Create project rooms, @mention teammates, drop in files. Mention @Ray and one persona answers. Call @team and a researcher, a builder, and a critic reply in parallel, read each other's takes, and a coordinator (Clara) synthesizes decisions and next actions. Drop a CSV and the team analyzes it live. Attachments are deduplicated by content hash; small text files are fed into the personas' context.

How it works - no API keys, no new bills

Every persona is GPT-5.6 running through Codex's non-interactive mode, authenticated by an ordinary ChatGPT subscription. There is no database: rooms and messages are append-only Markdown files in one sandboxed folder - your own cloud-drive sync becomes free backup, and the archive outlives the app. The server dispatches agent runs only when a persona is mentioned - no polling, no idle cost - with hard caps on turns, timeouts, and context, so cost is bounded by construction. A file-watcher streams new messages to the UI over SSE, so anything that writes a file into a room appears live.

How Codex and GPT-5.6 were used

Codex built the entire application in a single session: nine phase commits, an 85-test mock-first suite that spends zero model quota, live persona handshakes, and one rehearsed demo - the full trail is in BUILD_LOG.md and the linked Codex session. Codex is also the runtime: every teammate judges see is GPT-5.6 (Sol + Terra) speaking through Codex. Built with Codex; running on Codex.

Safety by design

The app can only touch its own folder (every path is guarded), messages are append-only with no delete codepath, engines are spawned without a shell, the server binds to localhost only, and message and file content is treated as data, not instructions.

What's next

The room is provider-neutral by architecture - any agent that can read and write the folder can join. Next: guest agents via cloud-drive relays, an MCP port so any client plugs in, and multi-human rooms.

Built With

• codex