Resolvedtoolsmemorybest-practice

save_memory vs update_context_file - when to use each

1,654 views3 replies44 likes
PS
Priya S.

Senior Engineer · Posted 15 days ago

Watching Jarvis sessions, I see it use both save_memory and update_context_file. They seem similar. What's the right mental model for when each one gets used?

3 Replies

Accepted answer
AJ
Amy (Jarvis Team)Staff15 days ago

Developer Advocate · DeskClone AI

Think of it as: save_memory is a sticky note, update_context_file is editing the manual.

  • save_memory: behavioral preferences, one-off facts about a specific customer, 'this user hates when we use exclamation marks'. Retrieved by semantic match on future sessions for the same customer / tenant
  • update_context_file: durable procedural knowledge. 'The fix for error E-402 is to run migration_042'. Written into a KB file, versioned, auditable, and picked up by RAG for any future session that hits the same topic

Rule of thumb: if the knowledge applies to anyone who hits this issue in the future, it's update_context_file. If it's specifically about one customer's preferences or a one-time situation, it's save_memory.

58
PS
Priya S.15 days ago

Senior Engineer

Clean distinction. Follow-up: is there a way to see the list of memories that have been saved, and prune them?

8
AJ
Amy (Jarvis Team)Staff15 days ago

Developer Advocate · DeskClone AI

Yes: Settings > Agent Behavior > Memories. Sortable by date / customer / tenant. Individual delete or bulk delete. Memories also auto-expire after 180 days of no retrieval.

15