Ctrl K
ComunidadGuías…
GITHUB · ANALIZADO

atrium

Atrium is a self-hostable, multi-user web chat UI for AI agent gateways (OpenClaw and Hermes). It provides streaming replies, file exchange, per-user routing, voice dictation, structured activity monitoring, branch conversations, and an observability API. Built on React + Vite with Convex backend.

Ficha actualizada 22 sept 2026, 23:24 · upstream 22 sept 2026, 23:06 · release v0.84.21

00

Qué es atrium

Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.

Atrium is a clean, self-hostable multi-user web chat interface designed for AI agent gateways. It unifies multiple agents into a single conversation flow with streaming responses, file sharing, per-agent routing, and built-in observability. The UI is capability-driven — it only exposes features that each gateway provider supports, making it agnostic to underlying technology. Atrium sits between the browser and any external agent gateway (OpenClaw or Hermes), normalizing their event streams into a stable Convex backend model.

CASOS DE USO
  • Multi-agent orchestration with per-user routing across multiple gateways
  • Real-time collaboration where different agents handle distinct parts of a conversation
  • Enterprise-grade agent management with full audit trails and metadata tracking
  • Voice-assisted interaction for accessibility or hands-free use in team environments
  • Branching conversations to explore hypotheses without losing context from the main thread
  • Observability-driven operations — monitoring tool calls, agent performance, and system health
PUNTOS DESTACADOS
  • Provider-agnostic UI that adapts to any gateway (OpenClaw or Hermes) via a capability-driven discovery mechanism
  • Streaming replies with stable contracts across provider versions without requiring protocol changes in the frontend
  • Full internationalization support including French as default language
  • Built-in voice dictation and read-aloud capabilities for accessibility
  • Branch conversation feature allowing safe exploration of hypotheses while preserving context from the main thread
  • Structured agent activity monitoring with inline tool call visualization
PRECAUCIONES
  • The UI is currently limited to OpenClaw and Hermes gateways; other providers are not supported out-of-the-box
  • File exchange requires a designated 'converter' agent for document processing (PDF, images, etc.)
  • Voice dictation depends on the gateway provider exposing TTS capabilities — browser voices only work in-browser
  • The Convex backend is self-hosted and must be provisioned separately from the frontend
  • No native multi-agent conversation history persistence across sessions without manual intervention
01

Perfil de infraestructura

Estimación inicial derivada del repositorio y de los servicios detectados.

CPU4 vCPUrecomendación inicial
MEMORIA4 GBRAM estimada
DISCO10 GBalmacenamiento base
COMPLEJIDADhighnivel de operación
02

Despliegue detectado

Qué señales reales de instalación hemos encontrado.

Despliegue manual

Deploy Atrium using Docker Compose or Helm. Set up a Convex instance for the backend, then run: cd deploy/compose && cp .env.example .env and ./bootstrap-env.sh to configure auth, bridge wiring, and environment variables. The frontend is served from npm packages (prebuilt bundle) with a /config.json file specifying the Convex URL. For production, consider Helm charts or Kubernetes manifests for scalability and rolling updates.

—Dockerfile
—Compose
—One-click
03

Stack y dependencias

Componentes inferidos a partir de manifests, configuración y documentación.

FRAMEWORKS
Next.jsReactNode.js
SERVICIOS
No detectados
BASES DE DATOS
No detectadas
PUERTOS
No detectados
05

Puede sustituir a

Relaciones detectadas por el análisis del repositorio y su categoría.

06

Experiencia real de la comunidad

Ayuda a contrastar la estimación automática con instalaciones reales.

Todavía no hay datos comunitarios para este proyecto.