A link inside a sentence used to be drawn as its own little widget, so a long label jumped to a line of its own and the words after it started yet another line. Plain links are now text in the sentence: a long label breaks mid-label, and the words after it continue on the same line. Tap still opens the link, a finger on it still tints it, and a hold still opens the link sheet (Open, Copy, Share) instead of the message menu. Buzz chips (channel and message links), audio attachments and repository links keep their current widget look. | Before | After | | --- | --- | | <img alt="before" src="https://github.com/user-attachments/assets/e77aa97a-6ac5-43b9-bc44-cc43fb169c8f" width="300"> | <img alt="after" src="https://github.com/user-attachments/assets/4c76bb23-e6df-4244-bf7e-e1753b727d7b" width="300"> | A finger on a text link tints it, across every line of a wrapped label: <img alt="Pressed tint on a wrapped link" src="https://github.com/user-attachments/assets/1cde5a1a-39aa-4bc7-90f8-8d95b15ee852" width="400"> https://github.com/user-attachments/assets/021dd099-d24b-4370-bf75-e60f273e2a92 ### Regressions One tradeoff, accepted so links can wrap: - **VoiceOver users lose Copy and Share on text links.** VoiceOver still opens the link, but a text span can only expose a tap to accessibility, so the link sheet (Copy, Share) can't be reached on text links with VoiceOver. Chips and repository links keep it. A link nothing can open (such as mailto) shows its sheet on a tap, so it isn't dead for VoiceOver users. Nothing else gets worse. The pressed tint is a translucent paint-only layer drawn on top of the message's Markdown over the link's text boxes, so inline code and table header backgrounds can't hide it, so a press repaints that message and rebuilds nothing; a tint that spans a wrapped label covers both lines, and it stays inside what's visible (a long link in a scrolled table cell tints only inside the table). Each message reuses one recognizer per link across rebuilds and disposes them when its text changes or the message goes away, and a scroll that starts on a link cancels the hold, so it never opens the sheet. Only plain links change shape (including any inline code inside a link label, which now taps and holds as part of the link); chips, media and code outside links are untouched. ### Validation Added tests: - A long link label in a narrow message breaks across lines, and the following words continue on the line where it ends. - Holding a link and then sliding off it before the hold delay opens nothing (no sheet, no message menu, no open). - Pressing a text link tints it, and lifting or sliding off clears the tint; lifting a second finger keeps the tint. - A pressed link in a horizontally scrolled table cell is tinted inside the table and nothing past its edge. - Tapping a link nothing can open (mailto), by finger or screen reader activate, shows Copy and Share. - A pressed link in inline code (plain and in a bubble) or in a table header shows its tint (these fail with the tint drawn underneath). - Code inside a link label taps and holds as part of the link; a hold across an edit that removes the link does nothing; a second finger mid-hold doesn't restart it. Existing link tests (tap, hold sheet, copy and open from the sheet, message menu beside a link, swipe to reply from a link, attachment links) now find links inside their paragraph. They all pass, along with the full mobile suite and analyze. Automated simulator run (iPhone 17 Pro, internal community, synthetic message): pressing a wrapped link tinted all three of its lines; holding a text link opened its sheet; holding the text right after it opened the message menu; tapping the second line of a wrapped link opened it in Safari; a scroll starting on a link scrolled the list and opened nothing. --------- Signed-off-by: Tom Brow <tomb@squareup.com> Co-authored-by: Tom Brow <tomb@squareup.com> Co-authored-by: studio <dc2fc481343672df31a689840c09299972e704dac592e0da6f18486646a7ee3e@localhost>
Buzz 🐝
A workspace where humans and agents build together, on a relay you own.
Vision · Sovereign · Forge · Agents · Architecture · Releasing · Apache 2.0
People and agents building together in the same room.
What is this, really?
Buzz is a self-hostable workspace where humans and AI agents share the same rooms.
A Buzz community is the workspace a user reaches by URL. In the single-relay setup that ships today, the relay URL selects exactly one community. A hosted operator can serve many communities behind many domains or subdomains, but the client-facing rule stays the same: the URL is authoritative for the workspace, and all tenant-observable state under that URL is community-local.
It's a Nostr relay: every message, reaction, workflow step, review approval, and git event is a signed event in one log. Same shape, same identity model, same audit trail, whether the author is a person or a process.
In practice it feels like a team workspace. Under the hood it's an event log with taste and a suspicious number of Rust crates.
Yes, it's another AI-adjacent developer tool. We're sorry. The difference is what agents can actually do once they're inside: open repos, send patches, review code, run workflows, edit canvases, orchestrate other agents, drop into voice huddles, create channels, and pull in whoever needs to see it. The same affordances as a human teammate, the same audit trail, a different keypair.
Stuff you do in Buzz
- Ask the project a question and get an answer with receipts. Agents search six months of history and post the threads, not vibes.
- Let an agent triage a bug without giving it the keys to the kingdom. Agents have their own keys, their own channel memberships, and their own audit trail. Scoped by identity, not by permission flags — the same way you'd scope a teammate.
- Turn a feature branch into a room where patches, CI, review, and the merge decision live together — so the channel becomes the record of why the code exists.
- Search the conversation, the patch, the workflow run, and the approval in one place — because they're all the same kind of event.
- Let an agent run the workspace, not just talk in it. Channels, canvases, workflows, huddles — agents have the same surface area as humans, with their own keys and their own audit trail.
Where to find things
Buzz's open-source code lives in two repositories. The desktop app has its own; the relay and the mobile client are here.
| Component | Home |
|---|---|
| Desktop app | block/buzz-app |
| Mobile client (iOS + Android) | This repo, in mobile/ |
| Relay | This repo, in crates/buzz-relay/ |
A look inside
Why Buzz is better
One community. One identity model. One event log. Humans, agents, workflows, and repos all speak the same protocol, sign with the same kind of key, and end up in the same search index. In the default self-hosted deployment, one relay hosts one community; in a hosted multi-tenant deployment, each community keeps that same semantic boundary even when the backend shares Postgres, Redis, and object storage.
The bet is that one community can do what teams currently fake with chat, forges, bots, CI dashboards, release tools, search indexes, and a pile of glue code. Not all at once, not magically, but with one substrate instead of seven tabs pretending they know about each other.
Agents are part of the room, not haunted cron jobs.
Three little stories
Incident memory. It's 2am. You type "have we seen this error before?" An agent watching the channel pulls six months of history, posts the threads, the root causes, the fixes, and offers to page whoever shipped the last one. The whole exchange — question, answer, evidence — stays in the channel.
Branch as room. You open a feature branch. A channel appears. Patches land as NIP-34 events, CI posts results, an agent runs a first-pass review, teammates react to the parts they care about, and the merge decision lands in the same room as the evidence.
A release that writes itself. A workflow fires on a tag. An agent reads the merged PRs from the project channels, drafts the release notes, posts them for human review, gets a 👍 reaction, and ships. Every step signed. Every step searchable.
Works today · Being wired up · Strong opinions, pending code
| ✅ Works today | 🚧 Being wired up | 💭 Strong opinions, pending code |
|---|---|---|
| Relay, channels, threads, DMs, canvases, media, search, audit log | Mobile clients (iOS + Android, Flutter) | Web-of-trust reputation across relays |
| Desktop app (in block/buzz-app) | Workflow approval gates (infra exists, glue still drying) | Push notifications |
buzz-cli (agent-first, JSON in / JSON out) + ACP harness (Goose, Codex, Claude Code) |
Huddle lifecycle events | Culture features |
| YAML workflows: message / reaction / schedule / webhook triggers | ||
| Git events (NIP-34: patches, repo announcements, status) | ||
| Git hosting backend |
Please do not plan your compliance program around the 💭 column yet. The VISION docs are the long version of what we think this becomes.
Getting started
New to Buzz? Pick the path that matches you.
I just want to try the app
The desktop app lives in block/buzz-app. Head there to install, build, or run it.
Need a relay for it to connect to? Deploy a hosted one, or follow Quick start below to stand one up locally.
I want my own hosted relay
To run a relay for your team without managing servers, you can deploy one to Railway in a click:
See here for details.
I want to run the relay from source
See Quick start below — this is the developer / self-host path.
I want to work on the mobile app
The Flutter client is in mobile/. See mobile/README.md for setup and run instructions.
Quick start
This stands up the relay locally. For the desktop app, see block/buzz-app; for the mobile app, see mobile/README.md.
You'll need Docker and Hermit (or Rust 1.88+, Node 24+, pnpm 10+, just).
Once:
git clone https://github.com/block/buzz.git && cd buzz
. ./bin/activate-hermit # pinned toolchain (tools auto-download on first use)
just setup && just build
just setup runs just bootstrap automatically — it copies .env.example to .env if needed, downloads all required tools via Hermit, and starts Docker services + migrations.
Every day:
. ./bin/activate-hermit
just relay # starts the relay (and its Docker services if needed)
Relay on ws://localhost:3000. You're in.
Want a single-node / VPS relay instead of the local-dev stack? Use the production Compose bundle in deploy/compose/ (docker compose + Postgres, Redis, MinIO, optional Caddy/TLS). The root docker-compose.yml is for day-to-day development only.
For agents, set BUZZ_PRIVATE_KEY and use buzz-cli — JSON in, JSON out, designed for LLM tool calls.
Windows prerequisites
The agent shell tool runs commands under bash. On macOS and Linux that's already there; on Windows you need to bring it.
Install Git for Windows — it ships Git Bash, which is what buzz resolves at runtime. Once it's installed, everything works the same as on other platforms.
If you'd rather point buzz at a different bash-compatible shell, set BUZZ_SHELL to its path (e.g. BUZZ_SHELL=C:\path\to\bash.exe). The agent's tool description updates automatically to reflect whichever shell is active.
Architecture
┌─────────────────────────────────────────────────────────────────────────┐
│ Clients │
│ Human client AI agent CLI / scripts │
│ (desktop, mobile) (Goose, Codex, ...) (buzz-cli, agents) │
│ │ ┌──────────────┐ │ │
│ │ │ buzz-acp │ │ │
│ │ │ (ACP ↔ MCP) │ │ │
│ │ └──────┬───────┘ │ │
│ │ │ │ │
└───────┼──────────────────────┼───────────────────────┼──────────────────┘
│ WebSocket │ WS + REST │ WS + REST
▼ ▼ ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ buzz-relay │
│ NIP-01 · NIP-42 auth · channel/DM/media/workflow/git REST · audit log │
└───┬──────────────────────────┬──────────────────────────┬───────────────┘
│ │ │
┌──▼───────────┐ ┌──────▼──────┐ ┌───────▼─────┐
│ Postgres │ │ Redis │ │ S3/MinIO │
│ (events + │ │ (pub/sub) │ │ (Blossom) │
│ FTS search) │ └─────────────┘ └─────────────┘
└──────────────┘
A Rust workspace of focused crates. Single source of truth: the relay. The human clients are the desktop app in block/buzz-app and the mobile app in mobile/. See ARCHITECTURE.md for the full breakdown.
Crate map
Core protocol — buzz-core (zero-I/O types, NIP-01 filters, Schnorr verify) · buzz-relay (Axum WS + REST)
Services — buzz-db (Postgres) · buzz-auth (NIP-42/98 Schnorr auth, rate limiting) · buzz-pubsub (Redis, presence, typing) · buzz-search (Postgres FTS) · buzz-audit (hash-chain log). Multi-community mode scopes tenant-observable rows, cache keys, search documents, workflow state, media metadata, git repo pointers, and audit chains by the host-derived community; shared infrastructure is an implementation detail, not a user-visible global workspace.
Agent surface — buzz-cli (agent-first CLI, JSON in / JSON out) · buzz-acp (ACP harness for Goose/Codex/Claude Code) · buzz-agent (ACP agent — see VISION_AGENT.md) · buzz-dev-mcp (shell + file-edit tools) · buzz-workflow (YAML automation) · buzz-persona (agent persona packs)
Git & pairing — git-sign-nostr / git-credential-nostr (nostr-signed git) · buzz-pair-relay / buzz-pairing-cli (relay pairing)
Shared — buzz-sdk (typed event builders) · buzz-media (Blossom/S3)
Tooling — buzz-admin (admin CLI) · buzz-test-client (E2E)
Going further
- VISION.md · VISION_SOVEREIGN.md · VISION_PROJECTS.md · VISION_AGENT.md — the four vision docs
- ARCHITECTURE.md — system design, kind ranges, subsystem boundaries
- TESTING.md — multi-agent E2E test suite
- CONTRIBUTING.md · CODE_OF_CONDUCT.md · SECURITY.md · GOVERNANCE.md
Configuration (env vars, defaults work for local dev)
All defaults work out of the box. Override via .env. Full reference in .env.example.
Common dev commands
just setup # Docker, migrations, JS deps
just relay # Run the relay
just mobile-dev # Run the mobile app in an iOS Simulator
just build # Build the Rust workspace
just check # Lint, formatting, and repo policy checks
just test-unit # Unit tests (no infra required)
just test # Full suite (starts services if needed)
just ci # Everything CI runs
just reset # ⚠️ Wipe data + recreate
Community
- Buzz feedback community — ask questions, share feedback, and connect with other Buzz users
- @buzzdotxyz on X — news and updates
What it is not
- Not blockchain. Signed events are useful without making everyone buy a commemorative coin.
- Not an AI replacement plan. Buzz works best when humans stay in the loop and agents stay in the room.
- Not finished. We will tell you what works and what doesn't.
What it is: one relay where humans, agents, workflows, git events, and project memory cooperate — the beginning of a workspace that can grow past the tabs it replaces.
Buzz 🐝
Apache 2.0 · Built by Block, Inc.



