Skip to content
Runner AI
Agent customization
English
Esc
navigateopen⌘Jpreview
On this page

Memory

Save stable facts and preferences that Runner can carry into future work.

Memory is for concise facts Runner should retain, such as a writing preference, a corrected business rule, or an approved decision. It reduces repeated explanation across tasks.

What this covers

You will be able to add, find, edit, and safely delete a memory.

Availability and prerequisites

  • You need a store project.
  • The Memory tab appears only when unified Memory is enabled for your account.
  • Memory is separate from the Skills plan gate.
  • Never save passwords, API keys, payment details, private credentials, or other secrets in Memory.

Entry path

Select Agent in the sidebar, then the Memory filter.

Memory controls

Entry or button Why it is useful What happens next
Add a memory Save a new fact for Runner. The New memory dialog opens.
Content State the fact Runner should retain. This text becomes the visible memory.
Scope Choose where the fact should apply. Select This store, Personal, or Organization.
Type Explain what kind of fact it is. Select Preference, Correction, Convention, Knowledge, or Decision.
Tags Make the memory easier to find and group. Enter one or more comma-separated tags. At least one tag is required to save.
Importance Tell Runner how strongly to weigh the fact. Select Low, Medium, or High.
Add memory Save a valid new memory. The dialog closes after success and the memory appears in its scope group.
Edit icon Correct or refine a memory. Edit memory opens with the current values.
Save Apply an edit. The row refreshes after the update succeeds.
Delete icon or Delete Remove a memory. Runner opens a destructive confirmation dialog.

Add a memory

  1. Open sidebar Agent, then select the Memory filter.
  2. Select Add a memory.
  3. Write one clear fact in Content, such as “Use sentence case for headings in this store.”
  4. Choose the narrowest correct Scope.
  5. Choose the closest Type.
  6. Add useful comma-separated Tags, such as copy, headings.
  7. Set Importance. Use High sparingly for facts Runner should prioritize when information competes.
  8. Select Add memory.
  9. Confirm the new row appears under the intended scope.

English annotations: New memory form with an example preference and This store scope

English callouts highlight the controls. Select the image to enlarge it.

The example is an unsaved preference. Choose the narrowest scope before selecting Add memory.

Watch: choose a memory scope

The recording inspects the scope choices for an example preference, then cancels. It does not save a memory. Follow the steps above and check the new row to confirm your own save.

Edit or delete a memory

  1. Find the memory by browsing its scope group or using search.
  2. Select the edit icon, update the fields, and select Save. Reopen the row to check the new content and scope.
  3. To remove it, select the delete icon or Delete inside the edit dialog.
  4. Review Delete memory and select Delete to confirm.

Deleting a memory cannot be undone from this dialog. Cancel closes the confirmation without removing it.

States and limits

  • A new account can show No memories yet with an Add a memory action.
  • A search with no match says how many memories are hidden and offers Clear search.
  • Content and at least one tag are required before the save button becomes available.
  • Memories are grouped by scope and show their type, scope, use count, and recent-use time.
  • Memory makes a fact available to Runner; it is not a guarantee that the fact will override every instruction or safety boundary.

Troubleshooting

  • If the Memory tab is absent, use visible navigation rather than an old direct link. The feature is not enabled for the current account.
  • If Add memory is disabled, add Content and at least one comma-separated tag.
  • If the list seems empty after search, select Clear search.
  • If an edit fails, the previous memory remains. Correct the displayed issue and retry.
  • If a memory is being applied too broadly, edit it and choose a narrower scope.

Last updated on September 8, 2026

Was this page helpful?