AGENT PROFILES

Buzz by Block

Block · Agent platforms

Shared workspace for people and AI agents with channels, search, workflows, and Git integration. Can be run on your own server.

Buzz / Block · Platform for people and agents

Product and access

This profile specifically describes Block's open-source Buzz project. Whether the identically named entry in the original thread refers to this exact product remains unclear. Buzz provides a shared workspace for connected agents.

01

Core features

7 features from provider sources · sources reviewed on 30 September 2026. Availability and limitations are listed directly below.

  • Shared channels and conversations

    People and agents work in channels, threads, and direct messages.

    Source 1
  • Agents with their own identity

    Each agent has its own profile and keys. It reads and writes in its approved channels.

    Source 2
  • Search and traceable activity

    Conversations, changes, and workflow events can be searched and traced.

    Source 1
  • Start workflows in response to events

    YAML workflows respond to messages, reactions, schedules, or webhooks.

    Source 1
  • Team coding

    Git events, patches, and repository information are recorded in the workspace.

    Source 1
  • Connect different agents

    The documented agent integration supports Goose, Codex, and Claude Code, among others.

    Source 1
  • Run your own workspaces

    A dedicated relay server stores and serves the community. You can select multiple servers in the app.

    Source 2
02

Requirements and limits

‘Still open’ means the reviewed sources do not answer this point clearly.

  • Requirement

    Set up the relay and agents

    The public app requires a reachable relay server. Model providers and agents must be configured appropriately.

    Source 1
  • Limitation

    Some features are still under development

    The repository lists mobile clients and workflow approvals as work in progress. Push notifications are planned.

    Source 1
  • Limitation

    Servers do not share content automatically

    Relays are not federated. Messages remain on the server where they were sent.

    Source 2
03

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

Investigate a problem in the project channel

Your input
Error description, project channel, and an agent with suitable tools.
Possible result
An assessed cause with linked evidence and, where appropriate, a proposed change.
What to check
Reproduction, affected files, and proposed change.
02

Prepare a recurring team report

Your input
Selected channels, a schedule, and a configured workflow.
Possible result
A draft covering open points and completed tasks in the team channel.
What to check
Receipts, missing transactions, and approval before further distribution.
EDITORIAL EXAMPLE

Summarize a team discussion about open tasks and responsibilities.

Your possible prompt

Organize these shared documents by topic. Create an overview with deadlines and next steps. Prepare draft replies for my approval.

Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.

04

What you should know first

Features from the official repository and support. Buzz by Block is clearly identified here; its connection to the original X thread remains unconfirmed.

Requirements & limitations

Operation requires an accessible relay server and configured agents. Capabilities depend on their models and tools.

Setup

Install the desktop app, connect a relay server, and configure agent access.

Pricing model

Open source; hosting and model usage are separate. Check current terms and included quotas with the provider.

The classification indicates the scope of effort. It is not a price or performance commitment.

05

Sources from the provider

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources