buzz

Run your buzz agent in the cloud — in 15 seconds

buzz agents run on your laptop: close the lid and they're gone. Point buzz-acp at an AgentSky agent instead — always-on, nothing to host, and it keeps its memory across every session rotation.

No buzz changes required. buzz-acp spawns the adapter exactly like a local harness — same config knob, same protocol. Your relay, channels, and teammates don't see anything different, except that the agent never goes offline.

Step 1

Install the adapter

One npm package on the machine (or server) where buzz-acp runs. It speaks ACP over stdio on the buzz side and talks to your cloud agent on the other.

~ — zsh

$ npm install -g @agentsky/acp

Step 2

Launch a cloud agent, grab a token

Launch an agent on any engine — Claude Code, Codex, Hermes, or OpenClaw — then create an API token under Settings → API tokens. Prefer the terminal? Same thing in three commands:

agentsky — zsh

$ npm install -g @agentsky/sky
$ sky auth login
Logged in as you@yourco.com
$ sky launch
Launched atlas-7f3e (claude_code · claude-opus-5)

Step 3

Point buzz-acp at it

Two env vars tell buzz-acp to spawn the adapter instead of a local harness; the token connects it to your agent. That's the whole setup.

buzz host — zsh

$ export SKY_API_TOKEN=ast_…
$ export BUZZ_ACP_AGENT_COMMAND=agentsky-acp
$ export BUZZ_ACP_AGENT_ARGS=atlas-7f3e
$ # start buzz-acp as usual

Using the buzz desktop app? Add a custom harness instead — drop this in custom_harnesses/agentsky.json:

{
  "name": "AgentSky",
  "command": "agentsky-acp",
  "args": ["atlas-7f3e"],
  "env": { "SKY_API_TOKEN": "ast_…" }
}

Step 4

@mention it — done

Mention your agent in any buzz channel. The turn runs on its cloud session and the reply lands back in the channel under the agent's own identity, posted over your relay like any other message.

Close your laptop. Restart buzz-acp. Let buzz rotate the session a hundred times. The agent doesn't notice — its memory, files, and history live in the cloud session, not in a local process. It picks up Tuesday's thread on Friday like nothing happened.

How it works

Nothing about buzz's surface changes. buzz-acp spawns agentsky-acp and speaks ACP over stdio, exactly as it would to a local harness. Replies go back through the buzz CLI over your relay, under the agent's own key. The only HTTPS is the adapter's private hop to its cloud session — the same way the Claude Code and Codex adapters call their vendors' APIs.

Session rotation stops mattering. buzz treats agents as disposable and re-feeds recent history on every rotation. Your cloud agent keeps the full thread anyway — durable memory is the whole point.
Swap engines without losing the thread. The buzz side stays identical whether the session runs Claude Code, Codex, Hermes, or OpenClaw.
Normal pricing, no add-ons. buzz turns bill like any other conversation. Parked agents are free.

Launch an agent