Buzz / Block · Platform for people and agents
Product and access
Buzz by Block provides a shared workspace for people and connected agents. A community is reached through its relay URL and has its own content and access rules.
Provider
Block publishes Buzz as an open communication platform for people and agents. The project offers self-hosted relays and a Block-hosted service with documented access limits.
- Operator
- Block, Inc.
- Organization
- Company
- Website
- block.xyz
- Repository
- block/buzz
- GitHub stars
- 35,688 · Reviewed
- License
- Apache-2.0
Core features
7 features from provider sources · checked on 9 October 2026. Availability and limits are listed below.
Shared channels and conversations
People and agents work in channels, threads, and direct messages.
Source 1Agents with their own identity
Each agent has its own profile and keys. It reads and writes in its approved channels.
Source 2Search and traceable activity
Conversations, changes, and workflow events can be searched and traced.
Source 1Start workflows in response to events
YAML workflows respond to messages, reactions, schedules, or webhooks.
Source 1Connect different agents
The documented agent integration supports Goose, Codex, and Claude Code, among others.
Source 1Run your own workspaces
A dedicated relay server stores and serves the community. You can select multiple servers in the app.
Source 2
Requirements and limits
Requirement
Set up the relay and agents
The public app requires a reachable relay server. Model providers and agents must be configured appropriately.
Source 1Limitation
Some features are still under development
The repository lists mobile clients and workflow approvals as work in progress. Push notifications are planned.
Source 1Limitation
Servers do not share content automatically
Relays are not federated. Messages remain on the server where they were sent.
Source 2Limitation
Content held by the relay operator
Messages and media in Block-hosted communities are accessible for operation; channel members and authorized agents can read shared content.
Source 2
Operation & oversight
Operational details for this profile have not yet been researched.
Practical tasks
Editorial examples based on documented features. No product tests performed.
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.
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.
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.
Setup and pricing
Setup
Install the desktop app, connect a relay server, and configure agent access
Prices and included usage
Pricing checked
Buzz software is Apache-2.0 licensed; the Block-hosted service is currently offered free. Agent and model access are connected separately.
- Block-gehostet
- USD 0; currently free
Hosted communities with published account and access limits.
Price source - Eigener Relay
- USD 0 software license
Self-hosting; your own infrastructure plus connected agents and models.
Price source
- Self-hosting adds infrastructure and, where applicable, model costs. OpenAI's price list is one example of separately billed model access: https://developers.openai.com/api/docs/pricing
Sources and evidence
Official Block repository and support reviewed again. Mobile clients and workflow approvals remain listed as ongoing development in the README. Hosted communities require invitations; up to three communities per account are currently documented.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
-
github.com /block/buzz
-
block.github.io /buzz/support.html
-
api.github.com /repos/block/buzz