ContextStream
Project
streampilot-demo-app
Session
July 13, 2026
Agent
Claude Code (via ContextStream MCP)

MCP — the open connector the agent uses to read this project’s saved memory.

Memory receipt · generated automatically

Here’s what your agent remembered — so you didn’t have to re-explain it.

9 items remembered ≈60× less context sent 3 records carried forward

01 What your agent remembered

Pulled into the session before the agent wrote a single line.

Decisions it followed ×3

  1. 1

    Use cursor-based pagination for /events (offset paging caused timeouts).

  2. 2

    All timestamps stored UTC, converted at the edge.

  3. 3

    Feature flags live in config/flags.yaml, never hardcoded.

Lessons it applied ×2 — mistakes made once, not repeated

  • Lesson

    Retry with exponential backoff, max 3 attempts — added after the Jun 18 rate-limit incident.

  • Lesson

    Flag changes in config/flags.yaml need a config reload, not a redeploy — written down after a Jul 2 hotfix shipped twice.

Files it was pointed at ×4 — exact files and lines

  • src/api/events.rs L112–168
  • src/db/pagination.rs L14–60
  • config/flags.yaml L1–22
  • docs/adr/007-pagination.md full doc

Pulled for this task3 decisions · 2 lessons · 4 files

02 What that saved you

Context is measured in tokens — the small pieces of text an agent reads.

Sent to your agent

2,400 tokens

Scoped context — only what this task needed.

≈60× less context sent

Whole-project dump estimate

≈148,000 tokens

Estimated if the entire project were sent instead.

The scoped bar is drawn at a minimum visible size — at true scale it would be about 1.6% of the full track.

Re-explaining avoided

~15 minutes

of walking the agent through decisions it already knew.

03 What got remembered for next time

Saved back to project memory when this session ended.

  • 1 new decision saved

    Jul 13, 2026 /events pages cap at 200 items; the next-page cursor travels in the Link header.

  • 1 new lesson saved

    Treat pagination cursors as opaque strings — a hand-built cursor broke paging during today’s testing.

  • Full session transcript indexed and searchable

    Ask later in plain language — “why did we cap /events pages?” — and this session comes back.

Next session starts here, not from zero.