Working memory and session watchdog

Long sessions lose the thread. OptiFlume keeps it, and tells you when a session is going in circles.

Working memory

When a conversation grows long, your tool compacts it: older turns are summarized to make room, and details get lost. OptiFlume keeps a short working memory of each session as you go: what you are trying to do, the decisions made along the way, and the approaches that already failed. After your tool compacts a long conversation, OptiFlume hands that working memory to the model, so it picks up where you were instead of retrying what did not work.

Once a conversation has been compacted, the working memory goes with your later prompts too, so a model OptiFlume switches to mid-session has it as well, not only your tool’s summary.

There is nothing to click and nothing to configure. It is part of Pro and the trial; it also continues while OptiFlume is paused.

Where it lives

On your Mac only. The notes are kept in ~/.optiflume/working_memory/, and the cached turn output they are built from in ~/.optiflume/turns/ for 30 days. Neither is ever sent anywhere. To remove them:

rm -rf ~/.optiflume/working_memory ~/.optiflume/turns

Every file OptiFlume keeps is listed in What is stored where.

Session watchdog

The watchdog follows the session as it runs and adds a short warning when a session seems to be going in circles: the same fix keeps failing, or a long chat has started to lose track of earlier details. Your prompt still goes through; the warning is advice, not a block. When the signs add up, it suggests a fresh chat or a more capable model.

The watchdog runs on Pro, the trial and the free tier. It is off while OptiFlume is paused or this Mac is signed out. The number of loops it caught each day appears in your usage rollup and on the console, as a count only.