short-term-memory

To preserve context across session compactions, use a per-project current-context.md file that stores recent decisions and next steps. Claude reads this file before every response and updates it with a timestamp after each interaction, ensuring momentum survives compactions.

Per-project memory persistence is the practice of maintaining a current-context.md file in your project directory. This file is read before responses and updated after interactions, keeping recent decisions, blockers, and next steps available across sessions and compactions.

Place a current-context.md file directly in your project directory. Entries should use the YYYYMMDD-HHMMSS timestamp format and remain concise. The file is read before every response and updated after each interaction, with older entries archived when the log grows.

Yes, this context persistence approach applies across any project. It requires placing the current-context.md file in the project directory and keeping entries concise while preserving recent decisions and next steps, making it platform-agnostic for workflow automation.

When the current-context log grows too large, older entries are automatically archived. This keeps the file concise and ensures only recent decisions, blockers, and next steps are preserved for reading before every response during session resumes.

Claude Code loses momentum after a session resume because recent decisions and next steps are not retained by default. Maintaining a current-context.md file that survives compactions and resumes solves this by preserving working context per-project.