“Why does it think that?”
A memory without a source is hard to trust.
See the evidencePersonal context. On your terms.
Inspect it. Correct it. Take it anywhere.
Turn your chats, notes, and work history into memory you can review. Give your assistant the right context, and keep the rest to yourself.
Work space
You
What should I focus on this week?
PersonaKit4 memories shared
Make room for the work that moves things forward.
Every read is saved to your history: which assistant asked, when, and exactly which memories it received.
No account connected
For the AI tools you already use
Your reviewed context, across assistants and agents. Explore compatibility ↗
The missing piece
Your context changes. Your tools change.
You should have a say in what follows you.
A memory without a source is hard to trust.
See the evidenceAn old project or passing preference shouldn’t define you forever.
Keep context currentSwitching assistants shouldn’t mean explaining yourself from scratch.
Take your memory with youNothing about you, without you
Open any memory and see where it came from. Correct the interpretation. Decide where it belongs.
Try a decision. It resets when you reload.
Why PersonaKit thinks this
“Skip the pep talk. Give me the practical next step.”
“If you disagree, tell me why.”
From your history to your next hello
Start with a chat export, notes, or work history you choose.
Check what PersonaKit learned, in groups or one by one. Anything you skip can still be used, marked as not yet checked.
Start with an MCP-compatible pilot or bring a reviewed Markdown export.
Get relevant context with sources and a record of what was shared.
Built to grow with you
At first it checks with you. As it learns what you keep and what you correct, it asks less, and still asks when something needs your judgment.
The PersonaKit principle
Your store, in an account you own.Your sources, attached to your memories.Your choice, every time context travels.
Your context goes with you
Take your memory to any assistant.
Connect it, or export a copy.
Connect an MCP-compatible assistant to the memories you choose to share.
We’ll guide you through setup
Guided MCP setup for your coding workflow, including other CLI tools with MCP support.
We’ll check your tool’s compatibility
Bring a chat export from ChatGPT, Gemini or Claude today. Direct connectors for ChatGPT and Gemini are planned.
You choose what to upload
Start from exported chats or assistant history you choose to share. Supported imports include Hermes session exports.
New chats? Import a fresh export.
Review a memory pack with source quotes before sharing it with another tool.
Markdown (.md) · example memories. Open in any text editor; no signup needed.
Shared files won’t update when you change your memories or permissions.
Choose a prompt. Read an example answer right here.
Example answer
Make room for the work that moves things forward.
You prefer a short, practical plan. Start here.
Work only
View in the product demo ↑Example answer
Directly, and with a next step.
That comes from two things you said, in July and August.
Work only
Example answer
Two memories stayed back for this question.
I know they exist, but I never received what they say.
2 withheld · Work planning
See what was withheld ↑Example answer
Public writing needs its own permission check.
No personal draft generated: public-use context is withheld.
0 shared · 6 withheld · Public writing
Example history
Every read is saved to your history.
You can see which assistant asked, when, and exactly which memories it received.
PersonaKit is a personal AI memory control layer for people who use AI every day. It turns selected chats, notes, and work history into source-backed memories you can review, correct, restrict, and export to the assistants you already use.
The private pilot starts with guided setup. The memories shown on this page are examples.
PersonaKit is designed to keep your memory store and read log in an account you own. Processing services handle the context needed for a request.
This website cannot access your personal memory. Before you share a source, we’ll explain the storage setup, providers, and what they can access.
No. PersonaKit’s policy is not to train models on your conversations.
Connected assistants and processing providers have their own terms and settings. We review those with you during setup before you share a source.
Review decisions let you edit, restrict, or reject records. Restrictions affect future PersonaKit reads. A previous export or an assistant’s existing conversation cannot be recalled by changing a record.
No. Anything you skip can still be used and is marked as not yet checked. Today, only you can confirm a memory. Over time we aim to ask you less, by learning from what you keep and correct. If PersonaKit ever starts confirming routine memories for you, we’ll tell you first and you’ll be able to turn it off.
No. Capture depends on the integration and what you choose to share. A connector is not automatic access to your entire conversation history. The pilot will make the boundary visible for your setup.
The memories shown on this page are examples, and the answers are scripted. Exploring the demo makes no model calls and does not connect your accounts. The private pilot starts with guided setup. The waitlist form is a local preview; it does not submit details, download a draft, or reserve a place.
An assistant by PersonaKit
Trinity is the assistant that uses your memory. It learns how you work, gets the groundwork done before you ask, and checks with you before anything leaves your hands. Invitation only.
Early access. A personal invitation.
A small group at a time, for PersonaKit memory and for Trinity.
We’re getting ready to welcome you. For now, the form is a preview - not a signup.
Early access
Join the waitlist. We’ll be in touch when early access is ready.