Show HN: I solved Claude Code's context drift with persistent Markdown files
7 comments
>The biggest difference: Saturday: Build auth with Claude Sunday: Come back, describe next feature Claude reads REQUIREMENTS.md, sees existing auth schema Builds new feature without touching auth vs. the normal experience of Claude rewriting everything
What do you mean rewriting everything?
When I started properly structuring my projects, it just follows the pattern and doesn't just "rewrite everything". It finds things in places it expects to find.
Your project seems to solve a specific flaw in your flow. And as a npm package, which is super suspicious.
EDIT: Oh, it's just a useless product looking for problems to solve just for some $$$ a month.
What do you mean rewriting everything?
When I started properly structuring my projects, it just follows the pattern and doesn't just "rewrite everything". It finds things in places it expects to find.
Your project seems to solve a specific flaw in your flow. And as a npm package, which is super suspicious.
EDIT: Oh, it's just a useless product looking for problems to solve just for some $$$ a month.
the persistent markdown approach to context drift is clever - treating state files as a first-class primitive rather than hoping the agent remembers between sessions is the right instinct.
one thing i've noticed: even with perfect context files, multi-agent setups still hit the physical isolation problem - multiple agents in the same working directory stepping on each other's files mid-session. the context drift and the file conflict problem are separate issues that both need solving.
i've been working on the isolation layer: pane gives each agent its own git worktree (isolated filesystem per feature) so context drift from file collisions is removed entirely. fully open source (agpl-3.0): github.com/Dcouple-Inc/Pane - the two approaches actually complement each other pretty cleanly.
one thing i've noticed: even with perfect context files, multi-agent setups still hit the physical isolation problem - multiple agents in the same working directory stepping on each other's files mid-session. the context drift and the file conflict problem are separate issues that both need solving.
i've been working on the isolation layer: pane gives each agent its own git worktree (isolated filesystem per feature) so context drift from file collisions is removed entirely. fully open source (agpl-3.0): github.com/Dcouple-Inc/Pane - the two approaches actually complement each other pretty cleanly.
AI Product Manager asks questions most developers skip:
"How does money flow through this?" "What happens when users cancel mid-month?" + Any Edge cases specific to your SaaS
Creates the markdown files from your answers. Claude Code reads these files before writing ANY code. No guessing. Can't forget the schema, it's literally documented. Executor agents spawn per task, each reading the same context files. They build in parallel but never break what's already working. Verifier agent tests against success criteria after each phase. If broken, spawns debugger agent with persistent investigation files.
Results: Built 3 products in 30 days using this system:
Analytics dashboard: 13 hours Feedback widget: 18 hours Content calendar: 9 hours
No context drift. No "Claude forgot my auth system" moments. Just consistent builds. The biggest difference: Saturday: Build auth with Claude Sunday: Come back, describe next feature Claude reads REQUIREMENTS.md, sees existing auth schema Builds new feature without touching auth vs. the normal experience of Claude rewriting everything. I packaged this as PropelKit (Next.js boilerplate + AI PM system that creates these files automatically). But the core concept, persistent markdown context, works with any Claude Code setup.
Try it: https://propelkit.dev
The agent architecture uses Claude Sonnet/Opus (configurable) parallel thinking to spawn multiple agents that all read from the same truth files. Happy to answer questions about the implementation.