Buzz Is Here: Why Tint Shops Should Start Using Jack Dorsey’s Agent Workspace Now

Jack Dorsey’s Block released Buzz in July 2026—a free, open-source workspace where humans and AI agents share the same channels. It looks like Slack. Under the hood it is something else: signed events on a Nostr relay, portable cryptographic identities for people and agents, built-in Git repos, and YAML workflows that agents can run with audit trails.

If you run a tint, PPF, or restyling shop, you should not wait for your CRM vendor to “add AI.” Pilot Buzz now—even with three people—because the shops that learn agent-native ops in 2026 will out-execute the ones still copying SOPs from Facebook threads in 2028.

What Buzz actually is (not the Twitter recap)

Buzz is published at buzz.xyz with source at github.com/block/buzz under Apache 2.0. Block built it to reduce its own dependence on Slack and GitHub while giving AI agents first-class membership in team chat—not bolt-on bots with a shared login.

Core pieces installers should care about:

| Capability | Why it matters in a bay | | --- | --- | | Channels + threads | Replace scattered text threads with searchable ops history | | Agent members | Claude Code, Codex, goose, or custom agents post and act in-channel | | Cryptographic identity | Every person and agent has its own keys—permissions are scoped, auditable | | Git in the workspace | Price sheets, checklists, and scripts live next to the conversation | | Workflows | Automate “new lead → summary → assign tech” without Zapier glue | | Self-host or hosted | Run your relay or start on Block’s hosted buzz.xyz |

Dorsey described Buzz as “model-agnostic, decentralized, self-sovereign, and open source.” That is not marketing fluff for tint—it means you can point agents at the LLM you already pay for and keep message history on infrastructure you control.

Why tint shops specifically should move now

Most shops already run a fragile stack: Tint Wiz / OrbisX / Jobber for jobs, Google Voice or Podium for texts, Meta for leads, and WhatsApp or iMessage for the team. Nothing talks to anything else. Owners re-explain the same rules every Monday.

Buzz does not replace your CRM on day one. It replaces the chaos around it:

1. SOP velocity — An agent in #install-standards drafts bay checklists from your notes; the lead tech edits in-thread; the final version lands in Git. No more “version 7 in someone’s camera roll.”

2. Lead triage — Paste a Meta lead or LSA export into a channel; an agent summarizes vehicle, package interest, and follow-up window. Front desk approves before anyone texts.

3. Multi-location memory — Store #2 asks the same ceramic upsell question Store #1 answered last month. Buzz search + agent Q&A over pinned threads beats scrolling SMS.

4. Vendor and law research — Perplexity-style research, but inside the workspace where managers see citations and can pin “do not quote customers until verified” rulings (see our NY VLT coverage).

5. No per-seat Slack tax — Open source + self-host is a real COGS win for 5–15 person groups paying per-seat chat tools.

The counter-argument is fair: Buzz is early (desktop-first; mobile still maturing). That is exactly why you pilot now with low risk instead of migrating 40 seats in Q4.

The 48-hour rollout (do this immediately)

Hour 0–2: Create the workspace

• Download Buzz from buzz.xyz (macOS, Windows, Linux).
• Create a community: #general, #leads, #install-sops, #film-qc.
• Invite owner, lead tech, front desk—three humans max for week one.

Hour 2–8: One agent, one job

• Add one agent (goose, Claude Code, or Codex—whatever your team already touches).
• Give it a single mandate: “Draft a front-window tint QC checklist from our current verbal rules.”
• Human edits in-thread; export final to Git in Buzz.

Day 2: Wire one workflow

• New lead template: vehicle YMM, glass scope, film tier, deposit status.
• Agent fills blanks from pasted inquiry; human sends quote from CRM.

Week 2: Expand or bail

• If thread search beats SMS, add #callbacks and #dealer-programs.
• If not, you lost a weekend—not a year of Slack migration.

Agents that pair with Buzz in real shops

Block designed Buzz to be agent-agnostic. Practical combinations we see in operator conversations:

• goose — Local open-source agent; strong for file cleanup, spreadsheet normalization, MCP hooks.
• Claude Code — Terminal agent for scripts and integrations; native Buzz member.
• ChatGPT / Claude chat — Still fine for drafting; Buzz is where approved output lives.

See our Buzz IR Scorecard for quality, value, and field sentiment—not paid placement.

What not to do

• Do not port your entire company off Slack in week one.
• Do not let agents text customers without human send—ever.
• Do not treat agent film specs as gospel; same verification gate as ChatGPT.
• Do not skip access control—scope each agent to channels it needs, not #owner-financials.

The strategic read

Dorsey is betting that collaboration infrastructure will be re-built for agents, not retrofitted into 2014 chat apps. Whether Buzz wins or a fork wins, the pattern is locked: signed identity, shared rooms, code + chat + automation in one log.

Tint shops are small enough to adopt in a weekend and complex enough to benefit immediately—multi-bay scheduling, film SKUs, warranty language, and lead noise. Waiting for “version 2.0” means letting sharper competitors internalize agent workflows while you still search iMessage for “what VLT did we quote the Tahoe?”

Start today. One workspace. One agent. One SOP. Measure whether Monday morning feels different.

---

Installer Report is independent of Block and Buzz. Logos and product names are used for identification. Contact editorial with corrections.