Glossary

Explore Meshline

Products Pricing Blog Support Log In

Ready to map the first workflow?

Book a Demo

Glossary / Evaluation and implementation guide

Context Windows

A context window is the maximum amount of text a language model can consider at one time — the prompt, retrieved documents, and conversation history all count against it.

Measured in tokens (word fragments), the limit determines whether an agent can reason over a full account history or only a slice of it.

When input exceeds the window, older content must be dropped or summarized, and the model simply loses sight of it.

A practical example

Example: an agent asked to summarize two years of support tickets and CRM notes for an enterprise account may exceed the window, forcing the platform to select or condense which records the model actually sees.

What to evaluate before investing

  • Ask vendors which model and context size each agent uses, and whether the same model serves all workflow steps.
  • Test with your largest real account: does output quality degrade when history is long, and does the platform disclose what was truncated?
  • Ask how the platform handles overflow — automatic summarization, retrieval-based selection, or silent dropping of older content.

Limitations and tradeoffs

Tradeoff: larger windows cost more per request and do not guarantee better answers, since models can lose focus in very long inputs. Capacity figures are a ceiling, not a quality measure.

Plan your next step with MeshLine

Connect this decision to your automation, organic marketing and customer lifecycle management. In a MeshLine demo, discuss your existing tools, the scope you need and how to measure the result.