Expand description
The two tools the model sees.
Memory reaches the model through function calls rather than injected context, for three reasons: the model’s use of a memory is visible in the transcript, retrieved text is unambiguously data rather than instruction, and nothing is spent on turns that never needed memory at all.
Both are TypedTools over argument structs, so the JSON Schema the model
is constrained by is generated from the types the handler actually decodes.
manage_memory’s operation is the domain’s own MutationIntent, which
means the tool contract and the ledger cannot disagree about what operations
exist.
Structs§
- Manage
Args - Arguments to
manage_memory. - Recall
Args - Arguments to
recall_context.
Enums§
- Recall
Scope - Which slice of memory a recall should search.
Constants§
- MANAGE_
DESCRIPTION - The management tool’s description.
- MANAGE_
TOOL - The memory-management tool’s name.
- MEMORY_
TOOLS - Every tool the memory subsystem installs.
- RECALL_
DESCRIPTION - The recall tool’s description.
- RECALL_
TOOL - The recall tool’s name.
Functions§
- manage_
memory_ tool - Build the
manage_memorytool for a session. - recall_
context_ tool - Build the
recall_contexttool for a session.