Meta’s Muse data guide distinguishes removing a source from removing what the agent learned. Deleting a message or file can leave remembered information behind. Asking Muse to forget instead prompts it to search memories and supporting files and remove relevant information to the best of its ability. That wording describes a supported control, not a guarantee that every trace will disappear.
A full reset has a broader cost: Meta says it permanently removes chats, files and active tasks and cannot be undone. The guide also provides a data-download option. Separately, the connector guide says disconnecting an app stops future data exchange while previously used information may remain in memory or chat history. These are existing documented controls; the pages show relative update labels rather than exact dates, and we have not tested deletion or reset behavior.
Editorial take: Before resetting an agent, inventory the work it is still doing and preserve any output you need. For one outdated project detail, a targeted correction or forgetting request may be the more appropriate starting point. Check the result afterward. Clearing the whole workspace can remove unfinished obligations alongside unwanted context, so a privacy cleanup also needs a continuity plan.