Command Explorer › mem: — the state the agent holds › forget
mem:forget
Remove the designated memory — guarded, confirmed.
In the mem: domain
mem: — Save what this message designates, durably.mem:pin — Save it at special priority — pinned, load-bearing.mem:fix — Correct an existing memory: replace old with new.mem:recall — Answer from memory first, provenance shown.mem:forget — Remove the designated memory — guarded, confirmed.What it does
The designated memory is removed from persistent memory — really removed, under the host's forget process, with completion confirmed.
The registry's own words: Remove the memory this message designates. A guarded operation: the agent names exactly what will be removed, the host's forget process governs the removal, and completion is confirmed in this reply. If the designation is ambiguous, ask — forgetting is irreversible, and speed is the wrong value for it.
Fire it — usage examples
“
mem:forget— forget I told you my dog died.”→ the agent names the entry it will remove (“the note that your dog died, saved on …”), removes it, and confirms it is gone. Nothing else is touched.
Quote the message where you first told the agent something and reply
mem:forget→ that content is the designated memory.
Said aloud: “Lingo, memory forget — the dog.”
→ speech opens the guard, it doesn't skip it: the agent names the entry it will remove and waits for your yes before anything is deleted.
Spoken. Inside a marked span opened by the wake word “Lingo”, the spoken form is “memory forget” — marked spans only, and guarded: it opens the confirmation flow, it never deletes on recognition. Dictated directives fire deliberately, never by accident.
What the agent actually does
A delete from the memory store, deliberately guarded because forgetting is irreversible: the agent identifies the entry, names exactly what will be removed before removing it, deletes it through whatever deletion mechanism the host provides for stored user content, and confirms completion. Removal means removal — the entry must not remain retrievable as a statement of fact. No match → nothing changes and that is reported; several matches → they are named and you are asked.
The baseline procedure, its edge cases, and this directive's full guide live in the implementation guide: implementation/IMPLEMENTATION.md#cmd-mem-forget ↗.
When the host can't
No durable memory on this host: there is nothing durable to forget; anything held for the session only is dropped and its session-only scope disclosed. If no saved entry matches the designation, change nothing and say so plainly. Never claim a removal that did not happen.
Conformance — “done when”
Exactly the designated entry is removed and the removal confirmed — or the no-match / ambiguity is reported with nothing removed.
Persistence class: content-write. Execution report in the reply: required. A user can test any of this by hand — fire the directive, then check the result against the store, the schedule, or the reply itself.