Best practice L2 · Context engineering informational

Turn Memory Off for One-Off or Sensitive Work

What it is

A control habit: use a temporary chat or turn Memory off when you're sharing sensitive information or doing throwaway work you don't want influencing future conversations.

Memory ondefault work· Preferences persist· Ongoing projects· Reusable contextMemory off / temporaryone-off & sensitive→ Confidential details→ Throwaway exploration→ Nothing to carry forward
Some context should never outlive the conversation it was shared in.

Why it works

Memory is useful precisely because it persists — which is exactly wrong for confidential details or one-off contexts you don't want resurfacing later. Switching it off for those sessions keeps sensitive input from lingering and stops unrelated, disposable context from quietly shaping answers weeks from now.

When to use it

Sharing private or confidential material, exploring something off-topic you don't want remembered, or testing prompts where persistence would pollute your real Memory.

When not to use it

Ongoing work where persistence is the benefit — your standing preferences and active projects should stay in Memory.

Prompt

[In a temporary chat / Memory off] Handling this here so nothing persists: <sensitive or one-off task>. Treat it as isolated from my ongoing context.

Example

Reviewing a confidential contract in a temporary chat means those clause details never end up in Memory and can't surface in an unrelated conversation later.

Common mistakes

  • Sharing confidential details in a normal chat and having them persist.
  • Letting throwaway experiments accumulate in Memory and skew later answers.
  • Forgetting to check whether Memory is on before a sensitive session.

Related