ChatGPT makes a request. Mnemara checks it on your Mac. The memory vault is local; permitted information travels back to the AI.
Demonstrated: ChatGPT + Mac. Phone approvals, cloud storage and broader client compatibility are planned.
Where things live
A bridge to your memory. Not another cloud vault.
The Model Context Protocol (MCP) lets AI tools call external services. In this prototype, a paired relay carries requests between ChatGPT and your Mac. It does not host the memory vault.
ChatGPT + Mnemara connectorThe AI sends a memory request.
↕
MCP relayTransport and pairing—not the memory vault.
↕
Your Mac initiates the connection. Approved results return through the relay.
Your Mac
Outbound bridgeRoutes relay requests to the Companion.
↕
Mnemara CompanionRetrieval, policy checks and approved writes.
↕
Encrypted local vaultMemories, revisions and local records.
Local owner API ↔ native Mac appUses the same local vault state for notifications, approvals, memory review and activity.
Your Mac must remain online.
Current prototype, not a future cloud design. Arrows show request/result or local-service interactions; they do not imply end-to-end encryption through the relay.
The vault stays on your Mac. Approved information doesn’t.
The native app depends on a local owner API/dashboard service. That service must run, but its browser dashboard does not need to be open. The Companion and outbound bridge are separate prototype processes.
Two different decisions
Keeping a memory. Sharing a memory.
Recall
The AI asks Mnemara for relevant saved information.
The Companion retrieves candidates and checks disclosure policy.
A protected result is withheld while the owner reviews the request.
After approval, the AI retries the request and receives the permitted result.
The model uses that result in its active context to answer. It may also decline a tool call or require its own consent.
Save or update
The AI proposes a durable fact, preference, decision or correction.
Mnemara checks local policy. Hard never-store rules take precedence over model suggestions.
The owner reviews an approval-gated candidate in Mnemara.
Approval commits the exact candidate locally, with record and revision history.
In the current flow, a locally approved write completes without another ChatGPT “continue” message.
Memory is not the whole conversation
Different information. Working together.
The app or agent around the model assembles what it can use for a response. Mnemara supplies permitted long-term memory; it does not replace the model’s instructions or every project connection.
Example: preparing for an investor meeting.
Part
Purpose and example
Core instructions
How the assistant operates. “Ask before sending anything to another person.”
Active context / short-term memory
Information available for this response: the current request, relevant conversation, instructions and any retrieved material. “Tomorrow’s meeting is 30 minutes.”
Personal profile / long-term memory
Who you are and how you like to work. “I prefer direct, practical explanations.”
Experience and decisions / long-term memory
What happened and what you learned. “Last time the deck had too much text. Lead with the demonstration.”
Project knowledge
The detailed work: the current deck, value proposition and financial forecasts in files or an Obsidian vault.
Personal profile and remembered experience are parts of long-term memory. These categories describe purpose, not exclusive storage locations. A lesson can also exist in a project note.
Where does RAG fit?
Retrieval-augmented generation (RAG) means finding relevant information and bringing it into the model’s context to help answer. It can retrieve project documents or long-term memories. It is a technique—not the entire memory framework. Mnemara can use retrieval techniques while also governing storage, revisions and disclosure.
What about Obsidian and other knowledge tools?
Obsidian can hold lifelong personal knowledge, decisions and project material. Mnemara’s focus is the owner-facing memory and permission experience, not replacing that library. A future connector would need its own scoped access and provenance. An Obsidian integration is not demonstrated or shipping today.
Being honest about the limitations
Local storage isn’t the same as local AI.
Shared information reaches the provider. Approved results pass through the relay to ChatGPT. The relay is a transport service, not the vault; that does not make it invisible to the data flow.
Turning off native memory is not a retention guarantee. Providers may retain conversations or process information under their own settings and terms. Mnemara does not erase earlier chats or control information you share directly.
Pause stops future access. It cannot pull back information already disclosed.
Compatibility must be proven. Provider consent, tool behaviour and available connectors can differ between products and clients. Storing memory independently does not automatically make every integration work.
Proof and next steps
A working prototype. Not a finished promise.
Demonstrated with synthetic data
Fresh-chat recall from the local encrypted vault.
Sensitive disclosure held for owner approval.
New memories and corrections committed after approval.
Native Mac notifications and owner review.
Memory, revision and activity views; pause/resume sharing.
Still to build or validate
Simpler installation and reliable service recovery.
Stronger natural-language recall and classification.
Live policy editing and native memory edit/delete controls: current UI controls are previews.
Broader supported integrations and device access.
Phone approvals, optional cloud storage and sync.
Production security assurance and operational hardening.
Approval-gated corrections through ChatGPT work; that is separate from the unwired native Edit/Delete controls. No independent security certification is claimed.
The bigger picture
Your memory follows you. You decide what each tool may use.
That is the direction. The first proof is deliberately narrow: one supported AI connection, a local vault, and an owner who has a say.