![\"\"](\"docs/assets/atrium-mark-dark.svg\")
\n \n \n
A clean, self-hostable, multi-user web chat for your AI agents — one UI across agent gateways.
\n\n\n ![\"License:](\"https://img.shields.io/badge/license-MIT-blue\"){kind=icon}
![\"Status:](\"https://img.shields.io/badge/status-early%20%2F%200.x-orange\"){kind=icon}
\n
\n
\n A local instance. The conversation content is fictional.\n
\n\nAn open-source, self-hostable web chat UI for **AI agent gateways**. It gives a\nteam a clean multi-user chat front end across one or more gateways, with streaming\nreplies, file exchange, per-user agent routing, voice read-aloud and dictation,\nand a built-in observability surface. **OpenClaw and Hermes are both supported**\n— each provider lives behind a bridge adapter, and the UI is **capability-driven**:\nit discovers what a given gateway can do and shows only that, so the same front\nend serves either provider without per-provider UI code.\n\n> Atrium is **provider-agnostic by design** and a community project — not\n> affiliated with or endorsed by any gateway vendor. You bring your own gateway\n> (OpenClaw or Hermes); Atrium is the chat surface in front of it.\n\n## Status\n\nEarly but functional, designed as a public, forkable foundation. The project is\n`0.x`: the bridge protocol and APIs are documented and versioned, but breaking\nchanges can still happen before `1.0`.\n\n## What it is\n\nAgent gateways are event-driven and best driven over a WebSocket: a single user\nturn can produce multiple runs, intermediate replies, tool output, generated\nmedia, auto-compaction restarts, and messages that arrive after a browser\nreconnect. Atrium embraces that model instead of fighting it:\n\n- A **React + Vite** front end (TypeScript, built on assistant-ui).\n- A **Convex** self-hosted backend (TypeScript functions + reactive database)\n that owns chats, messages, routing, auth, and the observability data.\n- A **Node/TypeScript bridge** with a **per-provider adapter** (OpenClaw and\n Hermes) that holds a persistent connection to the gateway, normalizes the\n version-specific event stream into a small stable shape, and relays turns to\n and from Convex. The provider is the only vendor-coupled layer. Hermes offers\n two transports — a JSON-RPC WebSocket (the default, richer surface) or an\n OpenAI-compatible REST/SSE API — selectable per instance.\n- An external **agent gateway** (OpenClaw or Hermes) that actually runs the\n agents. Atrium never runs the model itself — you bring your own gateway.\n\nThe front end never parses raw gateway frames; it subscribes to Convex, which is\nfed by the bridge. The result is a stable UI even as providers and versions evolve.\n\n\n