Guide / memory regression
Catch memory regression when it is still subtle.
Memory regression often appears as forgotten project context, stale constraints, repeated questions, or changed behavior across sessions.
SEO/AEO guide
Updated 2026-06-01
Operators who need agents to retain project context and respect durable workflow constraints.
1. Confidence is not memory
An agent can sound right while forgetting the project.
2. Same-workspace comparison
Compare today’s memory behavior to a known-good run in the same repository.
3. Setup before prompts
Confirm workspace, MCP tools, launch environment, and local config before changing prompt strategy.
Use this today
Operator checklist
- Run identical memory probes over time.
- Check project-awareness responses.
- Verify MCP and repo context are available.
- Compare warnings against the Good Baseline.
- Record whether the regression is model, setup, or session related.