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. Extended context (1M) is handled automatically when needed. Available Models:
ProviderModelContext
Anthropicclaude-opus-4.5200K
Anthropicclaude-sonnet-4.5200K
Anthropicclaude-haiku-4.5200K
Googlegemini-3-pro-preview1M
Googlegemini-3-flash-preview1M
OpenAIgpt-5272K
OpenAIgpt-5-codex (Beta)272K
Zhipu AIGLM 4.7200K
Moonshotkimi-k2-turbo262K
What’s Included in Context:
  • All messages in conversation
  • File contents loaded into context
  • Tool outputs and responses
  • System prompts and instructions

​
Viewing Context Usage

Monitor your current context window usage through the Context Remaining indicator in the middle panel. This shows how much context space remains for the current conversation. Context Commands:
CommandDescription
/compactCompress conversation history to free up context space
/clearClear conversation and start fresh
Use /compact when context is running low but you want to continue the same task. Use /clear or start a new task when switching to unrelated work.

​
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

Prompt Engineering

Best practices for writing effective prompts

Resource Management

Monitor token usage and credits