[Bug] Memory not automatically updated after code changes in conversation

Bug Description
My current conversation with Opus 4.6 on max settings was productive and as expected but the changes we (opus 4.6 and I) implemented were not propagated to the memory by default. Only after I explicitly asked, was memory updated which is the issue becasue subsequent conversations would have used outdated values stored in memory.

Environment Info

• Platform: darwin
• Terminal: windsurf
• Version: 2.1.86
• Feedback ID: 543afe70-e9c3-4c4e-a668-d64104a21498

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/tony/.local/share/claude/versions/2.1.86 (expected in multi-process scenarios)\n    at _p_ (/$bunfs/root/src/entrypoints/cli.js:2851:2138)\n    at Vn6 (/$bunfs/root/src/entrypoints/cli.js:2851:1218)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-03-28T20:26:48.711Z"}]