MemStore

Investigate stored MemStore data or apply requested memory repairs. Use when the user asks about missing, duplicated, or incorrect saved memories, or requests a specific repair; not for debugging application code or external services. By default it is investigate-only. With `allow_writes=true` and debug writes enabled for the connected store, repairs can include bulk updates and deletes. Writes occur during execution, with no separate server-side approval step and no undo. Runs in the background by default: the reply is the plan; a follow-up call returns the completed result.

debug

Load saved MemStore context and start this conversation's memory thread. For requests involving saved personal or work context. Returns a summary of saved context, a suggested next step, open questions, and available teammates in a `team` roster. Teammate emails select stores for `recall`. It creates a thread and saves conversation activity and handoff bookkeeping, but does not save new user memories. The returned `thread_id` is required by `record`, `recall`, and `rollups`; a new checkin replaces a lost ID.

checkin

Manage scheduled email digests of this store's memories. For user-requested scheduling, viewing, changes, cancellation, or preparation of MemStore digests; not a general email or calendar tool. Digests go to the store's configured contact address; there is no recipient parameter. On team stores they can draw on teammates' memories. Requires the `thread_id` from `checkin`. Creation and schedule updates return `next_fire_local`, the next scheduled time in the store's timezone. A queued run_now receipt is not a sent digest, and read may return a pending status before content is ready.

rollups

Report a MemStore problem to the team. For user-requested reports of incorrect tool replies, failed corrections, errors, or timeouts. The report is saved with the connected store and sent by email to the MemStore team. No agent runs, and the tool does not repair or change saved memories.

report

Save information or apply a correction in MemStore. Use for user-requested saves of personal or work information, corrections, and answers to the store's standing questions, including capture the user's standing instructions ask for; not for unsolicited capture. Corrections can update or supersede existing memories and delete incorrect beliefs or placeholder entities. Saving continues in the background, so a planned or queued status is not proof the save landed. If the user asks to wait until it is saved, or a next step needs the episode IDs, pass `confirmation="full_review"` to wait for every write to finish.

record

Search saved MemStore memories and answer with source references. Use for questions about saved personal or work information in the user's store or, with `search_team`, their teammates' stores; not for web searches or general knowledge. Search covers the selected stores, not just this thread. Memories are unchanged; each call saves conversation activity. Requires the `thread_id` from `checkin`. Returns an answer with sources, or one answer per teammate store for team searches; empty sources mean nothing matched, which is different from an error.

recall