ChatGPT Plugin

Esment

Private AI memory

Brand: NotasAI

Category: AI
Primary Subcategory: Personal AI Memory & Second Brain

Integration details

Description

Esment gives ChatGPT persistent, inspectable memory for facts, preferences, decisions, and project context. It can recall relevant context, save durable information, update or forget memories, and read organized pages (created locally, not yet available in the cloud) and memory blocks belonging to the authenticated user.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: AI
Primary Subcategory: Personal AI Memory & Second Brain
Secondary Subcategories: None listed
Brand: NotasAI
Access: Account optional
First tracked: 2026-09-08
Tool count: 18
Geography: US

Agent DiscoverabilityChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Your score is coming

ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT Personal AI Memory & Second Brain

View Category

Listed in alphabetical order

Primary Subcategory

2MindComing soonGet notified

AI PassportComing soonGet notified

AI Whisper Voice Note TakerComing soonGet notified

AI WisebaseComing soonGet notified

AiAkiv MemoryComing soonGet notified

EsmentComing soonGet notified

Tools

18 tools agents can invoke

Record a timestamped event (action, decision, observation) in the event store.
Save 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.
Reinforce 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 (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.
Read 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.
Read 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.
Read 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.
List the user's stored memories, optionally filtered by space and type. Use when the user asks what you remember or know about them.
List 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 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 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 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.
Save 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.
Used 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`.
Recall 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.
Load 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.
Overwrite 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.
Overwrite 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.

FAQs

Esment ChatGPT Plugin FAQ

How the directory, categories and Discoverability Score work.

Read the methodology

How do I improve Esment's ChatGPT Plugin discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Esment alternatives on ChatGPT?

As of 2026-10-23, Esment competes with 2Mind, AI Passport, AI Whisper Voice Note Taker, AI Wisebase, AiAkiv Memory, Areta, AristAI Thinker, Arkon Vault and 100 more in ChatGPT Personal AI Memory & Second Brain, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.