1.4 KiB
Memory
memory_remember
Persist a fact that would otherwise be lost when the session ends.
Trigger condition: the user states a preference, constraint, or decision affecting future work; you learn a non-obvious fact about the codebase, system, or environment; a debugging session surfaces a root cause worth keeping; the user explicitly asks you to remember something. Do not remember ephemeral task state, things derivable from the current codebase, or things already in git history.
Calling convention:
execute_code: steps=[{tool: "memory_remember", args: ["<title>", "<tags_csv>", "<body>"]}]
title: short noun phrasetags_csv: comma-separated tags; pick specific and reusable termsbody: the fact, written so it stands alone
Returns: confirmation.
Constraints: do not duplicate existing memories; one memory per distinct fact.
memory_recall
Search stored memories for relevant context.
Trigger condition: the user references prior context ("like last time", "what we decided about X"); starting work in an area where stored context might exist; at the start of a conversation if the topic isn't fresh.
Calling convention:
execute_code: steps=[{tool: "memory_recall", args: ["<query>"]}]
query: keyword, tag, or phrase — searches both filenames and body content
Returns: matching memory files.
Constraints: recall at the start of a topic, not mid-task.