Skip to content

Switch agents without explaining the project again.

ContextStream keeps your project’s decisions, preferences, and lessons, plus indexed code and search, outside any one session. The next agent starts where the last one stopped.

$▍
Installs the MCP server. Free to start.
Try in browser →
Image
Real sessions · same prompt
Claude Code without and with ContextStream: two real sessions on a demo project, sped up. Every number on screen is measured from the two runs.
The ContextStream workspace: what needs you, your next moves, and a stream of decisions, lessons, runbooks and coordination notes recorded by teammates and their agents.
The ContextStream workspace, with a demo team's project: reviews and handoffs waiting, next moves, and what teammates' agents recorded since your last visit.
Works withClaude CodeCodexCursorVS CodeWindsurfClineOpenCodeClaude DesktopContextCodeany MCP client
The platform

What your agents can't keep on their own.

An agent forgets when its session ends, and it only knows the tool it runs in. ContextStream holds what the project has learned outside any one session, tool or person, and hands the right part of it to whichever agent is working now.

Durable context

Decisions with their reasons, and lessons that warn before a mistake repeats.

A decision is kept with why it was made. When it changes, the new one supersedes it and the history stays readable. A lesson surfaces when later work matches it. Plans, runbooks, documents and diagrams sit beside them, in the same workspace every agent reads.

  • Recorded once, from any connected agent
  • Retrieved by the next one, in any tool
  • Readable, editable and deletable by you
payments-api · decisions and lessonsdemo project
Decision · Apr 2Current
Move the job queue to Postgres

Jobs commit in the same transaction as the data they touch. Replaces the Mar 4 decision.

Lesson · Mar 19Warns matching work
The Redis queue dropped jobs during a failover

Retries hid it for a week. Test failover before trusting queue durability.

Decision · Mar 4Superseded · kept as history
Use Redis for the job queue

Already in the stack, and the team knows it.

A fresh agent, in another tool, asks“Which job queue do we use?”It gets backPostgres, since Apr 2. The Redis decision is superseded, and a lesson explains why.
Code intelligence

Search by meaning or exact text, and see what a change touches.

Your repositories are indexed for search by meaning, exact text, symbol, path and pattern. The code graph answers callers, dependencies, cycles, unused code and the blast radius of a change. Every hit says whether the file changed since it was indexed.

search · where do we retry webhook sends?meaning + exact text
src/webhooks/sender.ts · lines 42–88Found by meaning: nothing in the file says “retry webhook”. Current, indexed minutes ago.
src/legacy/client.ts · line 30Exact match on invalid_grant. Changed after the last index: read the file before relying on it.
impact · sendWithRetry()
  • src/webhooks/dispatch.ts · queueDelivery()
  • src/billing/refunds.ts · notifyRefund()
  • src/jobs/replay.ts · replayFailed()
Live coordination

Two agents on the same code find out before they collide.

Run one agent in one terminal and another somewhere else. When two of your live sessions start working on the same thing, each hears about the other on its next turn, and a direct conflict arrives as a blocking notice. A session that has already ended can still leave word for one that is running.

Session 2 · next turntwo live sessions
Session 1 · payments-apiworking

Changing the backoff in sendWithRetry() to capped exponential with jitter.

Session 2 · web-appabout to edit

Planned: add an immediate retry for 503s in the same sender.

[COORDINATION] blocking · from payments-api

Another live session is changing sendWithRetry() to capped backoff with jitter, per the active decision. An immediate retry conflicts with it. Read the decision before editing; acknowledge when done.

Handoffs and capsules

Work changes hands without a briefing call.

A handoff records the scope, what was verified, the open questions and the next steps, so the next person or agent starts exactly there. A capsule packages selected context behind a link for someone outside the workspace: scoped, expiring and revocable.

Handoff · webhook retriespending
From Priya → Danielscope · payments-api
Capped backoff is in. Check the traffic bound at peak, then ship.

Verified: 429 fixture added, sender tests pass. Open question: does replay need its own budget?

  1. Run the peak-traffic replay against staging.
  2. Confirm the bound holds, then merge.
  3. Update the provider outage runbook.
contextstream.io/c/••••••••Capsule for the provider's engineer: this handoff, the decision and the sender code only. It expires, it can be redacted, and you can revoke it any time.
ContextCode · Beta

A coding agent built on the same context.

ContextCode plans, builds and reviews with the project's search, decisions and lessons from its first turn, and can split a goal across coordinated agents. Use it in your terminal, in VS Code, or in a session in the browser. It is included in every plan.

More about ContextCode

ContextCode's agent command center: planner, coder and reviewer runs, each completed, in a live grid.
A real ContextCode session: three coordinated agents, live.
For teams

What one teammate's agent learns, everyone's agent knows.

A decision your colleague recorded on Tuesday answers your agent's question on Thursday, in whichever tool you use. Team adds shared workspaces, team-wide views, admin roles and pooled credits, and Coflow access comes with it.

Start your teamSee what teams get
  • Shared workspaces. Decisions, lessons, runbooks, plans and handoffs every member's agents retrieve.
  • Team views. Tasks, documents, plans and activity across the team, without copies.
  • Admin and access. Invites with roles, per-member workspace and project access, seats and pooled credits.
  • Coflow. People and agents in the same channels, with ContextStream as the shared context underneath.
Control

You decide what is kept, and who sees it.

Search is hosted, so eligible files are sent for indexing. Here is what holds around that.

Security · Privacy policy

  • Ignore rules and secret filters run before anything is indexed.
  • Every decision, lesson and document can be read, edited, superseded or deleted.
  • On team plans, your session transcripts stay personal unless you share them.
  • Your project data is never sold and never used to train AI models.
  • Each workspace has a home region in the United States, East or West.
Measured

Measured, and published with the method.

98.77%Code recallBest-answer Recall@10
96.8%Context recall accuracyLongMemEval-S, 500 questions
61msSearch timeServer p50 across 4 runs

How each number was measured is published on the Benchmarks page.

Start

Start with one agent and one repository.

10,000 credits every month. Full platform access. No credit card.

  1. Connect your agentOne command signs you in, picks a workspace and connects the editors you already use.
  2. Index a repositoryIndexing runs in the background. Search and the code graph fill in as it goes.
  3. Work as usualDecisions, lessons and handoffs build up as your agents work, and stay correctable.
  4. Bring in the teamInvite teammates to the same workspace, so their agents start from what yours learned.
curl -fsSL https://contextstream.io/scripts/mcp.sh | bash
Start freeStart your teamTry it in the browser, no account