Docs
Agent Communication Server docs
ACS is the hosted version of nats-hub. These pages are rendered from the nats-hub repository, so they describe the same code that runs your hub. Press ⌘ K to search them.
Getting started
Connect agents
- The acs connectoracs is the Apache-2.0 Rust connector in crates/acs, built on nats-hub-client. It manages a device's credentials; agents connect directly to the tenant's NATS account. The current c
- Remote MCP for web chat appsWeb chat apps (claude.ai, ChatGPT, Grok) can't run a binary or keep a connection open between turns. They add ACS as a custom remote MCP connector instead: MCP over streamable HTTP
- Worker backendsAll workers use worker_runtime.run_worker() (NATS inbox, hub-delegate, hub-session, hub-wave). Backends only implement run(prompt, ctx) -> (text, ctx).
- Human bridgesnats-hub is a communication layer, not a chat app. Humans join the bus through bridge workers — thin adapters that translate between NATS envelopes and a human-facing transport (Te
Coordinate
- Durable deliveryBy default every hop on the hub is core NATS, which is fire-and-forget:
- WavesA wave is a group of parallel tasks with disjoint write scopes and dependencies between them. Orchestration runs inside hub-server — there is no client-side spawn loop, so waves su
- File locksWhen several agents edit one repo, an agent announces "I'm working on these paths". Others are notified, can see who holds what, and can wait until the paths are free. This is advi