Context engineering, AI workflows, governance, and lessons we capture while building ContextStream.
Some of the most valuable project knowledge isn't a decision yet but rather a pattern someone noticed, a hunch about how the work keeps wanting to grow, an observation that's too soft to be a rule but too useful to lo…
Most AI friction isn't about what the agent builds, it's about how. Tone, level of detail, planning style: the small corrections you give every session and lose every session. Preferences are how that guidance starts…
AI coding agents reach for "remembers everything" by default, but total recall is exactly what makes them noisy and unreliable. ContextStream was built on the opposite premise: remember the right things and surface th…
Last month I watched Opus 4.6 plan a brand new parts database. I already had a parts database. The agent didn't know. That's the tax you pay when your AI has spiky knowledge and no framework filling in the gaps.
Every developer working with AI in 2026 lives inside the same rhythm. You expand. You contract. Then you expand again. This isn't a flaw in the workflow. This is the workflow. The problem isn't the loop. The problem i…
Developer One lives in Claude Code. Developer Two lives in Codex. Last week, Developer One's agent refactored the caching layer and made a deliberate call: skip caching for any request flagged as a preview. There was…
Most code work slows down before the first edit. The problem is usually not writing the change. It is finding the right code, understanding what depends on it, recovering prior decisions, and keeping follow-up from ge…
You made the call three weeks ago. Route every Postgres connection through PgBouncer in transaction-pooling mode. You wrote down why. You walked your agent through the trade-offs. Today the agent suggested adding prep…
New users usually hit the same question quickly: where should this go? If that stays fuzzy, the system gets messy fast. This post gives you the working model for deciding what belongs in memory, what should become a d…
Your first hour with ContextStream should not be about learning every feature. It should be about feeling the core loop once: connect real work, store useful context, retrieve it later, and continue from there. This g…
AI tools are good at helping in the moment. They are much worse at preserving the state around the work once that moment ends. This post explains what ContextStream is, what problem it actually solves, and why it matt…
We've nailed cross-session persistence for AI coding tools. Now we're evolving ContextStream into an unmatched platform for context engineering.
ContextStream Skills lets you build a skill once and use it in every AI tool you work in. You can also import skills you've already built or found. No more copying between Cursor rules, CLAUDE.md, and Windsurf configs…
Most multi-agent designs split work by role. The smarter approach splits by context boundaries. But both assume agents have no memory. Add a shared context layer and the entire calculus changes — you can design by exp…
A recent paper just measured what CLAUDE.md and AGENTS.md files actually do to coding agents. The results are bad. Developer-written context files improved task success by about 4% on average, while LLM-generated cont…
The hardest part of building AI memory isn't the AI — it's deciding what deserves to be remembered. Here's how we thought through Notion integration and the tradeoffs we made.
After ~18 years of shipping products, I noticed an invisible tax: re-explaining my project to AI assistants every session. Here's how I fixed it.