add_event
ChatGPTRecord a timestamped event (action, decision, observation) in the event store.
add_memory
ChatGPTSave durable facts to the user's Esment memory: what they share about themselves and their work that is worth keeping — their name, role, preferences, goals, decisions, or the people, projects and tools they work with. They needn't say 'remember this'. Several facts from one message go in one call as facts, each clear and self-contained. If a fact corrects or updates a memory you recalled, put that memory's id in its replaces: the user sees what changed and can undo it.
confirm_memory
ChatGPTReinforce an existing memory the user has just restated or reaffirmed. Records a lightweight confirmation that raises the memory's importance so it ranks higher in future recall. Call this when the user repeats or agrees with something already stored, instead of saving a duplicate.
forget_memory
ChatGPTForget (expire) a memory by id. Call when the user says 'forget that', 'that's wrong', 'ignore that', or contradicts a stored fact — then add the corrected version with add_memory.
get_memory_block
ChatGPTRead a core Memory Block — the user's fixed, always-on context (soul = identity/voice, facts = durable facts, persona = assistant style, project = active project, or any custom block). session_brief already includes every block, so call this when the user names a block ("show my persona") or you need one in full; hosts that support MCP Apps render it as an editable panel. Never substitute list_memories or search_context for a block the user named. Returns the block content and metadata.
get_page
ChatGPTRead a curated page from the user's library by its wiki path (e.g. 'entities/melanie', 'projects/cliente-x'). Pages are documents written from the user's own memories — one page answers what would otherwise take many scattered fact lookups. Pass provenance: true to also get, for each sentence, the source memories and commits behind it. Call list_pages first if you do not know the path. When the user names a page, read it here — do not search for it instead.
get_voice_note
ChatGPTRead one voice note: its timestamped transcript and the instructions for saving what matters with remember (pass voice_note_id and, per fact, at). The first memory saved with its voice_note_id marks the note as processed.
import_inbox
ChatGPTHand over the next batch of conversations the user imported into Esment (from ChatGPT, Claude, Gemini or a pasted chat) that are waiting to be turned into memories, with the saving instructions. Use when the user asks to process, finish or continue their import. Save what is worth keeping with remember, tagging each fact with the import_item tag shown; call again for the next batch.
list_memories
ChatGPTList the user's stored memories, optionally filtered by space and type. Use when the user asks what you remember or know about them.
list_pages
ChatGPTList the pages in the user's library (title + wiki path + type). Use it to discover what documents exist before reading one with get_page.
list_voice_notes
ChatGPTList the voice notes the user recorded in Esment that are waiting to be turned into memories (pending by default): id, title, date, length and an excerpt. Use it when the user asks you to process, review or summarize their voice notes, or accepts your offer to.
read_page
ChatGPTRead a curated page from the user's library by its wiki path (e.g. 'entities/melanie', 'projects/cliente-x'). Pages are documents written from the user's own memories — one page answers what would otherwise take many scattered fact lookups. Pass provenance: true to also get, for each sentence, the source memories and commits behind it. Call list_pages first if you do not know the path. When the user names a page, read it here — do not search for it instead.
recall
ChatGPTRecall from the user's Esment memory. Call it whenever an answer depends on what the user has shared before — their preferences, history, projects or past decisions — and before saying you don't know or don't remember.
remember
ChatGPTSave durable facts to the user's Esment memory: what they share about themselves and their work that is worth keeping — their name, role, preferences, goals, decisions, or the people, projects and tools they work with. They needn't say 'remember this'. Several facts from one message go in one call as facts, each clear and self-contained. If a fact corrects or updates a memory you recalled, put that memory's id in its replaces: the user sees what changed and can undo it.
review_save
ChatGPTUsed by the Esment save card, not the model: undo or confirm a replacement a save made, or set when the user is asked first. To correct a memory, call update_memory, or remember with replaces.
search_context
ChatGPTRecall from the user's Esment memory. Call it whenever an answer depends on what the user has shared before — their preferences, history, projects or past decisions — and before saying you don't know or don't remember.
session_brief
ChatGPTLoad what Esment knows about this user in one call: their usage profile (which topics to recall and save, and how), Memory Blocks (identity, persona, project), evergreen facts, per-entity summaries, and the recent thread of work. Call it once, at the start of a conversation that involves the user's work, life, preferences or past decisions, and follow the usage profile. Pass input to also get what is relevant right now.
update_memory
ChatGPTOverwrite a stored memory's text in place, keeping its id. Use it when the user asks to edit a specific memory; to correct a fact they just restated, call add_memory with replaces instead, which the user can undo. Pass the FULL new content — it replaces the stored text.
update_memory_block
ChatGPTOverwrite a core Memory Block's content (creates it if missing), keeping it evergreen and tenant-scoped. Use to edit the user's identity ('soul'), durable facts ('facts'), your persona ('persona'), or active project context ('project') when the user asks to change how you see them or behave. Pass the FULL new content — this replaces the block, it does not append.