Memory for coding agents
Keep architecture choices, debugging notes and unfinished decisions available for the next coding session.
A task to start with
Recall why we chose this authentication library. Summarize the unresolved issues and propose a next step before changing code.
Use notes you are authorized to share. Review the draft before taking action.
From saved context to a working draft
Saved notes
Decision note: keep the existing auth library for migration compatibility. Open issue: refresh tokens expire during long sessions.
Example draft to review
- Keep the current library; the migration depends on its session format.
- Investigate refresh-token expiry before proposing a replacement.
- Add a long-session regression test; no code changes yet.
Start with a useful draft
Review a plan grounded in the decisions you saved, then give your coding agent a specific task.
Keep the right boundaries
Connect a compatible client through MCP and explicitly save important decisions. Connecting MCP does not automatically record every prompt.