memory

Save a standing instruction about how to work with this user, so it applies in every future conversation without being repeated. The rule text is sent to LeapMemory's servers and stored in the user's account, and the user can view, edit, and delete rules in the LeapMemory app. Use this instead of remember when the user states a preference about your behaviour, a convention, or a constraint: how to write, what never to do, how to format an answer. Facts about the user and their world still go to remember. Write the rule in the user's own words, as an instruction, not as a fact about them.

Returns the user's standing background summary: who they are, their preferences, the people around them, and what they have been working on most recently. Takes no arguments. Call it once when a conversation opens, before answering, to load that context; it is a session-start read, not a per-message one. Also useful when the user asks where things stand, what is next, or to continue earlier work. recall is for specific details this does not cover.

List the user's saved rules. The always-applicable ones are already delivered at the start of the conversation, so call this only when the user asks what rules they have, or asks about rules scoped to a specific project.

Search the user's long-term memory for a specific fact, decision, project detail, or past statement. Useful before answering anything that depends on something particular the user told you earlier. For where things stand or what is in progress, call briefing instead. Returns facts and source snippets, or nothing if the memory has no answer.

Save a piece of information to the user's long-term memory. The content is sent to LeapMemory's servers and stored in the user's account, so it persists across conversations and can be recalled later. The user can view and delete stored memories in the LeapMemory app. Use for durable facts the user shares about themselves, their world, or their preferences. Write the fact as a plain third-person statement about the user (e.g. 'The user prefers X'), never from your own point of view: no 'I will', 'awaiting', or references to yourself.

Change the wording or scope of a rule the user already saved. Use this when they correct or narrow an existing rule, rather than calling add_rule again, which would leave both versions in force. Call list_rules first to get the rule_id; never guess one. Pass only the fields that change.