Skip to main content
Chief can capture memories for you while you task. When collection is turned on, Chief notices useful facts and preferences in your conversations and saves them automatically — so your memory list builds itself.

Turn on auto-capture

The Collect user memories from conversations toggle, switched on
  1. Open the memory page for the scope you want: Settings → Memory for Your Memories, the project’s Memories page for Project Memories, or the organization’s Memory page for Organization Memory.
  2. At the top of the page is a toggle switch. For personal memories it’s labeled Collect user memories from conversations; for a project, Collect project memories from conversations; for an organization, Enable organization memory.
  3. Click the toggle so it switches on. Collection is now active for that scope.
ℹ️ Good to Know: The toggle is per scope. Turning on collection for Your Memories doesn’t turn it on for a project, and vice versa — set each one where you want it.
Chief only auto-captures Project Memories from tasks with Project visibility. Private and Restricted tasks don’t add background Project Memories, but they can still add to Your Memories when personal collection is on.

What happens when Chief captures a memory

Memories Chief captured automatically, listed under Your Memories
After a task where Chief saves or changes memories, a small button with a brain icon appears in the answer’s action row, reading 1 memory or, for example, 3 memories. Click it to jump straight to the relevant memory page: Settings → Memory when every change was personal, otherwise the project’s Memories page. The count adds up every memory change in that task, including memories Chief saved while it answered. When a new memory restates, updates, or reverses one you already have, Chief merges it into the existing memory instead of adding a duplicate — so 3 memories means three changes, not necessarily three new entries.

Turn off auto-capture

  1. Go back to the same memory page.
  2. Click the toggle so it switches off.
  3. A notice appears: “Memory collection is disabled. Existing memories are still available and can be managed below.”
Turning collection off stops Chief from capturing memories in the background after your tasks in that scope. Chief can still save a memory while it answers — for example, when you ask it to remember something — and the memories button shows under that answer. Turning collection off does not delete anything you’ve already saved — your existing memories stay and keep working.
🚀 Pro-Tip: Leave collection on and click the memories button under an answer now and then to review what changed. It’s far less work than adding every memory by hand, and you can edit or delete anything Chief gets wrong.

FAQ

No — that’s intended. Turning off collection only stops new memories from being captured. Your existing memories remain available and Chief can still use them. Delete or archive any you no longer want.
Open the memory page, find the entry, and click Delete (trash icon) to remove it, or Edit (pencil icon) to fix the wording. To stop similar background captures going forward, switch the collection toggle off for that scope. Chief can still save a memory when you ask it to remember something.
Check four things: the collection toggle is on for that scope; the task’s memory mode isn’t set to Off in the prompt bar’s Memory menu; for project memories, the task’s visibility is Project — Chief doesn’t capture project memories from Private or Restricted tasks; and the conversation actually contained a durable fact worth saving — not every message produces a memory.