Teammate handoff
Hand a project over without the 30-minute context dump. Decisions, the current plan and open threads are all there.
03 / 06ContextCapsules
Package the right context for the right handoff.
ContextCapsules bundle decisions, lessons, docs, working state, open threads and scoped project context into one package for a teammate, a client or an agent.
Ready
Expires in 7 daysstreambox · onboarding handoff
Scope · project · client-safe
- Decision
6 decisions · auth, billing, capsule expiry
- Lesson
4 lessons · migrations, rate limits
- Doc
3 docs · README, runbook, threat model
- Code
12 code refs · auth.ts, billing-webhook.ts…
- Session
Session #438 · 38 min, 14 turns
- Redacted
2 redactions · client identifiers removed
Readable by 2 teammates and 1 agentRevocable
01Three handoff modes
One package shape. Three ways to send it.
Client-safe handoff
The same package as a redacted view. Internal lessons stay hidden and scope boundaries are enforced, not just documented.
Agent bootstrap
A scoped slice an agent can read and cite back. Further chunks are fetched only when the agent needs them.
02What goes inside
Everything the recipient needs. Nothing they don’t.
- DecisionsWhy the project is the way it is.
- LessonsWhat the project has already learned.
- Current planWhat is open, in flight or blocked.
- DocsREADMEs, runbooks and threat models, indexed.
- Code summary or graph referencesSource-backed, never raw exports.
- Open threadThe active conversation, scoped.
- Redaction summaryExactly what was removed, and why.
# streambox · onboarding handoff scope: project · client-safe expires: 7 days · 2026-05-01 recipients: 2 teammates · 1 agent revocable: yes signing: verified handoff (enterprise) contents: 6 decisions 4 lessons 3 docs 12 code refs 1 session (#438) 2 redactions open with: $ contextstream capsule open cap_8f3c…
03Scoped by default
The right context, at the right scope.
Personal
Your own scratch Capsule. It never leaves your workspace.
Project
Context for one codebase, visible to project members and the agents working on it.
Team
Knowledge across projects: runbooks, preferences and escalations.
Client-safe
A redacted view bound to one client engagement. Boundaries enforced.
Agent-visible
An explicit subset for agent recipients, with lessons included as guardrails.
Time-boxed
Every Capsule has an expiry. A sprint, a week or a day: your call.
04How agents use Capsules
Open. Fetch. Cite back.
An agent opens the Capsule it was given, fetches only the parts it needs while it works, and cites the Capsule when it acts.
#agent receives a capsule URL
contextstream capsule open cap_8f3c
opened · scope=project · expires in 7d · 28 nodes available
agent fetches chunks as it reasons
contextstream capsule chunk cap_8f3c --node decision:auth-rls
returned 1 decision · 2 lessons · 1 doc · cited
agent cites the capsule when it acts
per cap_8f3c#decision:auth-rls, using row-level security
05Control the risk
Scoped, expiring and revocable. Always.
Expiring links
Every Capsule has a time limit. The default is short; extend it explicitly.
Revocation
One click. Recipients see a revoked handoff on their next fetch.
Redaction
The author sees a diff between the source slice and the recipient view.
Audit logging
Who opened what, when and from where. Exportable to your SIEM.
Verified handoffs
Cryptographic signing on Enterprise, for handoffs that must be verifiable.
Self-host or VPC
Enterprise can keep Capsule storage and signing keys inside its own boundary.
Cryptographic signing for verified handoffs is available on Enterprise. Pro, Elite and Team Capsules are scoped, expiring and revocable by default.
Create your first Capsule.
A scoped slice of your project, ready for a teammate, a client or an agent, in under five minutes.