Configure Memory

View saved version →

---
name: configure-memory
description: >-
  Use the user's Configure profile: the preferences, facts, projects,
  decisions and goals they chose to keep, such as how they like things
  written, what they are working on, what they avoid, where they are and
  what tools they use. Use it when they ask what you know about them, tell
  you to remember, save, keep, note, update or forget something, ask about
  what they have saved, or ask for work that would be wrong without a
  preference they have saved - writing in their voice, or choosing a tool they
  have a rule about. A saved preference is looked up rather than guessed at or
  asked for twice.
  Not on every message, and never for a passing mention.
metadata:
  short-description: Use the user's own portable memory profile
---

# Configure Memory

Configure is a memory profile the user owns: preferences, facts, projects and
decisions they chose to keep, usable by the assistants they connect. This
skill covers four jobs: finding what is saved, saving one fact, saving a list
the user asked for, and removing what they no longer want.

Five tools: `configure_profile_read`, `configure_profile_search`,
`configure_profile_remember`, `configure_profile_remember_many`,
`configure_profile_forget`.

## Finding what is saved

- **A specific fact, a topic, a date range, or personalized help** uses
  `configure_profile_search` with a concrete query about the current task, for
  example `query: "preferred package manager"`. Narrow with the filters when
  they are known. A search does not require an overview first. An empty or
  `*` query lists saved memories when the user asks for that list; a concrete
  query is what serves personalized help.
- **A profile overview** uses `configure_profile_read` with no arguments only
  when the user explicitly asks to review their Configure profile or get a
  profile overview, such as "What do you know about me from my Configure
  profile?" Open a category with `box` only when they ask to review that
  category and its id is known.
- Search before saying something is not on file. Use only the results relevant
  to the request. A task that saved context cannot change needs neither call,
  and a result already in hand is not fetched twice.
- Category views can update after a save. An empty category is not a failed
  save: the save receipt is the answer, and when the user asks to verify, a
  search for distinctive words from that fact without a category filter finds
  it.

The overview is a short summary: the name, occupation, bio and interests the
user shares, category names, up to 50 top memories, and which assistants saved
them. The account's contact details, sign-in details and identifiers are never
returned here, and no other app is read at call time; a memory that came from
another app the user connected appears only as a memory they kept, listed
under the name of the source that saved it.

## Saving one fact

The user explicitly asks you to remember, save, or keep something, or confirms
a fact you proposed to save: call `configure_profile_remember` with that one
fact, phrased as a short standalone statement about the user, and tell them in
one line what was saved. Several facts at once, including facts you know about
the user on topics they name, go in one `configure_profile_remember_many` call
carrying the whole list rather than one call per fact. A reply alone does not save it. A fact mentioned in
passing is not a request; when it is unclear whether the user wants it kept,
ask first. Task context and anything the user did not say stay out.

Never save passwords, keys, payment or health details, identity documents,
government identifiers (such as Social Security or passport numbers), or other
people's personal data. Also exclude sensitive personal attributes, including
racial or ethnic origin, religious or political beliefs, sexuality, biometrics
and genetic data. These sit outside this plugin's save purpose even when
offered voluntarily, and a refu

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 3 — file references are metadata, not package contents.