What is AI Passport and how does it work
AI Passport keeps selected personal context available across permitted AI tools. Learn how reviewed memories and app access work, with a simple first example.
AI Passport keeps selected personal context available to the AI tools you permit. It gives you a place to review what should be remembered and decide which connected assistants can use it.
It is useful when you keep explaining the same thing to different tools. You may have told ChatGPT how you like work emails written, then found yourself giving Claude the same instructions a week later.
What does Passport actually hold?
A memory can be a preference or a detail you expect to use again. For example, you might want an assistant to know that a workshop proposal is aimed at first-time volunteers.
That is different from keeping every sentence of the conversation where the proposal was discussed. An early idea may have been rejected. A budget may still be provisional. A short memory should preserve the distinction.
The useful statement might be “The workshop is for first-time volunteers. The venue is still undecided.” If an assistant rewrites that as a confirmed event at a particular venue, you should correct it before approval.
How does a memory become available?
In Passport’s normal review flow, a connected assistant proposes a memory. It appears in your private Inbox for you to check.
You can approve the statement when it is accurate. If the assistant has drawn the wrong conclusion, edit or reject it.
An app then needs the relevant permission to read approved context. Passport calls this a pass. Access is tied to the particular app and category, with a purpose and duration. You can inspect those choices and revoke access.
Some category access can be established during the assistant’s connection flow. Read that consent screen carefully. Approving a memory later does not itself grant every app permission to use it.
How is this different from ChatGPT’s memory?
ChatGPT’s native memory is part of ChatGPT. Claude has its own memory features. Passport is a separate context service that supported assistants can connect to.
Suppose you save a preference in Passport asking for British spelling in work emails. A permitted ChatGPT connection can retrieve it. A permitted Claude connection can retrieve the same approved preference.
You do not need to recreate that statement in each assistant’s native memory. You do still need a working connection and the appropriate access.
Be explicit when saving. “Remember this” may refer to the assistant’s built-in memory. “Save this to AI Passport” makes the destination clearer. Check that the proposal actually appears in Passport.
Does it import all my conversations?
Connecting an assistant does not automatically combine its conversation history with another service’s history.
Bring in the context you want through an available save or import workflow. Review the result before relying on it. An old conversation can contain information that is no longer true, even if every sentence was recorded accurately.
Passport’s core role is carrying context. Use a connected assistant for the task you want that context to help with.
What about documents and connected apps?
An approved memory is a selected statement. An original document contains its source material. A live app connection can provide current information from another service.
These do different jobs. A preference for afternoon appointments can be remembered. Whether next Thursday afternoon is free requires current calendar information.
Source access has separate permission boundaries. Saving a document or approving a suggestion from it does not automatically authorise an assistant to read the original. Linking a calendar also does not grant every connected assistant access to it.
What should you try first?
Choose one preference that regularly improves an answer. Save it through a connected assistant, review the wording and retrieve it in a fresh conversation.
If you use another supported assistant, connect it to the same Passport and repeat the retrieval. You should be able to identify which statement travelled and why the receiving app could read it.
Keep the context accurate as your circumstances change. A persistent memory should not turn a temporary situation into a permanent description of you.
Revoking a pass controls future reads under that pass. It cannot remove information already delivered into another service’s conversation, so manage those copies separately when needed.