MemStore

Investigate or repair missing, duplicate, or incorrect MemStore memories. Use for saved data, not application code. Default investigations keep memories unchanged and run in the background. Use a follow-up call for findings. With `allow_writes=true`, return a proposal of exact changes to each affected memory. This requires debug writes, which are off by default and enabled by the store owner in the dashboard settings. Proposals can include bulk updates and deletes. Show the changes to the user. After approval, call `debug(confirm=<proposal_id>)` to apply that proposal once. Confirmed repairs have no undo. Proposal and confirmation calls wait for the complete result.

debug

Load saved MemStore context and start a memory thread. For saved personal or work context. Returns a summary and a `team` roster; teammate emails select stores for `recall`. Questions that need the user's input appear in three fields: - `unresolved`: question text selected for the current task. - `asks`: question IDs and prompts for saving answers through `record.answers`. - `review`: total items awaiting the user's review and a link to the full list. `thread_id` is required by `record`, `recall`, and `rollups`. Reuse it for the current task. A new checkin is recommended when the user's intent or task changes. It starts a fresh thread. Check in again if the ID is lost. Saved memories stay unchanged. MemStore logs this call's inputs, caller identifiers, result summary, and status on the thread. It does not record the surrounding conversation.

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. Use for user-requested reports of incorrect replies, failed corrections, errors, or timeouts. MemStore saves the report with the connected store. When email notifications are configured and enabled, it also attempts to notify the team. `report_id` identifies the saved report. `notified` states whether the email service accepted the notification. Saved memories stay unchanged.

report

Save information or apply a correction in MemStore. Use for user-requested saves, corrections, or answers to standing questions. Applicable standing instructions can also authorize a save. Corrections can update, supersede, or retract memories. MemStore retains the accepted content and processes the save in the background. `processing` means the save is underway. `recorded` means the episode writes are complete. Use `confirmation="full_review"` when the user asks to wait or a next step needs episode IDs. MemStore logs this call's selected inputs, result summary, and status on the thread.

record

Search saved personal or work memories, not web or general knowledge. `search_team` selects teammates. Returns an answer with sources per store. Empty sources mean no matching source was found. Requires the `thread_id` from `checkin`. Personal recall includes `pending`, with relevant open Review questions. Use `record.answers` with each `decision:<id>` and its `answer` format. Team results do not include Review questions. Saved memories stay unchanged. MemStore logs this call's inputs, result summary, and status on the thread; it does not record the surrounding conversation. It also keeps unanswered questions for follow-up. Team call summaries contain member names, emails, and statuses; answers and sources stay in the response.

recall