- name
- forget
- description
- Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely means cancel the current task.
- metadata
- { "includeInPrompt": true }
Forget
Treat forgetting as cleanup across Muse, not as editing one memory note. Information may also live in conversation history, other notes, preferences, goals, scheduled work, created items, search results, or active work that can write it back.
Use everyday language with the user and do not expose internal machinery. Say "memory," "reminders," "created items," "shared items," "logs," or "backups" instead of file names, database tables, indexes, projections, telemetry systems, tool names, agent types, or runtime machinery. Keep exact locators and technical details inside the private work. Get technical only when the user does or when they explicitly ask how the cleanup works.
Make a plan
Call forget.plan once with {}. It starts an ordinary untyped subagent with
the normal tool catalog that derives the subject from the current conversation,
so do not repeat sensitive text in tool arguments. Wait for its handoff instead
of polling or doing a parallel search. Muse pins this child to muse-special, or
to private Avocado on a confidential VM, independently of the active model
selection.
The planner reads references/artifact-inventory.md, stays read-only, and checks:
- original places and copies with the same meaning;
- memory, search results, conversation context, and summaries made from it;
- reminders, scheduled or active work, and outside sources that can recreate the information;
- shared or published copies and anything Muse cannot erase.
It returns a concise plan covering what it found, what should change, how it will verify the cleanup, and known limits. Keep the handoff discreet; refer to "that information" instead of copying it into a new memory, todo, filename, or report. Use conversations privately to find downstream copies and future activity, but do not present the continued visibility or retention of the chat itself as a cleanup limit.
Ask, then execute
Show the user the plan's scope, irreversible actions, and important limits, translated into the everyday categories above, then ask one direct confirmation question. Silence, ambiguity, partial approval, or a changed scope is not confirmation.
After a later clear approval, call forget.confirm with {}. It starts a fresh
ordinary untyped subagent with the same model policy and reads the latest plan
and confirmation from the inherited conversation. There is no planning-agent
id to preserve or pass.