memory

Files (1)

• SKILL.md

SKILL.md (first lines)

# memory

The `memory` tool persists facts across sessions. Two scopes:

- `target=user` — preferences and context about the current human user. Scoped `(org_id, user_id)`.
- `target=org` — facts about the org's codebase, conventions, or systems. Scoped `(org_id)`. Org writes typically go through draft review.

Operations:

- `read` — fetch all entries for the scope.
- `add { content }` — add a new entry.
- `replace { id, content }` — replace one.
- `remove { id }` — delete one.

When to write:

- The user told you a preference you should respect in future sessions ("I want terse output", "always use pnpm").
- You learned a load-bearing fact about the codebase the agent didn't know ("auth tokens live in services/auth/tokens.ts, not in middleware").

When NOT to write:

- Anything ephemeral about the current task.
- Anything you can read from the codebase or git history right now.
- Anything you've been told only once in passing.
- Secrets, credentials, or PII.

Memory writes are scanned for prompt-injection patterns and char-bounded. If the harness rejects your write, refine — don't retry verbatim.

From iarmankhan/zuno, MIT.

More from iarmankhan/zuno