What does a model's 'context window' mean and what does it include?

**The context window** is the maximum total number of tokens a model can handle in one API call. It is measured in tokens, not in characters or words. The most important thing to understand is what counts against that budget. Everything counts. The system prompt counts. The user's current message counts. The full conversation history (every prior turn) counts. Any retrieved documents you injected for RAG count. Any tool-call results count. And critically, the model's own reply also counts. So when Claude Opus 4.7 or Gemini 3.1 advertise a 1M-token context window, that does not mean you can send a 1M-token prompt. It means the input and the output combined must fit under 1M tokens. If your input is already 999,000 tokens, the model has only 1,000 tokens of room to reply. The practical consequence: you have to budget context. Long conversations need history compression. RAG pipelines need to limit retrieved chunks. Long documents need chunking or summarization. The window is a hard ceiling.

**The context window** is a single token budget that the model has to fit an entire call into, including its own reply. It is the most consequential operational constraint of any LLM application. What counts against the budget: the system prompt (often 500 to 2,000 tokens for a real product), the few-shot examples if you have them, the full conversation history (every user message and every assistant reply, growing linearly with turns), any retrieved context from a RAG pipeline (3 to 10 chunks of 500 tokens each is typical), any tool-call results returned to the model, and the generated reply itself. The critical implication is that input and output share the budget. A 1M-token window on Claude Opus 4.7 or Gemini 3.1 means input plus output must fit under 1M, not that the input alone can be 1M. The max-tokens parameter caps the reply length, and the model will refuse to start generating if there is not enough room left. Most client SDKs handle context-window exhaustion by truncating from the oldest messages, which silently drops earlier context. Production systems instrument token usage per call as a metric and apply explicit history summarization, RAG chunk limits, or conversation windowing before the SDK has to truncate. The newer 1M-token windows have not eliminated this discipline; they have just moved the ceiling higher.