Skip to main content

Save Reusable Context

Memory is for maintained knowledge that should stay available across work. In Chat, context is the temporary material in a conversation: messages, files, selected agent state, and tool results.

Use Memory For​

  • Team playbooks.
  • Terminology and standard answers.
  • Policies, FAQs, and escalation rules.
  • Customer or project notes that need maintenance.
  • Short reusable guidance that agents should apply repeatedly.

If an agent has Memory attached, it can still be read-only. Ask an admin or agent owner whether Memory write is enabled before expecting the agent to create or update Memory pages directly.

Use Data Instead When​

  • The source is a file, folder, repository of documents, synced SaaS system, or website crawl.
  • You need processing status and source-level updates.
  • The source should be attached to a specific agent or collection.

Follow Use Sources and Files for that workflow and use the Data Product Specification for every source type and field.

Keep Memory Useful​

  • Keep pages short and current.
  • Name the audience and scope.
  • Remove stale rules instead of adding corrections below them.
  • Tell the agent which Memory page to use.
  • Ask the agent to say when the answer is not present in Memory.

Example​

Use the Support Escalation memory page. Classify this customer issue, explain the next step, and list anything missing from the memory page.

Fix Wrong Context​

If the answer uses the wrong customer, policy, or prior instruction, start a new conversation or explicitly reset context:

Ignore earlier customer examples in this conversation. Use only the attached contract and the Enterprise Pricing memory page.

If you need to preserve evidence from the previous work instead of resetting it, follow Continue Past Work.

Last updated on