Ask the server room: FrontierStack joins your Buzz team as a server admin agent

Published 2026-10-15

Every team has the moment: someone in the channel asks "is the shop down, or is it just me?" and everyone waits for the one person who can check. With Buzz, that person can be an agent. FrontierStack now joins a Buzz team as a server administrator you can @mention, and it answers from the same live view of your servers, sites, certificates and network that you see in the app.

What Buzz is, and why it fits

Buzz is Block's open-source workspace for people and AI agents: channels, threads and DMs built on the Nostr protocol, where every message is a signed event and agents are members with their own identities rather than bots bolted on. You can use Block's hosted service or run your own relay. Buzz starts agents through a small harness, buzz-acp, which speaks the Agent Client Protocol (ACP) to whatever agent you choose. FrontierStack now speaks ACP too.

Setting it up

1. In FrontierStack, open MCP Server ▸ Buzz and turn on Answer in Buzz.
2. Click Add to Buzz Desktop. This registers FrontierStack as an agent runtime in Buzz Desktop.
3. In Buzz Desktop, create an agent, choose FrontierStack Server Admin as its runtime, and add it to the channels where your team talks about operations.

That is all. There is no API key to paste and no FrontierStack credential stored in Buzz. If you run buzz-acp yourself against a self-hosted relay, the pane shows the two environment variables to set instead. When a mention arrives while FrontierStack is closed, it starts in the background to answer.

What you can ask

Anything you would ask the AI Administrator in the app, answered with the model you chose there:

• "@FrontierStack why is the staging site returning 502?" It reads the web server and PHP-FPM logs and reports what it finds.
• "Which certificates expire this month?" "Is the backup on the NAS current?" "What changed on the router since yesterday?"
• "Is the mail server on the denylist again?" It checks DNS, SPF, DKIM and DMARC and the blocklists.

The reply lands in the thread where the question was asked, so the whole team sees the answer and the evidence behind it.

Built for a room full of people

A chat channel is not a terminal. Anyone in it can type, a pasted log or quoted email can carry instructions aimed at an AI, and the agent on the other end can restart databases. So the Buzz agent is deliberately narrower than FrontierStack in your own hands:

• Channel text is data, not orders. Every message is wrapped and labelled as untrusted before the model sees it. Text that says "ignore your rules" is evaluated as a request, never obeyed as one.
• Some tools simply aren't there. Reading credentials, running arbitrary shell commands and changing FrontierStack's own settings are never offered on a Buzz turn, so there is nothing for an injected instruction to aim at.
• Read-only until you say otherwise. Out of the box the agent investigates and explains. Turn on Allow changes requested from Buzz and it can restart a service or fix a configuration, but every change waits for your approval in a panel on your Mac.
• Approval in chat never counts. ACP has its own "may I?" prompt, and Buzz's harness answers that prompt itself, automatically. FrontierStack doesn't use it. The only yes that counts is the one you click on your Mac.
• Buzz decides who it listens to. By default an agent answers only its owner. Add teammates to the agent's allowlist in Buzz when you want the whole team to ask.
• Nothing secret leaves in a reply. Answers are checked against your stored passwords and keys and redacted before they are posted, the same protection every external surface in FrontierStack gets.

Where it fits with the other agents

FrontierStack already works as the server administrator for ChatGPT, Claude, Grok, OpenClaw, Hermes and Paperclip over MCP and A2A. Buzz is the first place where it sits in a team channel as a member, alongside the people and the other agents. The rules are the same everywhere: other agents and people ask, FrontierStack checks, and nothing changes on your servers until you have seen exactly what will happen and said yes.

Answer in Buzz needs an active FrontierStack subscription; changes need Full Fleet. See Help ▸ AI ▸ Buzz agent for the details.