Optimization Areas

  • Model selection for cost and performance balance
  • Execution mode configuration for workflow efficiency
  • Context management for large codebases
  • Per-project and workspace-level customization

Speed vs Thoroughness Tradeoffs

Balance execution speed against analysis depth based on task requirements.
Configuration:
  • Model: Claude Haiku 4.5 (fast, cost-efficient)
  • Execution Mode: Agent Mode for direct execution
  • Use Cases: Quick fixes, routine operations, simple tasks
Benefits:
  • Fastest response times
  • Minimal interruptions
  • Lower credit consumption

Project-Specific Configuration

Project Rules (AGENTS.md)

  • Location: Project root directory or workspace folder
  • Scope: Applied only to the current project
  • Version Control: Commit to git for team-wide standards
  • Content: Coding standards, testing requirements, architectural patterns
Example:
# Project Rules

## Code Standards
- Use TypeScript strict mode
- Generate unit tests for all new functions
- Follow MVC pattern

## Testing
- All endpoints require input validation
- Run tests before committing

Configuration Priority

When configurations conflict, Verdent applies this priority order:
  1. Project Rules (AGENTS.md) - Highest priority (project-specific)
  2. Workspace Settings - Application workspace-level settings
  3. User Rules - Global user preferences (Settings → User Rules)
  4. Default Settings - Verdent’s built-in defaults

Context Management for Large Projects

  • Delegate complex operations to subagents with separate context windows
  • Only subagent results consume main context, not entire process
  • Prevents main context from filling with implementation details
Multi-workspace scenarios automatically apply appropriate project rules when switching workspaces. No manual configuration switching required.

Desktop-Specific Optimization

Parallel Agent Efficiency

Verdent’s parallel execution capability requires optimization consideration:
When Running Multiple Agents:
  • Each agent maintains independent context
  • CPU and memory usage scales with active agents
  • Network requests parallelize for faster completion
Optimization:
  • Limit concurrent agents on resource-constrained machines
  • Use Claude Haiku 4.5 for routine parallel tasks
  • Reserve Claude Sonnet 4.5 for complex individual tasks

Performance Optimization

Model Selection Strategy

Task TypeRecommended ModelReason
Quick fixesClaude Haiku 4.5Speed and cost
General developmentClaude Sonnet 4.5Best tradeoff
Complex architectureClaude Sonnet 4.5 1MExtended context
Parallel routine tasksClaude Haiku 4.5Resource efficiency

Execution Mode Strategy

ScenarioRecommended ModeReason
Learning new codebasePlan ModeSafe exploration
Active developmentAgent ModeFull capabilities
Production changesPlan Mode firstReview before execution

Cost Optimization

Credit Efficiency

Balance credit consumption against productivity:
Strategies:
  • Use Claude Haiku 4.5 for routine tasks (lower credit consumption)
  • Use @verifier for quick validation (separate context)
  • Break large tasks into smaller sessions
  • Use Plan Mode to avoid wasted execution context
Impact: Significant credit reduction for typical workflows

Monitoring Credit Usage

Track consumption in the User Menu:
  • Credit balance: Current credits remaining
  • Subscription details: Plan information
  • Top-up options: Purchase additional credits

FAQs

Large codebase optimization strategies:
  1. Use subagents strategically: @verifier preserves main context
  2. Read files selectively: Use @filename for specific files only
  3. Chunk large tasks: Break features into smaller, focused sessions
  4. Use Plan Mode first: Plan approach before consuming execution context
Recommended team configuration:
  • Project Rules (AGENTS.md): Commit shared coding standards
  • Plan Mode for changes: Review approach before execution
  • Auto Generate Code Review: Enable for quality assurance
This balances productivity with code review needs.
Resource impact:
  • CPU: Linear scaling with active agents
  • Memory: Each agent maintains separate context
  • Network: Parallel API requests
Optimization:
  • 2-3 concurrent agents optimal for most machines
  • Use Claude Haiku 4.5 for parallel tasks
  • Monitor system resources during heavy parallel work

See Also