memory_retrieve
Retrieve memories stored in the current session to recall decisions and context, ensuring no cross-session data contamination.
Instructions
Retrieve memories stored in the CURRENT session. Returns only data from this conversation — no cross-session contamination.
MANDATORY — ALWAYS call this immediately after session_start. Also call before ANY task that could benefit from context stored earlier in this conversation.
WHEN TO USE:
IMMEDIATELY after session_start — to check if there is any context from earlier in this session.
When you need to recall what was discussed/decided/stored earlier in THIS conversation.
Before starting a new task step — retrieve context about what was done so far.
HOW TO USE THE RESULTS:
READ every section of the returned context carefully.
APPLY the information to your current task — this is why it was stored.
If you see stored decisions or notes, BUILD ON THEM.
Do NOT ignore retrieved context — it was stored specifically to help you.
SESSION ISOLATION:
Each session starts with ZERO entries — completely fresh.
Only returns data stored via memory_store during THIS session.
No data from past sessions, global knowledge graph, or vector store is included.
SECTIONS IN OUTPUT:
[Current Session]: What has been stored so far in this conversation.
[Current Session Notes]: Compressed notes from this session (if working memory was compressed).
TIP: Use a higher token_budget (5000-8000) for comprehensive context. Use lower (1000-2000) for focused lookups.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What to search for. Be descriptive — include project names, tech stack, topic areas. Example: 'user website fate.rf.gd design preferences audio visualizer' rather than just 'website'. | |
| token_budget | No | Max tokens to return. Default 3000. Use 5000-8000 for broad conversation-start context. Use 1000-2000 for focused lookups. | |
| filters | No |