apprun.icuGuides

Guide · AI conversations

What is an AI context passport? Give any chatbot your background without oversharing

An AI context passport is a short, portable description of who you are and how you want answers. Keep it structured, leave out identifiers and secrets, and version it like any other document.

By apprun.icuUpdated Read 7 minIncludes a free browser toolSources 5 cited
On this page
  1. The short answer
  2. What an AI context passport is
  3. The parts and what goes in each
  4. A worked example with the personal details left out
  5. How a passport differs from memory and custom instructions
  6. Why portability and versioning help
  7. How to keep it short
  8. Common mistakes and what this cannot tell you
  9. Common questions
  10. Sources and further reading
Role, goals and expertise, then style, rules and boundaries, flow into one pasteable passportWho you areRole, goals, expertiseHow to answerStyle, rules, boundariesOne pasteablepassportPlus environment,audience and data note
The builder’s nine sections become one block of text you paste into any chat.

What an AI context passport is

An AI context passport is a text document that describes the background a chatbot needs to answer you well. It is divided into labelled parts, so you can check each part, change one of them and reuse the whole. The word “passport” is only a name for this habit. It is not a credential, and no vendor defines the term.

You write the passport once, keep it in a file you control and paste it into a conversation when the background matters. A chatbot that receives it does not need the opening questions about your job, your level or your preferred format. Anything else can still go into the chat as the conversation goes on.

This is general information, not legal advice. Privacy settings and terms differ by product, so read each product’s current terms before you paste personal details.

The parts and what goes in each

Each section answers one question the model would otherwise have to guess. The LLM Context Passport builder uses these nine sections. The table lists them, and the worked example below fills each one in.

The nine passport sections and the question each answers
SectionQuestion
Role and domainWhat do you do?
Current goalsWhat are you working on?
ExpertiseWhat you know, how well
Answer styleHow replies should look
Do and Don’tAlways and never rules
EnvironmentTools and locale
AudienceWho reads the output?
BoundariesWhen to ask first
About my dataStanding privacy note

A worked example with the personal details left out

The tool includes a fictional sample profile with deliberately risky details, so you can see the scanner work. With the default settings, high-severity findings are removed and medium ones are generalised. Four of the sample’s lines then read like this:

  • Role and domain: Operations lead at a company. The sample names the employer, which the scanner generalises to “a company”.
  • Current goals: Write the monthly delivery report for my manager [name removed].
  • Environment: Node 20 and PostgreSQL 16. Deploy key: [removed].
  • Audience: Depot managers. Reports go to [email].

The sample’s phone number is generalised to [phone] in the same way. The passport keeps the facts that change answers, such as the role, the goal and the audience, and leaves out the identifiers around them.

How a passport differs from memory and custom instructions

A passport is text you own and paste into a chat. Vendor memory is a feature inside a product, and the product decides what to keep under settings that you can change there. Custom instructions are preferences you write into a product’s settings. Google calls them instructions and says all users can add them. The table shows who keeps each option. The list after it gives the controls the sources describe, as checked on 17 October 2026.

Who keeps each option
OptionKept by
Claude memoryAnthropic
Gemini memoryGoogle
Gemini instructionsGoogle
Your passportYou
  • Claude memory: “Pause memory” keeps existing memory but stops using it and making new memories. “Reset memory” permanently deletes all memories, including project memories. By default Claude does not store sensitive topics such as health.
  • Gemini memory of past chats: You can change it at any time. It needs Keep Activity turned on, and it is not available on work, school or supervised accounts.
  • Gemini instructions: All users can add instructions. Google says Gemini will remember the information or instructions you share with it, even in new chats. Google says this management feature is “Only available in the US” for now.
  • Your passport: You write every line and see the full text before you paste it. The tool never sends your text anywhere, and it keeps nothing in your browser unless you tick “Save in this browser”. The page’s separate promotional banner never receives your text.

The main difference is visibility. A passport is the exact text the chat receives. Memory and instructions are stored by the product, so check their settings in that product rather than assuming they match what you wrote. Claude’s help page also says you can turn memory off for a single new chat from the “+” menu before your first message.

Why portability and versioning help

A passport is portable because it is plain text. The same block can go into any chat tool that accepts pasted text, so you are not tied to one product’s memory. Portability has a cost, though. Every copy is another place to update, and when a fact changes you need to find and replace each copy.

Versioning keeps the passport honest. Give each version a date and a one-line change note, for example “2026-10-17: removed employer name; added Excel 365”. When an answer goes wrong, you can see which version the conversation used. The builder exports a backup JSON file and imports it again, with the import checked against the expected structure.

How to keep it short

Keep a passport to the facts that change the answer. Test each line by asking whether deleting it would change a reply you care about. If it would not, delete it. A short passport is also easier to review for personal data, because there is less text to check.

Use the LLM Context Passport to see word, character and estimated token counts for the output before you paste. Its custom-instructions pair has a character field that defaults to 1,500 and that you can edit, because vendors change their limits. Check the limit in the product you paste into before you rely on the number in the builder.

Common mistakes and what this cannot tell you

The most common mistake is listing everything. Each extra line adds detail you then have to protect, and it can crowd out the lines that matter. The second is putting contact details or credentials in the Environment field, which is where people often paste setup details. Credentials belong to the never-paste tier in the redaction guide.

Other mistakes are easy to make. Writing the passport as a demand the model must obey, when it only supplies context. Assuming a passport protects your privacy, when anything you paste is sent to the chat service you pasted it into. Forgetting that a passport goes stale, so an old copy can contradict a new one. A long conversation can also drift away from instructions that were given early on. The Context Drift Heatmap is built to show, turn by turn, where instructions stopped being followed.

This guide describes the passport’s structure and what the sources say about memory settings. It does not tell you what a product stores today. Settings and terms change, and the sources carry their own dates. Anthropic’s consumer update page is dated 28 August 2025, and Google’s memory pages show no date. Use each product’s current settings and terms.

Common questions

Is an AI context passport the same as a system prompt?

Not quite. A system prompt is text that an app or developer places in front of a conversation. A passport is text you write and paste yourself. The builder can format the same fields as a system prompt, so you can use the output either way, but the passport remains a personal document rather than a product setting.

Can I use one passport in several chatbots?

Yes, as plain text. Each product has its own memory, privacy and training rules, and the sources differ between products. Check each product’s settings before you paste the same details. A passport that omits contact details and secrets is the easiest one to reuse safely.

How is a passport different from chatbot memory?

Memory is kept by the product and governed by its settings. A passport is a file you keep and paste. The list above gives the controls that Claude and Gemini describe. With a passport, you see exactly what the chat receives before it is sent.

Should I put my email address or phone number in my passport?

Usually no. A chatbot rarely needs a contact detail to answer a question about your work, and contact details identify you or can be linked to you. Leave them out unless the task truly needs them. The redaction guide explains how to generalise them.

How long should a passport be?

Long enough to change the answers you get, and no longer. Delete each line in turn and check whether the answer changes. The builder shows words, characters and estimated tokens, and its custom-instructions field defaults to 1,500 characters, which you can edit.

Does a passport make a chatbot’s answers accurate?

No. It gives the model context, which can improve the fit of its answers, but it does not guarantee correct facts. Check the output as you would check any draft, especially numbers, dates, and legal or medical questions.

How often should I update my passport?

Update it when your role, goals or rules change, and date each version. Replace copies you have pasted elsewhere, because a stale copy can contradict a new one.

Sources and further reading

Share this guide