Skip to main content
Effective context management ensures Verdent has the right information at the right time while avoiding performance degradation from context overload.

What You’ll Learn

  • Understanding context windows and their limits
  • Selecting files strategically for optimal context
  • Recognizing and responding to context overload
  • When to reset context for better performance

Understanding Context Windows

Verdent’s context window size depends on the model being used.
Most models use standard 200K context windows:
  • Claude Sonnet 4.5 - Balanced for complex tasks
  • Claude Haiku - Fast and efficient
  • GPT-5 - Reasoning tasks (Beta)
  • GPT-5-Codex - Code generation (Beta)
Capacity:
  • ~200,000 tokens of total memory
  • Sufficient for most development tasks
What’s Included:
  • All messages in conversation
  • File contents loaded into context
  • Tool outputs and responses
  • System prompts and instructions

Strategic File Selection

Be strategic about file selection to optimize context usage.
Start with fewer files and add more only when needed—Verdent can always read additional files during the conversation.
Use @-mentions for explicit file inclusion:
@filename.js
Verdent auto-loads related files, but @-mentions ensure precise control. Only include files directly relevant to the current task.

Recognizing Context Overload

Signs:
  • Less accurate or incomplete responses
  • Missing important details from earlier in conversation
  • Confused about recent changes or context
Action: Start a fresh task when quality degrades
If Verdent’s responses become vague or repetitive, context overload may be occurring. Start a new task to restore full performance.

When to Reset Context

  • Noticeably slower response times
  • Less accurate or inconsistent responses
  • Verdent forgetting earlier context
Action: Start fresh task when quality degrades
Best Practice: Complete atomic unit of work → test → commit → start fresh task.

See Also