ClawQLStreams
Event-driven autonomous agents you own — not a metered lab runtime.
World events enter. WORM records everything. Significance filters decide when agents wake — with full MCP tools, virtual-key budgets, and Durable Object scale.
One event loop. Three ways to respond.
The same subscription can audit continuously, keep agents ambiently aware, and escalate only when the world crosses a threshold — without a human opening a chat.
Reactive
Every event writes to WORM immediately — compliance-grade recording whether an agent wakes or not.
Ambient
Events buffer in NATS and surface on the next MCP tool call — awareness without spawning a subprocess.
Autonomous
A significance filter escalates only what matters into a full agent session with ClawQL tools and budget.
Anything in. Anything out. Events on the bus.
Protocol Fabric is the event-driven integration layer Streams builds on. ClawQL Core turns any API — or a page's own WebMCP tools — into MCP. mcp-api-adapter turns MCP back into OpenAPI, GraphQL, gRPC, CLI, WebSocket, or /mcp-ui (7 surfaces shipped). NATS JetStream wraps the fabric so the bus can act without a human at the console — Event Stream in, WORM and RTP out.
In — Core → MCP
REST · GraphQL · gRPC · WebSocket · MCP · generated CLI · WebMCP (preview) · QR stream (planned)
Out — adapter → surfaces
OpenAPI · GraphQL · Streamable HTTP · gRPC · gen-cli · WebSocket · /mcp-ui · QR (planned)
QR optical channel is planned as the 8th mcp-api-adapter surface — not shipped yet.
ESB lesson, agent era: N×M protocol integrations collapse to N+M. Streams is how the fabric reacts to webhooks, NATS topics, cron, and live sockets — not only interactive MCP clients. Protocol Fabric docs.
Infinite session scale without losing the audit trail
Streams is built on celld — Deno's self-hosted Durable Objects runtime with LTX replication to your own bucket — or Cloudflare's hosted DOs. Regulated tenants keep Kubernetes HPA until celld is production-stable. Slim Core search/execute runs in-isolate via CoreToolsDO by default; Bun host MCP remains the escape for full catalog and vault.
Virtual-key budgets
Lab sessions bind a virtual key at create and send it on every model turn; production spend ceilings land through
clawql-inferencemodel escalation.WORM on every action
Reactive ingest never waits on the model. Forensic reconstruction is a hash chain you own, not a vendor console export.
Training emission
Optional RTP + OpenBenchTrace export with consent scopes — the Intelligence Flywheel without surrendering sovereignty.
The pattern labs built for themselves — as a platform
Stripe Minions, Anthropic Managed Agents, and OpenAI Agents SDK all implement event → context → reason → tools → audit. ClawQL Streams is that pattern with operator-owned infrastructure.
| Capability | Stripe Minions | Managed Agents | Agents SDK | ClawQL Streams |
|---|---|---|---|---|
| Sovereignty | Internal only | Anthropic-hosted | Managed runtime | Self-host or Cloudflare |
| Triggers | Slack reactions | Cron / API | Pipeline / API | WebSocket · NATS · webhook · cron |
| Tools | Custom Toolshed | Built-in + custom | Built-in + custom | Any MCP surface via Protocol Fabric |
| Audit | Internal | Provider logs | Provider logs | Operator-owned WORM Merkle trail |
| Scale | Custom | Session hours | Managed | celld · Cloudflare DO · K8s HPA |
Specs and Lab 5b evidence on docs.clawql.com
Lab 5b (celld + CoreToolsDO path) ships today as an opt-in coordination layer over packages you already deploy — inference, payments, NATS, and WORM memory. Agent-facing stream_* MCP tools remain planned.
- ClawQL Streams specification — event loop, delivery modes, significance filters, training emission
- ClawQL Durable Objects — SubscriptionDO, AgentSessionDO, sidecars, K8s parity
- ClawQL celld integration — self-hosted DO runtime, LTX WORM trail, fleet deploy
- mcp-api-adapter — five (plus WebSocket) surfaces that complete the Protocol Fabric
Put an event loop under your agents
Request early access on the Agentic Gateway today. Lab 5b already runs on the same MCP endpoint, vault, and WORM trail — Streams coordination is not a second product.