<- all tokdocs

When Bigger Context Windows Stop Helping Your AI Product

Watch on TikTok

View on TikTok ->

Context windows keep getting larger. Models now accept hundreds of thousands of tokens in a single prompt. The temptation is obvious: just throw all your data in and let the model figure it out. Sahana, a former Pinterest engineer now leading a team building AI-first products, explains why that approach breaks down in practice.

The Attention Problem

A model is not going to read a 200-page prompt with the same focus as a short one. As context size grows, important details get missed. You might fit everything in, but the model will not use all of it equally.

Sahana explaining that models struggle with attention as context size grows

This matters most when your prompt contains contradicting rules or a large number of examples. The model starts averaging out contradictions instead of catching them. Accuracy drops, and the inconsistencies become extremely hard to debug because the failure mode is subtle. The model does not throw an error. It just gives you a slightly wrong answer.

The Cost Problem

If your product relies on data that changes frequently, you end up rebuilding massive prompts at a high frequency. Every API call sends the full context. With large context windows, that means significant cost per call, multiplied by the number of users and the frequency of requests. The math gets expensive fast.

Sahana gesturing while explaining the compounding cost of large context prompts

When Large Context Windows Do Work

Sahana is not saying big context windows are useless. They work well for one-shot analysis tasks where you need the model to consider a large document once. The problems appear when you are building a product that needs to make many calls, handle frequently changing data, or enforce complex rules consistently.

Key Takeaways

  • Models lose focus on long prompts; important details get missed as context size grows
  • Contradicting rules or too many examples cause the model to average out inconsistencies rather than flag them
  • Frequently changing data means rebuilding large prompts often, which compounds API costs quickly
  • Large context is a tool, not a default strategy; the right approach depends on how your product uses data

Published May 25, 2026. Writeup generated from a favorited TikTok.