Connecting Buzz to Landfall

Buzz is Block's open-source team chat where humans and AI agents work side by side, and each agent runs on a team member's own machine. That fits Landfall well: the investigator your team talks to in Buzz is a local agent that joins a Landfall war room through a share link, exactly like a responder's coding agent does. This guide covers three independent things: putting a Landfall investigator in a Buzz channel, attaching it through Landfall Edge for room context and capture, and posting incident updates into a channel. Opening a war room from a Buzz message has its own page under Triggering integrations → Buzz.

What you'll need

• Buzz Desktop 0.5.19 or newer on the Mac that will run the agent, signed in to your team's relay.
• The Landfall CLI 0.7.4 or newer on that Mac, signed in (brew install landfalls-ai/landfall/landfall && landfall login). Check the version with brew list --versions landfall.
• For the channel updates section: an admin seat on your Landfall organization, and owner or admin rights on the Buzz channel you want updates in.

1. A Landfall investigator in a Buzz channel

The Landfall Investigator persona pack is published at landfalls-ai/landfall-buzz-pack. On Buzz 0.5.19 you create the agent by hand from the pack's persona; newer Buzz versions that install packs directly can use the release archive instead.

1. Print the persona

   TerminalCopy

   git clone https://github.com/landfalls-ai/landfall-buzz-pack.git
   /Applications/Buzz.app/Contents/MacOS/buzz pack inspect ./landfall-buzz-pack

2. Buzz Desktop → Agents → New agent

   Name it Landfall, paste the persona body (everything after the frontmatter in agents/landfall-investigator.persona.md) as its instructions, and set the MCP command to landfall serve. Choose who may talk to it; owner-only is Buzz's default and an allowlist suits a team.

   Buzz Desktop → Agents → New agent

   🖼Buzz Desktop's create-agent form with the name Landfall, the persona pasted as instructions, and the MCP command set to landfall serve.

3. Hand it an incident

   In any channel the agent is a member of, mention it with a share link minted from a war room's Share control. The link alone is the whole ask.

   BuzzCopy

   @Landfall https://app.landfalls.ai/j/abc123

   The agent joins, reads the brief, and replies in the thread naming the incident. On the Landfall timeline you see its join, then whatever it shares; every claim goes through the room's admission gate like any other external agent's, and any fix it suggests is a proposal for a human to apply. It never executes anything.

   Buzz channel thread

   🖼A Buzz thread where a member posted a share link and the Landfall agent replied with the incident name and the first line of the brief.

2. Attach through Landfall Edge instead

With Landfall Edge on the same Mac, the Buzz agent becomes a full war-room member rather than a chatbot with tools: every turn carries the current room context, what the agent does is captured into the incident timeline, and Edge's local guardrail decides on each tool call. Nothing is written into Buzz's own files; Buzz keeps the agent's identity and key.

1. Landfall Edge → Attach → Buzz Desktop

   Pick the channel. Edge opens Buzz's own create-agent form, prefilled with the Landfall persona, and shows the two values to paste: agent command landfall-edge with argument acp, and no MCP command (Edge declares its own tools). Save in Buzz; Edge flips to verified when it sees the agent.

   Landfall Edge → Attach → Buzz Desktop

   🖼Edge's attach picker with the Buzz Desktop row selected, the channel chosen, and the paste-these-values step showing landfall-edge and acp with copy buttons.

2. What changes

   A share link in a Buzz message joins through Edge even before Edge itself has joined anything; later turns are bound to that incident. If Edge is not running, the agent still answers with Landfall's tools only and says once, in the thread, that capture and the guardrail are off. Detach from Edge removes the attachment and shows the owner's archive step in Buzz.

3. Incident updates in a Buzz channel

Landfall can post the incident lifecycle (opened, status changes, acknowledgement, resolution) and admitted findings into one channel of your Buzz workspace, threaded per incident, and keep the channel canvas as a markdown summary of the incident dashboard with a link to the live canvas. Landfall generates its own Buzz identity for this; the private key never leaves Landfall and you only ever see the public one.

1. Settings → Integrations → Chat → Buzz

   Enter the relay address and the channel id (from buzz channels list), then Connect. Landfall shows the new bot identity as an npub.

   Settings → Integrations → Buzz

   🖼Landfall's Buzz connection panel after Connect: the generated npub with a copy button, the add-member command, the attestation field, and the standing-approval checkbox.

2. Admit the bot in Buzz

   A channel owner or admin adds the identity as a bot member (the panel shows the exact command with a copy button). For a closed channel, Buzz's relay also expects an owner attestation of the bot identity; produce it with your owner identity and paste the resulting auth tag into the panel's attestation field. Then press Verify: Landfall confirms it can see the channel.

   TerminalCopy

   buzz channels add-member --channel <channel-id> --pubkey <bot pubkey> --role bot

3. Approve the message templates, then turn on real egress

   Posts are templated facts and already-admitted claims, never free text an agent wrote, so you approve the templates once as a standing approval; a template change pauses posting until an admin approves the new version. Real egress is off by default: until you switch it on under On-call → Real egress, every post is recorded on the timeline as simulated and nothing leaves Landfall.

What appears in the channel, and what does not

• A root message per incident (title, severity, war-room link), and every later update as a reply in that thread.
• Status and severity changes, page acknowledgements, resolution, and each claim once it is admitted. Staged or contested claims are never posted; a demoted claim posts a retraction.
• The channel canvas gets a clearly delimited Landfall section with one line per widget and the live-canvas link; everything outside that section is left exactly as your team wrote it.
• Never: agent-drafted prose, remediation approvals, credentials, or anything from a channel Landfall was not connected to.

What the investigation agent can read

Once connected, Buzz appears in the investigator's signal catalog like any other source: the agent can read the messages around a triggering message and its thread through the same credential proxy every provider uses, with no Buzz-specific agent code. See the Integrations architecture page for how that discovery works.

Reference

• Persona pack: https://github.com/landfalls-ai/landfall-buzz-pack
• Opening a war room from Buzz: Triggering integrations → Buzz
• Landfall Edge: Deploy Landfall Edge
• Rotate the bot identity any time from the same panel; open incidents start a new thread on their next post.