note

To save notes and maintain context across sessions, use the /note command to append entries to a persistent notepad. This ensures critical information survives conversation compaction and remains available for future review.

Keeping track of project details is best handled by saving them to a persistent notepad. You can store critical information in a priority context section that is automatically loaded at the start of every new session.

Working memory handles session notes by automatically pruning timestamped entries after 7 days. This keeps the active context clean while ensuring temporary information is retained for the duration of its usefulness.

Yes, you can maintain permanent notes by adding them to the MANUAL section of the notepad. Entries placed in this section are never pruned, ensuring long-term information retention without manual cleanup.

Saved context is not affected by conversation compaction because notes are stored in a persistent notepad file. Critical information saved to priority context is always loaded at session start, ensuring continuity.

You need a session-specific notepad when you must preserve important information like API details or project dependencies across multiple interactions. It provides timestamped entries and prevents data loss during context limits.