03 / 06ContextCapsules · scoped handoffs

Package the right context for the right handoff.

ContextCapsules bundle decisions, lessons, docs, working state, open threads, and scoped project context into a shareable package for a teammate, client, or agent.

Open demo Capsule →
★ Capsule ready

streambox · onboarding handoff

scope · project · client-safe
◷ expires 7 days
◇ 6 decisions · auth, billing, capsule expiry
◆ 4 lessons · migrations, rate-limits
⎙ 3 docs · README, runbook, threat-model
⌘ 12 code refs · auth.ts, billing-webhook.ts, …
○ session #438 · 38 min · 14 turns
◬ 2 redactions · client identifiers removed
↳ readable by 2 teammates · 1 agent⊘ revocable
01 Three handoff modes

One package shape. Three ways to send it.

◐

Teammate handoff

Hand a project off without the 30-minute context dump. Decisions, current plan, open threads — all there.

⊘

Client-safe handoff

Same package, redacted view. Internal lessons hidden, scope boundaries enforced — not just documented.

◈

Agent bootstrap

A scoped slice an agent can read and cite back. Lazy chunks fetched on demand.

02 What goes inside

Everything the recipient needs. Nothing they don't.

◇
Decisions
Why the project is the way it is.
◆
Lessons
What the project has already learned.
◐
Current plan
What's open, in flight, blocked.
⎙
Docs
READMEs, runbooks, threat models — indexed.
⌘
Code summary or graph references
Source-backed, never raw exports.
○
Open thread
The active conversation, scoped.
◬
Redaction summary
Exactly what was removed and why.
capsule.streambox / handoff-jordan
# 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…
03 Scoped by default

The right context, at the right scope.

◐

Personal

Your own scratch capsule. Never leaves your workspace.

◇

Project

Per-codebase context. Visible to project members and agents on it.

◈

Team

Cross-project workspace wisdom — runbooks, preferences, escalations.

⊘

Client-safe

Redacted view bound to a client engagement. Boundaries enforced.

◬

Agent-visible

Explicit subset for agent recipients. Lessons-as-guardrails included.

◷

Time-boxed

Every Capsule has an expiry. Sprint, week, day — your call.

04 How agents use Capsules

Open. Fetch. Cite back.

# agent receives a capsule URL
$ contextstream capsule open cap_8f3c
✓ opened · scope=project · expires in 7d · 28 nodes available
# agent fetches lazy 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 back when it acts
$ › per cap_8f3c#decision:auth-rls — using row-level security
05 Control the risk

Scoped, expiring, revocable. Always.

◷

Expiring links

Every Capsule has a TTL. The default is short. Extend explicitly.

⊘

Revocation

One click. Recipients see a revoked-handoff state on their next fetch.

◬

Redaction

Author-visible diff between the source slice and the recipient view.

⊡

Audit logging

Who opened what, when, from where. Exportable to your SIEM.

★

Verified handoffs

Cryptographic signing available on Enterprise for handoffs that must be verifiable.

◫

Self-host or VPC

Enterprise can keep Capsule storage and signing keys inside their boundary.

Cryptographic signing is available for verified handoffs on Enterprise. Solo and Team capsules are scoped, expiring, and revocable by default.

Create your first Capsule.

A scoped slice of your project, ready for a teammate, client, or agent. In under five minutes.

Read the docs