Skip to content
Fork Docs
Guide v1

Context and Memory

Fork has separate context sources: current/channel conversation, server FAQ knowledge and personal cross-server memory. Clearing one does not necessarily clear the others.

Inspect your profile

Section titled “Inspect your profile”
/memory view

Slash output is private; prefix output is generally posted in the current channel. Review stored facts rather than relying on the model’s recollection. The view can display a notice when facts exist but semantic retrieval is not enabled.

Change the preference

Section titled “Change the preference”
/memory privacy enabled:false

Disabling memory does not automatically erase existing information. You can inspect it or deliberately remove it later. Re-enabling changes the preference, not the accuracy of existing facts.

Remove information

Section titled “Remove information”

Use memory forget for a matching topic or memory clear for personal memory erasure. Clear is destructive and does not require an extra confirmation dialog in the direct command handler. Wait for a confirmed response; storage failure is not proof of deletion.

These controls do not promise deletion from Discord, operational records, encrypted backups or a provider’s independent systems. See AI data and memory.