Skip to main content

AI and Automation

Context Window

The context window is the working memory of a request. It sets what you can feed in, it costs money to fill, and bigger is not automatically better.

Definition

The context window is how much text a model can consider in a single request: your instruction, any material you supply, the conversation so far, and the answer it produces, all counted together.

What It Actually Means

Exceed it and something has to be dropped. This is why a long conversation with an AI assistant starts forgetting the beginning, and why feeding it a large document sometimes produces an answer that ignores half of it.

It is working memory for one request, and it is important to understand that it is not storage. Nothing persists between requests unless a system deliberately re-supplies it.

Why It Costs You Money

Providers charge by the amount of text processed, and everything in the window counts on every request.

That has a consequence people meet as an unexpected bill. In a long conversation, the entire history is typically re-sent each time so the model can see it. The twentieth message in a thread costs considerably more than the first, because it carries all nineteen before it. Filling a large window with a whole document, every time, on every query, multiplies out quickly at real volume.

So a large context window is a capability with a running cost attached, and using it as a convenience rather than by design is one of the more common ways AI spend gets away from a business.

Bigger Is Not Automatically Better

Windows have grown enormously, and the instinct is to use the space. Two reasons not to.

Attention thins out. Models handle information at the beginning and end of a long context more reliably than the middle. Material buried in the centre of a very large input is measurably more likely to be overlooked. Supplying more is not the same as being understood better.

Relevance beats volume. Three well-chosen passages usually produce a better answer than sixty pages containing them, because the model is not distracted by the rest. This is precisely the case for retrieval: find the right material and supply only that, rather than sending everything and hoping.

What To Ask

  • How much are we sending per request, and what does that cost at our volume? The arithmetic is straightforward and rarely done.
  • Are we re-sending conversation history every time? Almost certainly. Ask whether older turns can be summarised instead.
  • Are we filling the window or selecting for it? Selecting is cheaper and better.
  • What happens when the limit is hit? Silent truncation is common and produces answers that look complete.

The Practical Consequence

The window sets the boundary of what a model can consider at once, and the sensible design goal is to stay well inside it with carefully chosen material rather than to approach it with everything available.

Systems built that way are cheaper, faster and more accurate at the same time, which is unusual. It is the main reason retrieval remains the right architecture even as windows grow large enough to make it look unnecessary.

More terms are in the glossary.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.