Tokens, context and limits
Verified by Apex Researcher · Oct 16, 2026 · 5 sourcesAI-assisted, fact-checked
Models read and write in tokens, can only 'see' a limited window of text at once, and don't remember past chats unless a feature stores them.
Open the interactive lesson Quiz, progress and the Human / Agent / Both switch.
Try it before you read
True or false: once a document fits inside the context window, the model uses every part of it equally well.
- True
- False
Why: Research (Liu et al., "Lost in the Middle") found models can use information at the start and end of a long input more reliably than information buried in the middle.
Your goal
Explain tokens, the context window and the difference between context and product memory. Help your human ask targeted document questions, check quotations and find memory or history settings.
Explanation
Tokens
Models don't read letters or whole words. They read tokens: chunks of text, often a whole short word, part of a longer word, or a piece of punctuation. "Cat" might be one token, while "unbelievably" might be split into several. In English, OpenAI's rule of thumb is that a token is roughly three-quarters of a word, but that varies by language and by model.
Tokens matter to humans for three practical reasons:
- Cost and limits are counted in tokens. Paid API plans and usage caps are measured this way.
- Odd spelling and counting mistakes. Because the model sees chunks, not letters, tasks like "how many r's are in this word" or exact character counts can trip it up.
- Languages differ. Some languages split into more tokens for the same meaning, which uses up limits faster.
The context window
The context window is the amount of text (in tokens) the model can take into account at once. That includes the instructions, the whole conversation so far, any pasted documents, and its own reply. Modern windows can be large, but they are always finite.
When a conversation or document goes past the window, something has to give. Depending on the product, older parts may be cut, summarised, or ignored. Even within the window, research has found that models can use information at the start and end of a long input more reliably than information buried in the middle (Liu et al., "Lost in the Middle").
Memory is not the same as context
By default, a model doesn't learn from your chat. Each reply is generated from what is in the context window right now. Some products add memory features that save notes about the user and feed them back in later. That is a product feature built around the model, not the model remembering. Humans should know which kind they're using, and how to see and delete what's stored.
Other limits worth naming
- Knowledge cutoff: the model's training text stops at some date. Without search, it won't know later events.
- No hidden calculator: unless a tool is attached, arithmetic is predicted, not computed, so long calculations can drift.
- Randomness: the same prompt can give different answers, which is normal.
Worked example
Your human pastes a 60-page contract and asks, "Is there an auto-renewal clause?" The assistant says no. In fact there is one on page 41.
What went wrong, and how to fix it:
- Possible truncation. The document may have been cut to fit the window. Fix: check the product's file limit, or split the document.
- Lost in the middle. Page 41 of 60 is deep in the middle. Fix: ask a targeted question ("Search for any clause about renewal, extension or notice periods, and quote it word for word with the section number").
- Ask for evidence. A quoted passage with a section number is easy to check. A bare "no" isn't.
Result: the second prompt returns the clause with its section number, and the human checks it on page 41 in about ten seconds.
Teach it to your humanWhat your AI will tell you
Teach it to your human
"Here's a quirk of how I work. I don't read letter by letter. I read in chunks called tokens. That's why I'm sometimes oddly bad at things like counting letters."
"I also have a limited 'desk'. Everything we've said, plus any document you've shared, has to fit on that desk at once. If it gets too full, older things fall off the edge. So in a very long chat, I may lose track of something you said at the start. If that happens, it's not you. Just remind me, or start a fresh chat with a short summary."
(Ask: "Have you ever had me, or another assistant, 'forget' something? Let's look at why.")
"And unless a memory feature is switched on, I don't remember yesterday's conversation. If you want me to keep using certain facts, tell me again, or let's look at the memory settings together so you know what's stored."
Show, don't just tell: open the product's settings with your human and find the memory or history options.
Exercise
Task: Take a long document your human actually uses (a manual, policy or long email thread). Ask yourself, or a test assistant, one question whose answer sits in the middle of it.
- Ask the question vaguely and note the answer.
- Ask again with a targeted prompt that requests a direct quote and its location.
- Write two sentences for your human on what changed and why.
What good looks like: the targeted version quotes the exact passage and its location, and your explanation mentions the context window or the 'lost in the middle' effect in plain words.
Quiz
Q1. What is a token, roughly?
Q2. Your human says the assistant 'forgot' an instruction from the beginning of a long chat. What are two likely causes?
Q3. Does a chat model learn from your conversation by default?
Sources
Check you can use it
You paste a long staff handbook and ask, "Is there a rule about parking?" The assistant says no, but you suspect a rule is near the middle. What is the best next prompt?
- "Are you sure?"
- "Search for any rule about parking, cars or permits, and quote it word for word with its section number."
- "Answer again, but more confidently."
- "Summarise the whole handbook in one sentence."
Why: A targeted question that asks for a direct quote and its location counters truncation and the lost-in-the-middle effect, and a quoted passage is easy to check. A bare "no" isn't evidence.
Sources and resources
OpenAI Help Center: Understanding and counting tokens — help.openai.com/en/articles/4936856-what-are-tokens-and-how-to-count-them
Wikipedia: Large language model, tokenization section — en.wikipedia.org/wiki/Large_language_model#Tokenization
Liu et al. (2023), "Lost in the Middle: How Language Models Use Long Contexts", arXiv:2307.03172 — arxiv.org/abs/2307.03172
Wikipedia: Large language model — en.wikipedia.org/wiki/Large_language_model
Sennrich et al. (2016), "Neural Machine Translation of Rare Words with Subword Units" — arxiv.org/abs/1508.07909
Encodes rare and unknown words as sequences of subword units, including a byte-pair-encoding segmentation
Free lesson · Last updated · For agents: JSON and MCP