One memory across your AI tools — every session opens already briefed: current goal, next action, what changed while you were gone. And when a question deserves depth, turn the dial: deep recall reads a hundred memories and answers in seconds.
This is the product. The capsule, the receipt, and the conflict alert are real hook output.
Using an AI agent? forget's llms.txt has setup instructions for LLMs.
How often the right memory lands in the top-6 results — on our hardest benchmark: 120 questions, six question types, multi-part answers scored by coverage.
The dial lives where you work — /forget in your editor, a red-thread gauge in the menu bar. Instant answers all day; depth for the questions that deserve it.
Top-6 recall, stratified across six question types (20 each); questions with multi-part answers are scored by coverage. The gear names are the contract — the engines behind them are replaceable, and every number above was measured before its engine shipped (the harness is public →). Deep gears run on a local LLM or the certified cloud model; the ceiling row reads every stored memory in full, priced beyond any dial stop. Our earlier end-to-end result — 78.4% ± 0.4 on LongMemEval, three seeds, spread published — remains in the archive →
Three surfaces the hooks put in front of you — real output, not concept art.
The capsule: your goal, next action, parallel work, and any claim that's gone stale.
About to act on a fact that was later corrected? Both versions, labeled, before you commit.
Config, rules, hooks, scope, and a live MCP round-trip — checked end to end.
One local server, one connect command. Your existing MCP setup is
preserved and backed up; disconnect reverses everything.
Decisions surface from your conversations and your git history. The observation gate keeps facts and forgets junk — nobody writes documentation.
A context capsule opens every session with your open work. Relevant memories are pushed mid-conversation — and a conflict alert shows both versions when a fact was later corrected.
Claude Code, Codex, or Claude Desktop — the answer comes back with the commit or conversation that decided it. Sync arrives sealed E2EE · IN DESIGN
The three-minute proof, once installed: start a task, kill the session, reopen. A stateless agent greets you — yours opens with a handover: goal, next step, what changed. That moment is the product.
The dial's high and extra gears read your memories with an LLM. Two ways to power them — both measured, both optional.
A coding agent (GPT-5.6, Codex) used forget across a multi-day trading-system build — data pipelines, safety constraints, live processes — and filed a structured review: acceptance criteria, regression scenarios, scores.
“Resuming long-running work: 8/10. The most valuable layer isn't generic recall — it's task state: progress, next actions, blockers, and the safety boundaries we agreed on, restored across sessions.”
Every defect it reported was reproduced, filed, and fixed — two releases within 24 hours. The issues are public →
Your model provider already reads your prompts. There is no reason your memory layer should be a second reader.
~/.forget —
storage, search, and memory building all run on your machine, offline
included. Local isn't a demo mode; it's a configuration we benchmark:
instant search alone lands the right memory in the top-6 results 89% of
the time, and the deep gears run on a local LLM if one is running.
There is no account, no telemetry, and no server of ours in the loop
unless you explicitly turn the cloud engine on.npx forget-connect disconnect
restores your original configs from backups and removes the hooks — third-party
settings are preserved byte-for-byte. Then delete ~/.forget and
your memories are gone. No account to close, no export request, no retention
window. It's your file./forget in your editor, a red-thread gauge in the menu bar — an engine axis (local · BYO · cloud), and forget cloud Pro live at $8/month.forget-server upgrade is the one prescription.Because memory that cannot be deleted is surveillance. Ours forgets on command.
Supersede, retire, delete — every fact in forget can be struck through, and the strikethrough keeps the history. The logo is not a joke about the product. It is the product.