note

Persist notes across conversation compaction by saving entries to a persistent on-disk notepad at .omx/notepad.md. This ensures important context remains accessible even when the active chat session is trimmed or compacted.

Retain important session context by writing details like incident notes or team contacts to the on-disk notepad. The file stores entries with timestamps so you can load and recall critical information after compaction occurs.

Save notes with timestamps by creating or updating entries directly in the .omx/notepad.md file. Each entry records the note content and timestamp, allowing debugging and recall across multiple sessions.

Yes, you can organize notepad entries with optional priority and manual sections in .omx/notepad.md. This structure allows you to create, update, and retrieve categorized notes alongside their timestamps.

Yes, the on-disk notepad works for recording incident details, deployment notes, and team contacts. Loading these entries on session start ensures critical debugging and reference context stays available across sessions.

You need an on-disk notepad when important context vanishes from trimmed or compacted chats. If critical information must remain accessible across multiple long-running sessions, persisting notes to disk solves the recall problem.