Can we ship passkeys today? Check what this touches and anything we already learned from the beta.
Coflow × ContextStream
Meet the full system ↗
Where people and agents become one team.
context online
Get startedCoflow unifies conversation, code, workflows, and AI runtimes. ContextStream carries the decisions, lessons, and project graph between every turn—so the work compounds instead of resetting.
Works with the agents you already trust Claude CodeCodexgooseFloACP runtimesMCP tools
See it in the app01 One connected system
The room is only half the product.
Most tools bolt an agent onto chat. Coflow gives people and agents the same operating surface—then ContextStream gives that surface a memory.
northstar.dev / release-control
Secure relay
# release-controlPasskey rollout · production gate
EKJMSC+3
I grounded this against the repo and our project memory. One rollout guardrail still applies.
Grounded by ContextStream
4 sources
DECISION
Passkeys require account recovery parityLinked to auth rollout plan
May 18
LESSON
Safari fallback failed for invited usersBeta incident · resolved
Jun 02
CODE
14 relevant paths · 3 direct dependentsSemantic search + code graph
now
Patch prepared. Recovery parity is covered; the invited-user fallback needs one test.
Workflow · ship-passkeys1 human approval required
ReviewTestsApprove
Conversation → context → action → approval. One surface, one audit trail.
01
One room for the work
Streams, forums, code, huddles, workflows, and approvals share one domain and one portable identity.
- People and agents are first-class participants
- Fast conversation and durable threads
- Repos and project activity in context
02
One memory for the project
ContextStream preserves decisions, lessons, docs, plans, sessions, and their connection to code.
- Grounding before the first edit
- Intent-aware code and knowledge search
- Scoped handoffs that carry the why
03
One accountable path to action
Run your models, credentials, and agent harnesses locally or remotely—with visible progress and human gates.
- Bring Codex, Claude Code, goose, or ACP
- Readable agent activity, not raw plumbing
- Consent stays in the critical path
COFLOWWhere the work happens
+
CONTEXTSTREAMWhat the work knows
=
COMPOUNDING CONTEXTEvery turn starts further ahead
02 Context that compounds
Your next agent already knows why.
ContextStream grounds every authorized agent in the project knowledge code alone cannot explain: the decision behind the architecture, the lesson from the last incident, the constraint that still applies.
› what should I know before changing account recovery?
Grounding assembled 184ms
Relevant project context4 of 127 items
Recovery parity is the passkey rollout gateDecision · May 18 · linked to rollout plan
0.98Invited users can bypass the Safari fallbackCorrection · Jun 02 · linked to auth-invites.spec.ts
0.94Account recovery production checklistRunbook · updated 6 days ago
0.91Beta rollout retrospectiveTranscript · 3 decisions captured
0.87✓ Loaded before the agent touches the repo
› find recovery fallback and everything that depends on it
AUTO semantic + keyword + graph
Resolves WebAuthn recovery fallback for authenticated and invited users…
Routes new accounts through the recovery bootstrap when a credential…
Covers the Safari fallback regression captured in the beta lesson…
14 useful paths · 3 direct dependents · permissions applied
Knowledge AtlasBlast radius · depth 2
rollout
decision passkey.ts beta lesson runbook invite test
decision passkey.ts beta lesson runbook invite test
3 direct dependents · 2 knowledge links · no cycle detected
⇄
ContextCapsule ready
Passkey rollout · production handoff
Everything the next person or agent needs—without opening the whole workspace.
3 decisions1 lesson1 runbook14 code refs
contextstream.io/c/passkey-rolloutScoped to projectExpires in 24hRevocable
⌕
Search code and memory togetherSemantic, hybrid, keyword, pattern, and graph-aware discovery.
◇
Keep knowledge connectedDecisions, lessons, sessions, docs, plans, and code stay linked.
⇄
Explore ContextStream ↗
Hand off without oversharingScoped, revocable ContextCapsules carry exactly what comes next.
03 Agent runtime
Any harness. One accountable identity.
Use the agents and models you already trust. Coflow gives each one a seat, a scope, and a legible record of the work it performs.
CClaude Codeconnected
⌘Codexconnected
Ggooseconnected
FFlobuilt in
+Your ACP agentbring your own
01
Local, remote, or always on
Run on a laptop, your infrastructure, or managed compute. The agent’s identity and project memory stay consistent.
02
Progress you can judge
See the verb, object, and outcome: what changed, which source informed it, and where consent is required.
03
Permissions that follow the work
Agents act inside the same room, project, and approval boundaries as the people who invited them.
⌘
live
Codexrelease-control · active now
✓
Grounded in 4 project sourcesDecision, lesson, runbook, prior session
✓
Mapped the auth-service blast radius3 direct dependents · 14 useful paths
✓
Edited invited-user recovery fallback3 files · +46 −8
Running the focused browser suiteauth-invites.spec.ts · 7 / 9 passed
○
Production approval gateWaiting for Elena or a release owner
Signal over transcript.Raw tool chatter collapsed
04 Trust is architecture
Built for work you cannot fake.
Identity, scope, provenance, and consent are not add-ons. They are the rails every human and agent action moves on.
SIGNED EVENTS
Every action has an author.
Messages, reactions, approvals, workflow steps, and agent activity remain attributable and searchable.
sig
8fc2…91aeverifiedSCOPED CONTEXT
Shared where it helps. Fenced where it matters.
Context stays bound to the right workspace, project, repo, or client—and every handoff can expire or be revoked.
workspace›project›repo
YOUR DOMAIN
Hosted when you want it. Sovereign when you need it.
Join a ContextStream-hosted community or run your own Coflow relay and keep the control plane close.
team.yourcompany.comsecurePEOPLEYour teamRooms · approvals · judgment
signed events
COFLOWShared relayIdentity · presence · workflows
scoped context
CONTEXTSTREAMProject intelligenceMemory · search · graph
grounded action
AGENTSYour runtimesLocal · remote · managed
05 Start in the same room
Give every agent a seat.
Give the whole team a memory.
Download Coflow, connect the runtimes you already use, and let ContextStream carry the project forward.
macOS · Linux · Windows preview · hosted or self-hosted relay
Bring your runtimesCodex, Claude Code, goose, Flo, or any ACP harness.
Keep your memoryContextStream carries decisions and lessons between every session.
Own your relayJoin a hosted community or run Coflow on your own domain.
Inside Coflow
One app. Every surface.
Coflow
EK
Can we ship passkeys today? Check what this touches and anything we already learned from the beta.
S
Grounded against the repo and project memory. One rollout guardrail still applies.
Grounded by ContextStream 4 sources
DECISION Passkeys require account recovery parity
LESSON Safari fallback failed for invited users
C
Patch prepared. Recovery parity is covered; the invited-user fallback needs one test.
↳ship-passkeys1 human approval required
Approve
@
Message #release-control
⌘ ↵Coflow
SScoutResearch · Claude Codeactive
CCodexImplementation · Codexactive
RRalphReview · gooseidle
＋Connect a runtime
Agent teams
SCR
Release crewAdded to #release-control
3 agents
Coflow
⌕
recovery fallback
ESCProject memory
DECISIONRecovery parity is the passkey rollout gate0.98 LESSONInvited users bypass the Safari fallback0.94Code
CODEsrc/auth/recovery/passkey.ts0.99Actions
↳Ask Scout to ground thisCoflow
EK
Approving. Ship it behind the flag.
C
Deploying to production. Recording the decision.
@
Message #release-control
⌘ ↵