note

To save context and notes that survive conversation compaction, use a persistent notepad file to store critical information. This ensures long-term context retention and allows important data to remain available even after long sessions or context resets.

Managing persistent notes for complex coding tasks involves saving information to different sections of a notepad file. You can store critical API endpoints, team contacts, or debugging findings directly into the notepad to ensure they are always available.

You differentiate between critical priority context and temporary working memory by saving notes to distinct sections of a notepad file. This context management supports always-loaded priority context, auto-pruning temporary working memory, and permanent manual notes.

Yes, you can automatically load saved notes when a new session starts. The notepad integrates with session startup to automatically load priority context, ensuring your critical information is immediately available without manual retrieval.

To add information to your priority context quickly, add the desired text directly to your notepad file. For example, adding "Project uses pnpm" to your priority context ensures that specific project constraints are always loaded during your sessions.

A limitation of using a markdown notepad file for long-term context retention is that temporary working memory requires auto-pruning to manage size. You must manually categorize notes into priority, temporary, or permanent sections to maintain efficient context loading.