ContextStream
streampilot-demo-app sandboxdemo sandbox

Session-start memory proof

Welcome Back recap

Less lost context. The same Friday-morning session, started twice. On the left, the agent starts cold and has to be re-briefed. On the right, ContextStream hands it your project memory before the first message — useful work starts in seconds.

01 · The proof

One session, two starts

Both panels open the same project at 09:12 with the same request. The small timers count minutes from the first keystroke.

Demo state

Without ContextStream

Fri Jul 10 · 09:12
You0:00
Back on the StreamPilot demo app. Quick refresher, since you won’t remember any of it: Next.js storefront, Node API, and we were somewhere in the middle of the checkout flow.
You2:19
Hang on — pasting everything from my notes.
project-notes-paste.txt ~1,400 tokens · pasted by hand auth approach… db choice… migration order… checkout plan…
Agent3:41
Thanks — a few basics before I can start. Which database did you settle on, are auth tokens handled on the client or the server, and where exactly were we in the checkout flow?

4:06 · still re-aligning — no work started yet

0 facts recalled · ~1,400 tokens re-pasted useful action · still waiting at 4:06

With ContextStream

Fri Jul 10 · 09:12
Injected at session start 0:00

Welcome back

streampilot-demo-app

Last session · July 8, 2026 (2 days ago)

Decision

Keep auth tokens server-side only.

Tokens never reach the browser — the Node API owns the session.

Decision

Use Postgres over SQLite for demo data.

Keeps local behavior matched to the deploy target.

Lesson

Run migrations before seed data — this broke twice.

Seeding an unmigrated schema fails.

Open plan step
Checkout flow — step 3 of 5 open: wire the payment webhook.

1–2 done (cart, order draft) · 3 open · 4–5 remain (receipt email, end-to-end pass)

Pick up where you left off?
Agent0:05
Resuming streampilot-demo-app. I have both decisions, the migration lesson, and step 3 of the checkout plan — ready to wire the payment webhook?

0:12 · aligned — webhook work starts

6 facts recalled · ≈ 148 tokens injected useful action · 0:12

02 · Under the hood

What powers the recap

The exact plain text your agent receives on the first grounding call — and the matching card on the contextstream.io dashboard. Same facts, both views.

same facts, two views
plain text · first grounding callcap · 150 tokens
contextstream · session-start recall
project       streampilot-demo-app
last session  July 8, 2026 (2 days ago)

decision  Keep auth tokens server-side only. Tokens never reach the browser — the Node API owns the session.
decision  Use Postgres over SQLite for demo data. Keeps local behavior matched to the deploy target.
lesson    Run migrations before seed data — this broke twice. Seeding an unmigrated schema fails.
plan      Checkout flow, step 3 of 5 open: wire the payment webhook.
status    Steps 1–2 done (cart, order draft) · step 3 open · steps 4–5 remain (receipt email, end-to-end pass).
next      Add POST /api/webhooks/payments and verify the provider signature before writing orders.

Pick up where you left off?
≈ 148 / 150 tokens Returned on the first grounding call — authored to fit the 150-token cap, not truncated to it.