What is stored where
OptiFlume keeps its data under ~/.optiflume on your Mac, in plain text and SQLite you can open.
| Path | Contains | Kept |
|---|---|---|
telemetry/routing-events.ndjson | One line per routing decision: what it judged, the model it chose, the outcome, first 40 characters of the prompt. | 90 days |
telemetry/turn-activity.ndjson | Which tools ran each turn: file reads, edits, shell commands, failures. | 90 days |
telemetry/safety-audit.ndjson | Every secret redaction and blocked or warned command. | 90 days |
turns/ | Cached turn output with segment labels, for working-memory extraction. | 30 days |
working_memory/ | The working-memory notes distilled from your conversations, for handoffs. | Until you delete it |
sessions/, state/ | Current session: edits, errors, compactions, alerts, pending choices; also the trial meter, the compatibility list and a random device id. | Session files per session; the rest until you delete it |
indexes/ | The code index and the conversation index. SQLite and JSON. | Until you delete it |
learned/ | How you override it, and what it has learned from that. | Until you delete it |
cache/ | The local models (about 1 GB, in cache/models/), the list of models Cursor offers, and the last price lists. | Until you delete it |
license/ | Your sign-in session and your signed license. Readable only by you. | Until you sign out |
config/ | Your settings. | Until you delete it |
logs/ | Diagnostic logs from OptiFlume in each tool, and from updates. | Until you delete it |
The 90- and 30-day limits are applied each time a Cursor session starts. Claude Code and Codex sessions don’t apply them yet, so without Cursor the routing log keeps growing; delete it whenever you like.
What the installer changes
Everything OptiFlume adds to your Mac, so nothing is a surprise. Installing step by step is covered in Install and uninstall.
~/Library/Application Support/OptiFlume: the program itself. The macOS installer unpacks it in/Library/Application Support/OptiFlume, which is why it asks for your password once, then moves it into your user folder.~/.optiflume: your settings, logs and indexes, listed above, and the files your editors use for Claude Code and Codex while they are on. Earlier versions kept your data in~/.intent-router; the installer moves it and leaves~/.intent-routeras a link to~/.optiflume.~/.optiflume/bin: theoptiflumecommand, and OptiFlume’s ownclaudeandcodexcommands if the terminal is on. It is the only folder added to your PATH.- One
PATHline in~/.zshrc(or~/.bash_profile, or a fishconf.dfile), marked# OptiFlume CLI. It puts~/.optiflume/binfirst on your PATH, soclaudeandcodexin a new terminal run with OptiFlume. Updates move the line to the end of the file so it stays first.optiflume terminal offturns this off. - For Claude Code and Codex in your editors: a setting in each editor so its Claude Code and Codex panels use OptiFlume, one Codex hook in a marked block of
~/.codex/config.toml, and the OptiFlume Status extension. Claude Code and Codex memory and instruction files (CLAUDE.md,AGENTS.md), transcripts and sign-ins are left alone, and Claude Code’s settings are only read, never written. - For Cursor, added on every Mac whether or not you use Cursor: OptiFlume’s hooks, added to Cursor’s hook list,
~/.cursor/hooks.json(hooks you already had stay); a short rule,~/.cursor/rules/optiflume.mdc, so Cursor’s assistant can explain OptiFlume’s notes when you ask; and the OptiFlume Bridge extension, installed through Cursor’s own extension installer (or copied into~/.cursor/extensions).
optiflume uninstall removes the program and puts your editor settings back as they were, keeping your data in ~/.optiflume; optiflume uninstall --purge also deletes that local data. (macOS keeps its usual record that a package was installed; if any shared files were left in /Library, the uninstaller prints the one command to remove them.)
What never leaves
Your prompts and your code: OptiFlume never sends them anywhere. Every decision is made locally. Claude Code and Codex still send your prompt to the model you use, as they always have, and OptiFlume never sees your Claude or ChatGPT sign-in or API keys. On your Mac, the routing log keeps a 40-character snippet of each prompt for your own analytics, and working memory and the turn cache keep session content for handoffs. The code index is built on your Mac from your files and kept in ~/.optiflume/indexes/code; it is never sent anywhere.
What leaves, and how to stop it
- Plan check, at sign-in and then up to twice a day: your Mac sends its sign-in session and receives a signed license. Required for Pro and the trial. A license lets the Mac work offline for up to about 30 days, plus a 14-day grace period unless the license ends with your paid period.
- Update check, when Cursor or VS Code starts, when a Claude Code or Codex session starts, and every few hours; a newer, verified version then downloads from get.optiflume.ai and installs itself. Set
"auto_update": falseinconfig/routing-config.jsonto be asked first, or"update_check": falseto turn the check off. - Local models, downloaded once after install (about 1 GB) from get.optiflume.ai, or huggingface.co as a fallback.
- Model prices, daily from optiflume.ai/api/prices (Cursor’s published prices, signed); for a model that list lacks, from Cursor’s public page (cursor.com/docs/models-and-pricing.md) at most once a day, only when Cursor offers a model OptiFlume has no price for. Nothing about you is sent.
- Compatibility list, fetched daily and signed, so a breaking Cursor update can be paused the same day. It carries no information about you beyond the request itself.
- Usage rollup for your console, on Pro and the trial: daily counts only, at most every six hours.
optiflume telemetry offdisables it, or turn it off for every Mac in console settings. See Analytics and telemetry for the exact fields.
Delete
rm -rf ~/.optiflume/telemetry # just the logs
optiflume uninstall --purge # everything on this MacTo delete what our servers hold (your account, plan and stored usage counts), delete your account in the console; see Account, Macs and billing.