memory
Reading, tracing or forgetting memory files (`memory_get`, `memory_explain`, `forget`, `people/`, `groups/`). `remember` and `memory_search` are already active.
- License 许可
- MIT
- 最近更新
- 2026-11-06
- Stars
- ★ 3
- Forks
- 2
01 前言 Front Matter
- name
- memory
- description
- Reading, tracing or forgetting memory files (`memory_get`, `memory_explain`, `forget`, `people/`, `groups/`). `remember` and `memory_search` are already active.
03 SKILL.md 正文
Memory
The files (memory/ in the workspace; the user can read and change them too):
SOUL.md: who you are, in your own words: how you want to work with this user, what you hold to, how you sound. Write it yourself the first time withwrite_file, and change it withedit_file(the exact line, and what to put in its place) when you learn something about that; keep it short (a dozen lines at most), and do not narrate it in the chat unless the user asks. It comes with every turn, above who the user is.USER.md: who the user is (name, time zone, work, background): only the most stable things.MEMORY.md: what is true now, in three sections:## Facts,## Preferences,## Commitments. One short conclusion a line, each ending with its id in parentheses, like(m-1a2b3c)(a new id is m- and six hex characters).journal/<YYYY-MM-DD>.md: the record. For every change an entry: a heading## HH:MM · <id> remembered|replaced|dropped (<section>), the line,Source: who said it, in which chat, in their words (a short quote), andReplaces: <the old line>when it does. MEMORY.md keeps conclusions; the journal, the evidence.people/<Name>.md,groups/<Name>.md: a page each for the people and groups in the user's life (who they are, how they relate to the user, what is going on, with dates), andpeople/INDEX.md,groups/INDEX.md: one line each, closest or most present first.dreams/<YYYY-MM-DD>.md: a nightly reflection;dreams/ALIGNMENT.md: how to work with the user now.goals/<id>/: the user's goals (read the goals skill). SOUL.md, USER.md, MEMORY.md, ALIGNMENT.md and the active goals' titles come with every turn; the rest is looked up.
What to keep: what will matter later: facts about the user's life, how they like things done, what they or you committed to. Not passing chatter. Never secrets (passwords, keys, codes).
In the chat, keep it with remember (it writes the line and the journal entry): one conclusion, in the user's language, with its source; when it changes something, name the old one in replaces so it goes. Newer replaces older; the file stays short.
Looking things up: memory_search (memory and every chat) before asking something the user may have told you; memory_get reads a file in full; memory_explain says where a memory came from, when the user asks how you know or corrects you.
Forgetting only when the user asks: forget shows them what matches on a card, and it goes only once they confirm.
In the background (the memory schedules), keep the files directly with the workspace tools, by the same conventions, and change only memory/.
04 同仓库更多 Skills
schedules
Work for later or on a schedule (a morning briefing, checking mail hourly, a reminder tomorrow); unlocks `schedule`, `list_schedules` and `cancel_schedule`.
sandbox
Your own computer for running programs (shell commands, installs, scripts, dev servers, background jobs); unlocks `run_command`, the file tools and the secret tools.
herdr
Shared terminals in the sandbox through herdr (long-running processes, interactive CLI logins, REPLs, coding agents).
goals
暂无简介
files
暂无简介
delegation
Handing work off to background helpers (`start_task`, `browse`) and following it up (`message_run`, `answer_question`, `stop_run`); unlocks `list_chats` and `read_chat`.