Atmosphere

Atmosphere

The real-time engine for AI agents on the JVM. Tokens flow from the LLM runtime to the client through a broadcaster you can filter, gate, and observe — over WebSocket, SSE, long-polling, or gRPC, and out through MCP, A2A, and AG-UI. A plain @Agent is a full deep agent, batteries-included, and Atmosphere handles reconnect, authorization, and governance.

---

Atmosphere is built for teams that need AI agents to behave like production services: streaming over real transports, guarded before every tool call, observable by tenant and run, and portable across AI frameworks without rewriting the endpoint.

Why Atmosphere

Need	What Atmosphere provides
Stream to real clients	WebSocket, SSE, long-polling, and gRPC run through one broadcaster pipeline as always-on defaults; WebTransport over HTTP/3 is optional
Swap AI integrations	One AgentRuntime SPI with twelve runtime adapters and contract-tested capability flags
Ship a deep agent	A plain @Agent is batteries-included — memory, a plan (write_todos), a virtual filesystem, and sub-agent delegation (task), on by default via the harness
Govern execution	Policy admission, @AgentScope, human approval, plan-and-verify, cost ceilings, PII rewriting, and admin kill switches
Pause for humans	Durable HITL approvals hibernate without holding a thread, persist workflow state, and resume through REST approval surfaces
Resume long runs	Durable sessions, run IDs, replay buffers, checkpoints, and reconnect-safe continuation
Observe and replay	An opt-in session tape records session-boundary AI events (SQLite-durable) — reconstruct a run or a coordination tree with no model call, then distill a smaller model from it
Expose the same agent everywhere	Browser endpoints plus MCP (stateless RC on the MCP 2026-07-28 spec, sessions back to 2024-11-05), A2A, AG-UI, Slack, Telegram, Discord, WhatsApp, and Messenger modules

Scope

Atmosphere is a real-time, event-driven framework, not an agent-hosting platform. We ship the primitives your application uses at runtime; the host you choose (Tomcat, Jetty, Netty, Undertow, Quarkus, Spring Boot, or any servlet container) owns compute and scheduling. Payment rails and commerce primitives are out of scope. Compared to the agent-platform stack vocabulary that has emerged around offerings like Cloudflare Agents, AWS Bedrock Agents, and Vertex AI Agents: