Configuration & Customization

Verdent for VS Code provides extensive configuration options to adapt to your development workflow, coding preferences, and team standards. Configure settings through VS Code's native settings interface, customize keyboard shortcuts, and create rules and subagents for specialized behavior.

What You'll Learn

• Configure VS Code extension settings for Verdent
• Customize keyboard shortcuts for efficient workflow
• Create and manage Rules for personalized agent behavior
• Build custom subagents for specialized tasks

Prerequisites

• Verdent for VS Code installed and authenticated
• VS Code settings access (Cmd+, or Ctrl+,)
• Basic understanding of JSON for rule files (optional)

VS Code Extension Settings

Verdent for VS Code settings are accessed through multiple locations depending on the configuration type and scope.

Accessing Settings

Extension Settings (VS Code Native):

1. Open VS Code Settings: Cmd+, (macOS) or Ctrl+, (Windows/Linux)
2. Search for "Verdent" in the settings search bar
3. Modify extension settings (e.g., verdent.enableCheckpoints)

Verdent-Specific Settings:

Click the Settings button in the Verdent top bar to access:

• Rules - User Rules, Project Rules, Plan Rules
• MCP Servers - Model Context Protocol configurations
• Subagents - Custom subagent management

In-Chat Controls:

Many settings can be toggled directly from the Input Box at the bottom of the Verdent panel:

• Switch Permission - Manual Accept, Auto-Run, Plan, Skip Permissions
• Switch Mode - Agent, Plan, Chat modes
• Switch/Customize AI Model - Performance, Balance, Efficiency presets
• Think Hard Mode - Maximum thinking budget for complex reasoning
• Add Context - Attach files using @-mentions
• Add Images or Files - Include screenshots or documents
• Add Subagent - Delegate to specialized subagents

Settings changes take effect immediately without requiring VS Code restart.

Available Extension Settings

Verdent for VS Code provides 2 core extension settings that can be configured through VS Code's settings interface:

Input Box Controls Reference

The Input Box at the bottom of the Verdent panel provides quick access to configuration controls:

Permission Modes

Model Presets

Keyboard Shortcut Customization

Default Shortcuts

Primary Shortcut:

• macOS: Cmd+L - Open/Focus Verdent Panel
• Windows/Linux: Ctrl+L - Open/Focus Verdent Panel
  • Command: verdent.addToChat
  • Works from Command Palette and Editor Context

This is the essential shortcut for accessing Verdent quickly from anywhere in VS Code without interrupting your coding flow.

Additional Commands:

Available via Command Palette (default shortcuts can be customized):

• verdent.addFeedBack - Provide feedback
• verdent.addTerminalOutputToChat - Add terminal output to Verdent
• verdent.addToChatBySearch - Add to Verdent by search
• verdent.centerButtonClicked - User Center
• verdent.historyButtonClicked - Project History
• verdent.mcpButtonClicked - Add MCP Server
• verdent.openInNewTabByParams - Open in new tab
• verdent.plusButtonClicked - New Session
• verdent.rulesButtonClicked - Rules Settings
• verdent.SettingClicked - Settings Menu
• verdent.subagentButtonClicked - Add Subagent

Customizing Shortcuts

All Verdent keyboard shortcuts can be customized using VS Code's standard keybinding system.

{
  "key": "cmd+shift+v",
  "command": "verdent.addToChat"
}

{
  "key": "ctrl+shift+v",
  "command": "verdent.addToChat"
}

Customization Scope:

• All Verdent commands can be remapped
• Multiple shortcuts can be assigned to the same command
• Default shortcuts can be removed
• Changes sync across machines with VS Code Settings Sync

Platform-Specific Shortcuts

Verdent follows VS Code's platform-specific keyboard conventions:

Common Patterns:

• Settings: Cmd+, (macOS) vs Ctrl+, (Windows/Linux)
• Command Palette: Cmd+Shift+P (macOS) vs Ctrl+Shift+P (Windows/Linux)
• Keyboard Shortcuts: Cmd+K Cmd+S (macOS) vs Ctrl+K Ctrl+S (Windows/Linux)

Custom Instructions & Personas

Verdent for VS Code supports two systems for customizing AI behavior: Rules for preferences and guidelines, and Subagents for specialized task personas.

Rules System

Rules define how Verdent behaves and responds during coding sessions. Rules are stored in Markdown files and continuously applied throughout conversations.

Three Types of Rules

1. User Rules (VERDENT.md):

• Location: ~/.verdent/ (global configuration directory)
• Scope: Applied to all conversations across all projects
• Purpose: Personal coding preferences, communication style, documentation standards

2. Project Rules (AGENTS.md):

• Location: Project root directory or workspace
• Scope: Applied only to the current project
• Version Control: Can be committed to git for team-wide standards
• Purpose: Project-specific coding standards, architectural patterns, testing requirements

3. Plan Rules (plan_rules.md):

• Location: ~/.verdent/ (global configuration directory)
• Scope: Applied when using Plan Mode across all projects
• Purpose: Customize plan content, format, and detail level

Creating and Editing Rules

Example User Rules:

# Code Style Preferences
- Always use functional React components with hooks
- Prefer TypeScript over JavaScript
- Add JSDoc comments for all exported functions
- Provide explanations before showing code

Example Project Rules:

## Testing instructions
- Run `pnpm turbo run test --filter <project_name>` to run all checks
- Fix test and type errors until suite is green
- Add or update tests for code changes

## PR instructions
- Title format: [<project_name>] <Title>
- Always run `pnpm lint` and `pnpm test` before committing

Rules Storage and Application

Configuration Priority:

When rules conflict, Verdent applies this priority order:

1. Project Rules (AGENTS.md) - Highest priority (project-specific)
2. User Rules (VERDENT.md) - Global user preferences
3. Default Behavior - Verdent's built-in defaults

Subagents

Subagents are specialized AI agents with custom system prompts and isolated context windows for handling specific tasks.

Built-in Subagents

Verdent includes three default subagents immediately available without configuration:

Creating Custom Subagents

Subagent File Format:

---
name: security-reviewer
description: Security-focused code review specialist
---
# System Prompt

You are a security-focused code reviewer. When analyzing code:
- Prioritize security vulnerabilities (SQL injection, XSS, auth flaws)
- Use skeptical, critical tone - assume code is vulnerable until proven otherwise
- Provide specific remediation steps with code examples
- Reference OWASP Top 10 and security best practices
- Never approve code with unresolved security issues

Invocation policy (strict): Only run security-reviewer if user explicitly requests it.

When to use the security-reviewer agent:
- User requests security review of authentication/authorization logic
- User asks to audit code for vulnerabilities
- User needs security assessment before deployment

When NOT to use:
- General code review without security focus
- Opening or reading files without analysis

Managing Subagents

Access through Settings → Subagents to:

• Edit: Modify system prompts, tool permissions, configurations
• Copy: Duplicate subagents for variations or templates
• Delete: Remove unused subagents
• Enable/Disable: Toggle availability without deletion

Using Subagents

Built-in Subagents:

• Reference with @-mentions: @Verifier, @Explorer, @Code-reviewer
• Automatically invoked when appropriate task types are detected

Custom Subagents:

• Click Add Subagent button in Input Box
• Select from dropdown
• Main agent automatically delegates appropriate tasks

Subagent vs Rules

Example Workflow:

1. User Rule: "Generate unit tests for all new functions"
2. Main Agent: Detects need for test generation
3. Delegates to Test Generator Subagent: Specialized comprehensive testing approach
4. Subagent: Generates complete test suite with isolated context
5. Main Agent: Receives results and continues without context pollution

FAQs (Frequently Asked Questions)

See Also