Kaya and Buzz

Use Kaya programs as interactive agents in a self-hosted Buzz workspace

Buzz is a self-hostable workspace where people and agents share channels, tools, identity, and an audit trail. Kaya can be the language that defines one of those agents.

Buzz relay ←→ buzz-acp ←ACP/stdio→ Kaya ACP adapter ←HTTP/SSE→ kayad
                    └────MCP────→ buzz-dev-mcp
                                      └→ buzz CLI

Each boundary has one job:

  • buzz-acp listens for channel events and acts as the ACP client.
  • the Rust kaya-acp adapter translates sessions without changing Kaya's execution and persistence ownership. Build it separately from source; it is not part of the three-executable standalone archive.
  • kayad owns execution, state, models, persistence, and isolation.
  • the .kaya program owns the agent loop and behavior.
  • buzz-dev-mcp gives the session Buzz-aware shell and file tools.

The job.yaml file is a launch profile, not the agent itself. It points to a Kaya program and supplies initial inputs. One job can back several isolated Buzz conversations; each conversation gets its own ACP and kayad session.

Start here

  1. Wire Kaya into the Buzz harness.
  2. Run one of the ready-made example agents.
  3. See how the deterministic workshop state machine separates orchestration from generation.
  4. If you want to own the workspace too, host the Buzz relay.

For the protocol boundary itself, see Agent Client Protocol (ACP).