Working now
Channels, threads, DMs, canvases, media, search, audit logs, workflows, and a desktop app are described as available.
Reading note · Agent systems
Why we’re buzzing
Buzz is an open-source workspace built around a simple pressure I keep running into: agents cannot help with context they cannot see, and every seam between tools sheds part of the story.
Read jack’s original article on X ↗The context problem
Teams currently split conversation, code, CI, review, and agent activity across separate systems. Buzz proposes one signed record instead of asking people and agents to reconstruct the work after the fact.
Chat and decisions
Code and patches
CI and workflows
Reviews and approvals
Buzz relay
One attributable context
People and agents operate through the same cryptographic identity model.
- signed events
- one search and audit trail
- branch and conversation together
The design choices that matter
-
Self-sovereign
Each workspace runs through a relay the team hosts, with its own domain, data, and keys.
-
Open
Buzz is Apache 2.0, built on Nostr, model agnostic, and already names harnesses for Goose, Codex, and Claude Code.
-
One context
A feature branch becomes a channel where patches, CI, review, and the merge decision remain beside the conversation that produced them.
-
Equal identity
Agents receive keys, channels, and an attributable audit trail instead of appearing as an invisible process behind a person.
What sticks with me
I have been thinking about agent workflows mostly through prompts, skills, plugins, orchestration, and the surfaces used to watch the work. Buzz moves the question one level outward. The quality of the agent is limited by the shape of the workspace around it.
The interesting idea is not simply giving an agent more access. It is keeping the work, the conversation, and responsibility for each action in one coherent record.
The question I want to carry forward is how much of this requires a complete workspace and how much can be recovered by making the seams between existing tools more explicit. Either way, the article gives the context layer a much larger role than I have usually given it.
Still early
Still being built
Full Git hosting, mobile, push, tighter agent scoping, approval gates, hosted operation, and relay federation remain in progress.