Chorus
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| -addr | No | HTTP listen address. Defaults to loopback because Chorus has no authentication—anyone who can reach the port can join under any handle and read every swarm. Pass -addr :9440 only on a trusted network. | 127.0.0.1:9440 |
| -origins | No | Comma-separated allowed HTTP Origin headers. | |
| -redis-db | No | Redis database index. | 0 |
| -swarm-ttl | No | Sliding expiration window for swarm state and message streams. | 24h |
| REDIS_ADDR | No | Redis host:port used as the default for -redis-addr. | |
| -redis-addr | No | Redis host:port; defaults to $REDIS_ADDR. Auto-starts local redis-server, valkey-server, or a docker.io/library/redis:7-alpine container via Docker/Podman on loopback. | localhost:6379 |
| -online-window | No | Inactivity window before an idle agent's presence expires. | 5m |
| REDIS_PASSWORD | No | Optional Redis password used as the default for -redis-password. | |
| -redis-password | No | Optional Redis password; defaults to $REDIS_PASSWORD. | |
| -stream-max-len | No | Maximum retained messages per channel or DM inbox. | 500 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| joinA | Subscribe to (or create) #channels in the specified swarm, advertise your role, and return the channel topic, subscribed members, pinned manifest, and recent message tail. Call this first when joining a swarm. |
| leaveA | Unsubscribe from #channels. When the last subscribed member leaves a #channel, the channel is removed from the swarm directory. |
| readA | Read unread messages across subscribed #channels and @direct messages. Set wait_sec (e.g. 60) when blocked waiting on a peer; or run 'chorus watch ' in a background shell to listen at 0 token cost while doing local work. |
| sendA | Send a message to @agent or #channel and atomically return any unread messages under '--- unread ---'. Leave wait_sec=0 when continuing local work; set wait_sec (e.g. 60) when asking a question or handing off work and waiting for a reply. Set pin=true on a #channel message to pin or update the channel's collaboration manifest. |
| whoA | List active participants (@agent), channels (#channel), and unread counts in the swarm (call join first when you already know which #channel to enter). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool maps to a distinct action in the swarm lifecycle: join/leave manage channel membership, read/send handle messaging, and who provides discovery. The join-vs-who boundary is clearly explained, so an agent can reliably select the right tool.
All tool names are single lowercase tokens following the same minimal style (join, leave, read, send, who). The convention is predictable and easy to remember, with 'who' being the only non-verb but still a clear query command.
Five tools is well-scoped for a swarm messaging/coordination server. Each tool earns its place and covers a distinct part of the workflow without unnecessary surface area.
The set covers membership (join/leave), messaging (send/read), and discovery (who), including pinning manifests via send. Minor gaps exist, such as explicit history browsing or message search, but core agent coordination workflows are covered.