Context Awareness is Verdent’s ability to keep track of code, tasks, and conversation context while understanding dependencies across your project. With up to 1M token capacity, Verdent comprehends entire medium-sized codebases.

What You’ll Learn

  • Understanding context windows (200K vs 1M)
  • How Verdent tracks dependencies
  • Context isolation across parallel tasks
  • Recognizing and resetting context overload

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 4.5 - Fast and efficient
  • GPT-5 (Beta) - Excellent for reasoning
  • GPT-5-Codex (Beta) - Optimized for coding
  • Gemini 3 Pro - Advanced reasoning and multimodal
  • Kimi K2 Series - Lightning-fast for coding
Capacity:
  • ~200,000 tokens of total memory capacity
  • Sufficient for most development tasks and medium-sized projects
What’s Included:
  • All messages in conversation
  • File contents loaded into context
  • Tool outputs and responses
  • System prompts and instructions
  • MCP server definitions
Performance:
  • Degrades significantly when approaching limits
  • Watch for signs of context overload (slower responses, less accurate outputs)
  • Reset context more frequently for optimal performance

What Verdent Tracks

Context TypeWhat’s Preserved
Code ContextFile contents, structure, coding patterns, file relationships
Task ContextCurrent goals, progress, decisions made, conversation history
Dependency ContextImports, exports, function calls, configuration references

Understanding Dependencies

How Verdent Tracks Dependencies

Verdent understands how files in your project relate to each other:
RelationshipExample
Importsimport { UserService } from './services'
Exportsexport class UserController
ReferencesFunction calls, class instantiation
ConfigurationConfig files referenced by multiple modules

Context Across Parallel Tasks

How Context Works in Parallel Execution

When running multiple agents in parallel, each maintains independent context:
AspectBehavior
Per-Workspace ContextEach workspace has separate context
Per-Task ContextEach task has its own conversation context
No Cross-ContaminationParallel agents don’t share context
Project-Level AwarenessAll agents can understand project structure

Switching Tasks

When you switch between tasks:
What HappensDescription
Context PreservedEach task’s context remains intact
No ConfusionContexts don’t mix between tasks

Recognizing Context Overload

SymptomSigns
Response QualityLess accurate responses, missing details, inconsistent outputs
Speed IssuesSlower responses, longer processing delays
Behavioral ChangesForgetting earlier context, redundant questions
TechnicalSessions running for several hours, or 20+ large files (>1000 lines each) loaded
If Verdent’s responses become vague or repetitive, context overload may be occurring. Reset the conversation to restore full performance.

When to Reset Context

ScenarioAction
Performance degradesStart fresh session when quality drops
Task transitionsNew session for unrelated features or modules
After commitsCommit → test → new session
Long sessionsProactively reset before context degrades
Best Practice: Complete atomic unit of work → test → commit → clear context → start fresh.

Best Practices

PracticeBenefit
Use @-mentionsDirect Verdent to specific files (@filename, @folder/)
Be specific about scopeLimits context to relevant areas
Focus on specific modulesBetter performance on large codebases

FAQs

For most projects, Claude Sonnet 4.5 (200K) is sufficient. For large codebases or long development sessions, use Claude Sonnet 4.5 1M for extended context.
Yes. Extended context models have higher credit consumption than standard 200K models.
Start a new task to reset context. Your previous task remains accessible in the task list.
No. File changes are saved to your workspace. Only conversation context resets.
Yes. The Context Remaining indicator in the middle panel shows remaining capacity for the current conversation.
Yes. Task history persists between sessions. You can resume tasks where you left off when you reopen Verdent.

See Also