WEBVTT

1
00:00:00.225 --> 00:00:07.537
You're listening to three early deployments of Block's workspace that gave agents identities, channels, code, and signed histories.

2
00:00:07.537 --> 00:00:10.775
Written by Dee-aygo Ferrahro on Promptway.

3
00:00:11.310 --> 00:00:16.160
The most revealing line in Block's Buzz repository is written for employees.

4
00:00:16.485 --> 00:00:17.110
Do not use the

5
00:00:17.110 --> 00:00:18.547
public build, it says.

6
00:00:18.547 --> 00:00:22.547
Download the internal version from squareup/buzz-releases.

7
00:00:22.547 --> 00:00:22.785
That

8
00:00:22.785 --> 00:00:26.685
build already points at Block's relay and agent provider.

9
00:00:26.960 --> 00:00:32.260
Block is using a separate, preconfigured version of its open-source workspace inside the company.

10
00:00:32.260 --> 00:00:33.885
That is a stronger case study than the

11
00:00:33.885 --> 00:00:34.210
launch

12
00:00:34.210 --> 00:00:34.535
claim

13
00:00:34.535 --> 00:00:34.660
that

14
00:00:34.660 --> 00:00:34.960
Buzz

15
00:00:34.960 --> 00:00:35.147
might

16
00:00:35.147 --> 00:00:35.547
replace

17
00:00:35.547 --> 00:00:35.960
Slack

18
00:00:35.960 --> 00:00:36.885
and GitHub.

19
00:00:36.885 --> 00:00:45.485
It tells us the product has crossed the line from demo to working infrastructure for at least one team, while stopping well short of proving an enterprise migration.

20
00:00:45.835 --> 00:00:48.685
Buzz launched publicly on July 21.

21
00:00:48.685 --> 00:00:51.147
It puts people and AI agents in the same

22
00:00:51.147 --> 00:00:51.710
channels,

23
00:00:51.710 --> 00:00:51.997
gives

24
00:00:51.997 --> 00:00:52.322
each

25
00:00:52.322 --> 00:00:52.697
agent

26
00:00:52.697 --> 00:00:52.760
a

27
00:00:52.760 --> 00:00:53.472
cryptographic

28
00:00:53.472 --> 00:00:54.160
identity,

29
00:00:54.160 --> 00:00:54.285
and

30
00:00:54.285 --> 00:00:54.710
records

31
00:00:54.710 --> 00:00:55.397
messages,

32
00:00:55.397 --> 00:00:55.747
code

33
00:00:55.747 --> 00:00:56.310
patches,

34
00:00:56.310 --> 00:00:56.910
approvals,

35
00:00:56.910 --> 00:00:57.035
and

36
00:00:57.035 --> 00:00:57.560
workflow

37
00:00:57.560 --> 00:00:57.960
events

38
00:00:57.960 --> 00:00:58.110
in

39
00:00:58.110 --> 00:00:58.372
one

40
00:00:58.372 --> 00:00:58.685
signed

41
00:00:58.685 --> 00:00:59.935
log.

42
00:01:00.210 --> 00:01:00.310
The

43
00:01:00.310 --> 00:01:00.635
Slack

44
00:01:00.635 --> 00:01:01.260
comparison

45
00:01:01.260 --> 00:01:01.847
explains

46
00:01:01.847 --> 00:01:01.935
the

47
00:01:01.935 --> 00:01:02.710
interface.

48
00:01:02.710 --> 00:01:02.872
The

49
00:01:02.872 --> 00:01:03.210
audit

50
00:01:03.210 --> 00:01:03.560
log

51
00:01:03.560 --> 00:01:04.097
explains

52
00:01:04.097 --> 00:01:04.185
the

53
00:01:04.185 --> 00:01:05.360
product.

54
00:01:05.635 --> 00:01:05.747
What

55
00:01:05.747 --> 00:01:06.035
Block

56
00:01:06.035 --> 00:01:07.185
built

57
00:01:07.185 --> 00:01:07.560
Buzz

58
00:01:07.560 --> 00:01:07.685
is

59
00:01:07.685 --> 00:01:07.810
a

60
00:01:07.810 --> 00:01:11.372
self-hostable workspace built on the Nostr protocol.

61
00:01:11.372 --> 00:01:13.822
A workspace maps to a relay U R L.

62
00:01:13.822 --> 00:01:22.035
Every message, reaction, workflow step, review approval, and Git event becomes a signed Nostr event stored by that relay.

63
00:01:22.385 --> 00:01:25.522
Humans and agents use the same identity shape.

64
00:01:25.522 --> 00:01:29.772
Each participant has a public key, and every event carries a signature.

65
00:01:29.772 --> 00:01:38.335
Agents can join channels, open repositories, send patches, review code, run workflows, edit canvases, and call other agents.

66
00:01:38.610 --> 00:01:40.610
The relay remains the source of truth.

67
00:01:40.610 --> 00:01:44.510
Postgres stores events, channels, workflows, tokens, and the audit chain.

68
00:01:44.510 --> 00:01:46.285
Redis handles presence and fan-out.

69
00:01:46.285 --> 00:01:48.935
The desktop application uses Tauri and React.

70
00:01:48.935 --> 00:01:52.235
buzz-cli gives agents a jay-son-in, jay-son-out interface.

71
00:01:52.235 --> 00:01:59.060
Agent Client Protocol (ACP) adapters connect Claude Code, Codex, Goose, and other compatible harnesses.

72
00:01:59.335 --> 00:02:36.485
Here is the practical difference: Existing team stack Buzz A Slack bot posts under an integration account An agent joins as a named member with its own key The agent works in a private terminal session Its channel, tool calls, patches, and replies can share one record GitHub holds the patch while Slack holds the decision Git events and conversation use the same event log Bot permissions live across oh auth apps and service tokens Relay membership, and agent identity sit in one system Search reconstructs a decision from several products Search can query the conversation, patch, workflow, and approval Buzz does not make the underlying model safer.

73
00:02:36.485 --> 00:02:40.035
It makes authorship and history easier to inspect.

74
00:02:40.310 --> 00:02:47.910
Case one: Block has an internal relay The public README gives Block employees their own installation path.

75
00:02:47.910 --> 00:02:52.272
The internal build comes wired to the company relay and agent provider.

76
00:02:52.272 --> 00:02:58.710
Jack Dorsey's launch post said the project was built to reduce Block's dependence on Slack and GitHub.

77
00:02:59.010 --> 00:03:01.822
Those two facts support a careful conclusion.

78
00:03:01.822 --> 00:03:08.135
Block has deployed Buzz internally and wants it to absorb work now split across incumbent tools.

79
00:03:08.460 --> 00:03:15.797
They do not tell us how many employees use it, how much traffic it carries, or whether any team has removed Slack or GitHub.

80
00:03:15.797 --> 00:03:21.360
Block has published no migration percentage, retention number, or incident record.

81
00:03:21.660 --> 00:03:23.772
The internal build still matters.

82
00:03:23.772 --> 00:03:32.285
Block is testing the identity model against its own agent work instead of asking open-source users to discover every rough edge first.

83
00:03:32.560 --> 00:03:36.247
The release notes focus on problems active teams encounter.

84
00:03:36.247 --> 00:03:51.735
Version 0.5.0 shipped on July 28 with use-limited invite links, a generic ACP runtime seam for bringing another harness, agent display names as Git authors, a lower default parallel-agent limit, and a security update for a Nostr denial-of-service advisory.

85
00:03:52.085 --> 00:03:59.160
Identity, invitations, Git attribution, runtime compatibility, and resource limits are not landing-page features.

86
00:03:59.160 --> 00:04:02.335
They are the problems a working room produces.

87
00:04:02.610 --> 00:04:12.710
Case two: Jupiter Broadcasting opened a community Jupiter Broadcasting linked a live Buzz community from its July 26 episode of LINUX Unplugged.

88
00:04:12.710 --> 00:04:20.810
The episode page also points to external-agent integration work for Hermes, a multi-agent system the network has been testing.

89
00:04:21.110 --> 00:04:24.847
This is an early outside deployment, not a customer success story.

90
00:04:24.847 --> 00:04:31.710
Jupiter already runs a technical community across several open tools, which makes it unusually tolerant of beta infrastructure.

91
00:04:31.710 --> 00:04:40.160
Its use still tests something Block cannot prove alone: whether a community that values self-hosting will move conversation and agents into the same room.

92
00:04:40.485 --> 00:04:42.197
The linked work is specific.

93
00:04:42.197 --> 00:04:48.372
A feature request asks Buzz to support external agent systems that do not speak ACP.

94
00:04:48.372 --> 00:04:54.085
Related pull requests add Hermes runtime discovery and document the host integration.

95
00:04:54.410 --> 00:04:58.022
That is open-source adoption in its least polished form.

96
00:04:58.022 --> 00:05:06.035
A real community wants to bring an existing agent stack, finds the protocol seam too narrow, and contributes the missing adapter.

97
00:05:06.310 --> 00:05:15.085
Case three: A real permissions gap appeared in two days On July 23, an operator filed a request for channel-scoped guest access.

98
00:05:15.085 --> 00:05:19.535
They run a membership-gated Buzz community with internal channels and agents.

99
00:05:19.535 --> 00:05:25.285
They want customers to enter one public support channel without gaining access to anything else.

100
00:05:25.560 --> 00:05:29.285
As of July 29, Buzz cannot express that policy.

101
00:05:29.585 --> 00:05:35.222
The relay can require membership for everyone or accept authenticated identities more broadly.

102
00:05:35.222 --> 00:05:38.385
Channel visibility applies after relay admission.

103
00:05:38.385 --> 00:05:47.735
The operator wants a guest to read and write in #support while blocking every other channel, repository, workflow, direct message, and administration surface.

104
00:05:48.060 --> 00:05:57.110
This issue is the best early case study in the repository because it shows the product working and the authorization model failing at the same time.

105
00:05:57.410 --> 00:06:00.310
Cryptographic identity answers who signed an event.

106
00:06:00.310 --> 00:06:04.960
It does not automatically answer which event that identity should be allowed to publish.

107
00:06:04.960 --> 00:06:16.110
The operator wrote out the missing contract in detail: one allowlisted channel, text-only at first, normal moderation and rate limits, agents allowed to answer, and no broader relay membership.

108
00:06:16.410 --> 00:06:21.435
That request is more useful than another screenshot of an agent posting in chat.

109
00:06:21.435 --> 00:06:24.885
It names the boundary a production community needs.

110
00:06:25.135 --> 00:06:30.122
The product claim that holds up Block says agents should be members instead of bots.

111
00:06:30.122 --> 00:06:32.785
That claim holds up in the architecture.

112
00:06:33.060 --> 00:06:36.285
Buzz's agent runtime uses two small Rust binaries.

113
00:06:36.285 --> 00:06:40.222
buzz-agent speaks ACP, calls a model, and manages sessions.

114
00:06:40.222 --> 00:06:45.860
buzz-dev-mcp gives the agent a shell and file editor through the Model Context Protocol (M C P).

115
00:06:45.860 --> 00:06:53.385
The pieces communicate through published protocols, so teams can swap the model provider or agent harness without rebuilding the workspace.

116
00:06:53.735 --> 00:07:00.635
Each community keeps its own profiles, presence, direct messages, memories, jobs, memberships, and audit trail.

117
00:07:00.635 --> 00:07:07.485
The same public key can join another community, but the agent's state does not silently follow it across hosts.

118
00:07:07.760 --> 00:07:13.835
Portable identity does not become portable access by accident, which is the safer boundary.

119
00:07:14.085 --> 00:07:26.335
The Slack-killer claim is early Buzz has desktop applications, chat, channels, threads, direct messages, canvases, media, search, Git events, workflows, and an agent-first command-line interface.

120
00:07:26.335 --> 00:07:29.485
It also says plainly that it is unfinished.

121
00:07:29.760 --> 00:07:35.835
As of July 29, the public roadmap still lists workflow approval gates and parts of the mobile experience as active work.

122
00:07:35.835 --> 00:07:40.697
Hosted relays are free during beta, with no published enterprise price or final usage limits.

123
00:07:40.697 --> 00:07:50.335
Slack Connect, mature retention controls, enterprise discovery, identity-provider integration, and years of administration tooling do not disappear because Nostr events have signatures.

124
00:07:50.660 --> 00:07:53.147
The self-hosting story carries work too.

125
00:07:53.147 --> 00:08:01.097
A production relay brings Postgres, Redis, object storage, backups, updates, key recovery, monitoring, and incident response.

126
00:08:01.097 --> 00:08:05.060
Teams gain control because they accept the operating burden.

127
00:08:05.360 --> 00:08:08.310
Buzz may reduce seven tabs to one substrate.

128
00:08:08.310 --> 00:08:13.285
It also puts seven products' worth of responsibility onto that substrate.

129
00:08:13.560 --> 00:08:26.060
Who should pilot it A small engineering team or open-source community should run a pilot when agents already perform real work and the private agent conversation keeps vanishing from the team record.

130
00:08:26.360 --> 00:08:29.385
Use one repository, two agents, and one workflow.

131
00:08:29.385 --> 00:08:31.660
Give the research agent read-only access.

132
00:08:31.660 --> 00:08:34.060
Give the coding agent a disposable branch.

133
00:08:34.060 --> 00:08:37.897
Require a human reaction before a workflow can publish or merge.

134
00:08:37.897 --> 00:08:45.660
Measure how often teammates can reconstruct a decision from Buzz alone and how often they return to Slack or GitHub for missing context.

135
00:08:45.935 --> 00:08:48.172
Keep the incumbent tools during the pilot.

136
00:08:48.172 --> 00:08:50.560
Buzz has not earned a cutover.

137
00:08:50.910 --> 00:08:58.310
Teams with regulated data, complex guest access, large Slack Connect networks, or mature GitHub governance should wait.

138
00:08:58.310 --> 00:09:01.022
The channel-scoped support issue shows why.

139
00:09:01.022 --> 00:09:06.060
Signed events are valuable, but authorization still needs the boring policy work.

140
00:09:06.335 --> 00:09:15.585
Verdict Buzz has the most coherent method I have seen for tying agent work to an identity, an authority, a room, and a body of evidence.

141
00:09:15.910 --> 00:09:20.197
Block's internal build proves the company is willing to use its answer.

142
00:09:20.197 --> 00:09:24.160
Jupiter Broadcasting proves an outside community can extend it.

143
00:09:24.160 --> 00:09:29.185
The support-channel request proves the permissions model still has sharp edges.

144
00:09:29.510 --> 00:09:32.010
Pilot Buzz as an agent workspace.

145
00:09:32.010 --> 00:09:39.685
Do not call it a Slack and GitHub replacement until a team publishes the migration numbers and the authorization gaps close.

146
00:09:40.245 --> 00:09:41.095
That's the story.

147
00:09:41.095 --> 00:09:44.007
You'll find every source linked at the end of the article.

148
00:09:44.007 --> 00:09:46.670
Thanks for listening, on Promptway.