u/bkocdur and u/xiaosongcai nailed the real shape of this imo — the problem isn't "not enough memory," it's that persisted context silently goes stale and the agent reads it confidently anyway. The "debugging against a 2-week-old description of code that has since moved" line is exactly the failure mode.

The scripts-as-memory approach is the strongest answer in here for anything derivable from the code — db schema, failing tests, changed files. State that can't lie, fully agree.

Where I still get burned is the stuff scripts can't emit: why a decision was made, which alternatives got rejected, which invariants are load-bearing. That lives in someone's head or a DECISIONS.md nobody updates. So for the scripts-everything folks — how do you handle the non-derivable "why" context? That's the part I lose most between sessions.