How are you guys handling mid-session requirement updates right now?  
i have problem for project requirements keep shifting in mid session. I am leading a small dev crew, shifting project requirements mid-session are a constant daily reality. A PM changes a spec on Slack, a client pivots during review, or you realize mid-refactoring that an earlier architecture choice won't scale.  
like a user starts by asking for a PostgreSQL setup, then changes to MongoDB three turns later, and eventually settles on Redis with PostgreSQL. prompt history just pends every single change, leaving five conflicting sets of rules sitting in the context window. The model starts hallucinating by mixing old constraints with new ones.I ran into this exact headache during a long refactoring session and fix it with Memmy running locally on Linux. Instead of appending every new requirement to an ever growing message log, Memmy handles constraint updates through in-place state mutation.  
When a rule changes, the local memory layer replaces the outdated constraint in the active state slot rather than stacking another paragraph onto the prompt. The active context window always stays lean and only contains the latest ground truth, while Memmy tracks the update locally on disk.

Shifting requirements kept ruining my long sessions until I started mutating state locally on Linux