Rozum: Salas de Reunião para Agentes IA e Humanos
sergey-scherbina/rozum
Sala de reunião multi-interface para agentes IA + humanos com transcrição persistente
Ver no GitHubRuntime local que cria salas de reunião nomeadas onde agentes IA (Claude, Codex, etc) e operadores humanos colaboram em tempo real via MCP. Suporta múltiplas interfaces (TUI, web, Telegram, Discord) com transcrição persistente em disco, sem turnos fixos — todos participam simultaneamente.
Instalação
npx convez-ai sergey-scherbina/rozum1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Colaboração em tempo real entre agentes IA e operadores humanos
- Debugging e auditoria de múltiplos agentes MCP em paralelo
- Prototipagem interativa de workflows com agentes e humanos
- Integração de agentes IA com chats (Telegram, Discord, web)
Veredito

Rozum é uma solução sofisticada e bem-arquitetada para orchestração síncrona de agentes IA com presença humana, ideal para times que precisam de debugging colaborativo e workflows interativos. A implementação em Rust, suporte a múltiplos protocolos (MCP, WebSocket, Telegram, Discord) e transcrição persistente demonstram maturidade técnica, mas exige profundo entendimento de agentes e runtimes MCP.
README
A tradução para o português deste README ainda está na fila.
rozum
Local meeting rooms for live CLI agents and a human operator.
A rozum process owns one named meeting room. Humans join through the TUI; AI
agents (Claude Code, Codex, anything that speaks MCP) join through the bundled
stdio MCP proxy; web browsers, Telegram chats, and Discord channels join
through dedicated bridges. Everyone sees the same transcript and can submit at
any time — there are no fixed turns.
What it is
- A meeting room runtime. One Unix process = one room with a Unix-domain
socket on
$XDG_RUNTIME_DIR/rozum/<room>.sock. - An MCP proxy for agents. Drop
rozum mcp-proxyinto any agent's MCP config; the agent getsrooms.list,rooms.join,meeting.wait_my_turn,meeting.submit,meeting.mark_responding,meeting.leave, andmeeting.status. The proxy auto-reconnects if you restart the room. - A built-in TUI for the human operator: live transcript with scrollback,
per-participant typing/waiting/idle presence, autosizing soft-wrap input,
slash commands (
/name,/kick,/pause,/resume,/stop). - A web bridge that exposes the room over HTTP+WebSocket with a zero-dependency vanilla-JS client (presence row, sticky-bottom scrollback, collapsing long messages, lazy history paging, optional on-disk transcript).
- Telegram and Discord bridges for joining a room from a chat app.
- On-disk transcript persistence so a room survives
rozumrestarts and late joiners can replay history.
Quick start
git clone <repo-url> rozum
cd rozum
git submodule update --init --recursive
cargo run # launch a meeting room with an auto-generated name
In another terminal, list the running rooms:
cargo run -- list
Point an MCP-capable agent at rozum mcp-proxy to join programmatically; see
USER_MANUAL.md for the full agent setup, web/Telegram/Discord
bridges, hotkeys, and slash commands.
Documentation
- INSTALL.md — prerequisites, build, optional features.
- TUTORIAL.md — hands-on walkthrough with examples and best practices around naming rooms, persistence, topics, and agents.
- USER_MANUAL.md — running rooms, TUI controls, MCP proxy setup, bridges, persistence, environment variables.
- SPEC.md — global project spec (runtime contract, invariants).
docs/specs/— per-feature specs.- CHANGELOG.md — completed work, newest first.
Project layout
src/
├── main.rs CLI entry point (clap subcommands)
├── lib.rs library entry
├── backend.rs optional inference backend abstraction
├── meeting/ room runtime, MCP server + proxy, persistence
│ ├── app.rs top-level room driver
│ ├── state.rs Meeting state machine, events, transcript
│ ├── mcp_server.rs Unix-socket MCP server (per room)
│ ├── proxy.rs stdio MCP proxy (agents)
│ ├── budget.rs per-room char budgets
│ └── participant.rs human + agent participants
├── tui/ ratatui terminal UI for the operator
├── web/ HTTP + WebSocket bridge for browsers
├── telegram/ Telegram bridge
└── discord/ Discord bridge
Development
cargo fmt --check
cargo test
cargo build --release
This repository uses
agent-plugins as a git submodule for
multi-agent (coordination across feature-branch agents) and spec-dev
(spec-before-code workflow). See AGENTS.md.
License
Apache-2.0. See LICENSE.