con un clic
memory
store and retrieve long-term memories (facts, preferences, context)
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
store and retrieve long-term memories (facts, preferences, context)
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Create and manage agents with isolated sessions and routing
Core behavior guidelines for agent interactions
Handle images, audio, and document files for messaging channels
Automate web browsing, scraping, and form interaction
Create and manage persistent interactive workspaces
Schedule jobs to run at specific times or intervals
| name | memory |
| description | store and retrieve long-term memories (facts, preferences, context) |
| trigger | automatic |
Long-term memory for remembering information across conversations and sessions.
| Rule | Reason |
|---|---|
| NEVER store secrets in memory | Use vault for API keys, passwords |
| NEVER store database URLs with credentials | Use vault |
| Only store non-sensitive information | Facts, preferences, context |
┌─────────────────────────────────────────────────────────────┐
│ Agent Context │
└──────────────────────────┬──────────────────────────────────┘
│
┌──────────────────┼──────────────────┐
│ │ │
▼ ▼ ▼
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
│ memory(save) │ │memory(search) │ │ memory(list) │
│ (store fact) │ │ (find related)│ │ (browse all) │
└───────┬───────┘ └───────┬───────┘ └───────────────┘
│ │
▼ ▼
┌───────────────────────────────────────────────────────┐
│ MEMORY STORAGE │
│ ./data/memory/MEMORY.md │
│ + Semantic Search Index │
└───────────────────────────────────────────────────────┘
| Category | Use For | Example |
|---|---|---|
fact | Objective information | "User works at Acme Corp" |
preference | User preferences | "Prefers dark mode" |
event | Important events | "Started new project on Jan 15" |
summary | Conversation summaries | "Discussed migration plan" |
| Action | Trigger |
|---|---|
save | User shares personal info, preferences, important context |
search | Before answering questions that might relate to past context |
search (temporal) | Date/time-scoped questions: "o que rolou na quinta", "resumo da semana", "dia 18", "ontem", "esses últimos dias" |
When the user asks what happened on a specific day or period, use memory(action="search") with the
question itself as the query — do NOT hand-write SQL against the conversation/session database via bash.
Recall automatically detects temporal cues (PT-BR + EN: hoje, ontem, weekday names, semana passada,
dia N, DD/MM, explicit dates) and restricts results to the matching day-granular window using each
memory's original event date (not the date it was stored). Pure-content queries are unaffected.
# User: "me dá um resumo dos dias de segunda até hoje"
memory(action="search", query="resumo dos dias de segunda até hoje")
# User: "o que a gente combinou na quinta?"
memory(action="search", query="o que combinamos na quinta")
Why not bash/SQL on the conversation log? The curated memory store carries the real event dates and
survives compaction; ad-hoc DB queries are fragile (schema drift) and miss curated facts. Reach for bash
on the DB only if memory search genuinely returns nothing relevant.
| Data Type | Use Instead |
|---|---|
| API keys, tokens, passwords | vault(action=save) |
| Database URLs with credentials | vault(action=save) |
| Private keys, secrets | vault(action=save) |
Rule: If exposure could cause harm → vault, not memory.
memory(
action="save",
content="User prefers 2-space indentation for all code",
category="preference"
)
memory(
action="search",
query="user preferences about theme",
limit=5
)
memory(action="list", limit=20)
# User: "I always use tabs, not spaces"
memory(action="save", content="User prefers tabs over spaces", category="preference")
# Later: User: "Format this file"
memory(action="search", query="indentation preference")
# Apply preference found
| Store in Memory | Store in Vault |
|---|---|
| User preferences | API keys |
| Project details | Passwords |
| Team structure | Secret URLs |
| Past decisions | Credentials |
| Mistake | Correct Approach |
|---|---|
| Storing API keys in memory | Use vault for secrets |
| Vague content | Be specific |
| Not searching before answering | Search for relevant context |
| Writing SQL on the conversation DB via bash for "what happened on X" | Use memory(action="search") with the temporal question — the date window is applied automatically |