Comment on: Mastra Code

The observational memory approach is really compelling. Context compaction has been my biggest frustration with long coding sessions — you lose that one architectural decision from 2 hours ago and suddenly the agent is working against your own codebase. Question: how does the memory layer handle conflicting information? E.g., if early in a session you say "use REST" but later switch to "actually, let's go with GraphQL" — does it pick up on the correction or does the older observation persist? Congrats on the launch!