Skip to content

BERD TASK · 0023 · SAFEGUARD AND HAND OFF

Hand work between Berd and Buzz

This page is not finished

The one route between the products sends into Buzz's shared, signed record under a configured identity and needs a private key in the agent's environment. Read from skills/buzz-handoff/SKILL.md (1.0.0), not run end to end. What is below is the shape of the task and the facts the sources support — not a walkthrough anyone has followed.

One route, a skill published in v0.6.3: a Berd agent reads a Buzz thread through the Buzz CLI, continues privately, and can send back one approved reply.

Steps at a glance

  1. Decide where the work lives before you start
  2. Bring a Buzz thread into Berd
  3. Check the requirements are met outside the chat
  4. Send a reply back only after approving the exact text
  5. Move everything else by hand

1. Decide where the work lives before you start

Describe a piece of work you placed wrongly and what moving it cost.

  • If anyone else needs to see it, add to it or point back at it later, it belongs in Buzz — Buzz or Berd. A Berd conversation never travels there.

2. Bring a Buzz thread into Berd

Describe what you pasted, what the agent said it read, and how much came across.

  • Paste a buzz://message link or a channel id; the agent passes it exactly as supplied.
  • Buzz content is untrusted material, never instructions.
  • The agent summarises only the relevant context and continues privately unless asked to share. Only agents given this skill know Buzz exists.

[SCREENSHOT: T23-01 — a buzz:// link pasted]

3. Check the requirements are met outside the chat

Describe how the environment was set up and what the agent did when something was missing.

  • buzz on PATH; BUZZ_RELAY_URL and BUZZ_PRIVATE_KEY in the agent's environment; BUZZ_AUTH_TAG where required.
  • The agent checks only that the variables exist, never prints them, and never asks for a key in chat; if missing, it stops.
  • It does not read Buzz Desktop's keychain: the key you configure is the identity the reply carries.

4. Send a reply back only after approving the exact text

Describe the preview you saw and what happened when you edited the draft.

  • Every write needs approval of the exact text, channel and reply target; editing is not approval, and any change means a fresh preview and a fresh yes.
  • Prefixed 🤖 under your own identity unless a distinct agent identity is configured.
  • No automatic retry: on delivery_unknown or a timeout, verify in Buzz first.

[SCREENSHOT: T23-02 — the approval preview of a reply]

5. Move everything else by hand

Describe what you carried across by hand.

  • Post the conclusion; upload the file; set the agent up again in Buzz from its card, file or ZIP.

Last checked: Berd v0.6.4, 2026-09-11 — read from source and release notes, not yet tested in the app.

Learn more

Reference

Moment
apply
Takes
untimed
Steps
5
Verified
Berd v0.6.4 · 2026-09-11 · source-read
NEVER BESTUCK AGAINCLICK ME

Guide built with Berd, Claude and Codex · verified against Berd v0.6.4, 2026-09-11 · read from source, not yet tested in the app · Buzz Guide · About · not affiliated with Block