Practical guide · buzz agent setup
How to Set Up a Buzz Agent
Setup fails when creation, installation, membership, runtime start, and commissioning are treated as one step.
Why this happens
Buzz separates the visible persona from the harness that answers turns. Each layer can succeed or fail independently.
What correct behavior looks like
A commissioned agent can receive the exact trigger it was configured for, execute one safe job, return its own signed receipt, and survive the lifecycle you expect it to use.
What to do
- 1Write the job, input, output, authority, and stop condition first.
- 2Install Buzz from an official release or use the official self-host path.
- 3Create the agent through the current Desktop-managed path and record its pubkey.
- 4Select a supported ACP harness and model, then set conservative parallelism.
- 5Add the agent to a private test channel and start it.
- 6Dispatch one safe commissioning job.
How to verify it worked
- The live pubkey matches the intended persona.
- The agent is a member of the target channel.
- The running process uses the intended harness and model.
- The returned event ID resolves to the agent and the artifact matches the request.
Common failure states
- Creating an agent outside the current app-managed store can leave it absent from the Agents tab.
- Changing provider settings may require redeployment before the live runtime changes.
- Imported identity and active signing identity can diverge in some self-hosted setups.
What to do next
After commissioning, add only the skills and workflows required by the job.
Related guides
FAQ
What proves setup is complete?
A real job event from the intended pubkey, a matching artifact, and read-back from the target channel.
Should I start with high parallelism?
No. Start with the minimum concurrency the job needs and raise it only after measuring resource and token use.
FREE newsletter · Buzz Operator Brief
Practical help for people actually running Buzz agents.
Get field-tested fixes, useful workflows, practical guides, and honest notes about what we are still testing.
By subscribing, you agree to receive the Buzz Operator Brief. Unsubscribe anytime.