Shared context for every agent in Buzz
Connect ContextStream MCP once and give Claude Code, Codex, Goose, and your own agents persistent, grounded project knowledge.
One source of context, available to every authorized human through every authorized agent.
The agent changed. The understanding didn’t.
A requirement changes in one room. A human approves the decision. Another agent continues later from the same grounded project state.
- Buzz · #build
Claude Code starts
Retrieves the requirements and architecture decisions, implements the feature, then surfaces a changed requirement for approval.
ContextStream: 4 project memories used · 3 sources
- Shared project
The approved decision persists
ContextStream records the focused decision, its source, who approved it, and the handoff state—not the whole room transcript.
Saved: Authentication migration decision · human approved
- Buzz · #review
Codex continues
Grounds against the same project, retrieves the changed requirement, and continues correctly without a manual rebrief.
ContextStream: handoff + decision retrieved · sources attached
The room changed. The agent changed. The context didn’t.
Buzz makes identity portable. ContextStream makes understanding portable.
Buzz and ContextStream solve adjacent problems. The integration is valuable because it preserves that boundary instead of pretending workspace history and reusable project context are the same thing.
| Buzz | ContextStream |
|---|---|
| Remembers what happened inside the workspace | Carries knowledge across tools and workspaces |
| Stores conversations and signed events | Organizes reusable project understanding |
| Gives agents a place to collaborate | Gives agents a shared source of grounded context |
| Makes identity portable | Makes understanding portable |
| Records activity | Recalls decisions, constraints, history, and rationale |
Ground first. Preserve deliberately. Hand off cleanly.
01
Brief before work
Before substantial work, the agent retrieves the requirements, decisions, constraints, previous attempts, code, documentation, and current project state that matter.
“I checked the shared ContextStream project before starting. Three previous decisions affect this task.”
02
Preserve after approval
When a conclusion should outlive the room, the agent proposes a focused durable record and waits for a human to approve the write.
“This appears to be a lasting project decision. Save it to ContextStream with this thread as the source?”
03
Handoff between agents
The next authorized agent receives a concise project brief with verified state and next steps, without asking the team to reconstruct the work.
“Claude starts it. Codex continues it. ContextStream carries the understanding.”
Connect the project once. Reuse it across agents.
The reference package includes a safe launcher, Buzz-specific agent instructions, a real MCP smoke test, and a reproducible two-agent demo script.
- Install and authenticate ContextStream MCP.
- Select the shared ContextStream project.
- Choose a Viewer role for read-only or a contributing role for approved writes.
- Launch a Buzz ACP agent with the included ContextStream MCP command.
- Add the agent to a room and ask a project question.
- Connect another agent to the same project and continue without rebriefing.
Works today
A verified Buzz ACP integration seam
Buzz ACP accepts a stdio MCP command and passes it to supported agent runtimes. The reference is pinned to the upstream Buzz revision it was tested against and includes the exact contract checks.
Verified with Buzz ACP tests and a live ContextStream MCP initialize, tool discovery, project init, and grounding request.
Current desktop boundary
The first-class selector is the next upstream step
Buzz Desktop currently derives MCP commands from its runtime catalog rather than accepting a per-agent override. The working launcher uses the supported ACP environment seam; a safe “ContextStream Project Memory” picker needs a small product change.
No arbitrary binary execution is proposed: templates should select an approved MCP command and scoped project credential.
Keep Buzz collaborative. Keep project knowledge portable.
Does ContextStream replace Buzz history?
No. Buzz remains the collaboration workspace and signed event log. ContextStream preserves approved project knowledge that should travel across agents, sessions, tools, and workspaces.
Do all Buzz messages get copied into ContextStream?
No. Agents retrieve relevant project context and preserve focused requirements, decisions, constraints, lessons, plans, and handoffs. Durable writes should begin with human approval, not automatic ingestion of workplace chatter.
Can Claude Code, Codex, and Goose use the same project?
Yes. Buzz's ACP harness can launch these runtimes and attach the same ContextStream MCP server, so each authorized agent can ground against one ContextStream project.
Is there a one-click ContextStream selector in Buzz Desktop?
Not yet. The working reference uses Buzz ACP's supported MCP command environment seam. A first-class Desktop selector requires a small upstream change, and the reference package documents that boundary precisely.
Give every authorized Buzz agent the same project context.
Stop re-explaining the project when the room, model, harness, or workspace changes.