Skip to main content
Verdent for VS Code features a clean, three-part interface designed for minimal distraction. All interactions happen within the Visual Studio Code sidebar, keeping you close to your code.

​
Accessing Verdent

Open Verdent using any of these methods:
  • Sidebar Icon - Click the Verdent icon in the Visual Studio Code activity bar (left sidebar)
  • Keyboard Shortcut - Press Cmd+L (macOS) or Ctrl+L (Windows/Linux)
  • Command Palette - Press Cmd+Shift+P / Ctrl+Shift+P, then search for “Verdent”
The panel opens in the Visual Studio Code sidebar and can be resized, moved, or docked as needed.
Resize the Verdent panel by dragging its edge to see more conversation history or give your editor more space.

​
Interface Components

  • Top Bar
  • Chat View
  • Input Box
Quick access to key functionality:
ButtonFunction
New SessionStart a fresh conversation with clean context
Project HistoryBrowse and restore previous sessions
User CenterView account information and credit balance
FeedbackSubmit feedback and report issues
SettingsConfigure MCP servers, subagents, rules, and model presets

​
Status Indicators

Verdent communicates system state through visual indicators:
  • Chat View Status
  • Text Cursor
  • Mode Indicators
The Chat View communicates status through visual cues rather than explicit labels:
  • Processing Indicator - A visual indicator appears when Verdent is actively working. This shows when the AI is reading files, analyzing code, or preparing to respond.
  • Text Being Generated - You’ll see Verdent’s response appearing in real-time as the AI composes explanations, code suggestions, or plans. The streaming text indicates the model is actively generating output.
  • Nothing Happening - When the Chat View is static with no activity, Verdent is waiting. This means you need to approve file changes, answer clarifying questions, or provide your next request.
Status indicators update in real-time to show exactly what Verdent is doing, helping you understand agent activity.
  • Top Bar Navigation
  • Input Box Navigation
  • Returning to Chat View
The Top Bar uses different navigation patterns depending on the function:Buttons:
  • New Session - Clicking this button immediately clears your current conversation and returns you to a fresh Chat View with clean context. There’s no separate page or popup; it happens instantly in the same view.
Pages:
  • Project History - Opens a dedicated full-page view where you can browse all your previous sessions and conversations. This navigates away from the Chat View to show your session history. Click the X button to return to the Chat View.
Popups (Overlay Dialogs):
  • User Center - Opens an overlay popup displaying your account information, credit balance, and usage details. The Chat View remains visible behind the popup.
  • Feedback - Opens an overlay popup with a form to submit feedback and report issues. The Chat View stays in the background.
To close popups, either click outside the popup area or use the X button in the popup corner.Dropdown Menus:
  • Settings - Opens an inline dropdown menu with options for MCP servers, subagents, rules, and model presets. When you select an option from the menu (e.g., “MCP Servers”), it opens a dedicated full-page view for that configuration. Click the X button to return to the Chat View.
Use @-mentions and slash commands to guide navigation—this helps Verdent understand your intent and choose the right tools.

​
Customizing with Rules

Access Settings → Rules to customize Verdent’s behavior using Markdown files:
  • User Rules
  • Project Rules
  • Plan Rules
File: user_rules.mdScope: Global preferences applied across all projectsPurpose: Set your personal usage preferences that Verdent will apply during chats across all workspaces. These are global settings that persist across all sessions regardless of which project you’re working on.Common Use Cases:
  • Default output language (e.g., “Always respond in Spanish”)
  • Code comment preferences (e.g., “Include detailed comments in generated code”)
  • Response formatting (e.g., “Use TypeScript for all JavaScript examples”)
  • Personal coding style preferences
How to Edit:
1

Open Settings

Click Settings in the Top Bar
2

Select Rules

Choose Rules from the dropdown menu
3

Edit User Rules

Select User Rules to create or edit user_rules.md in Markdown format

​
See Also

Quick Start

Start using the interface with your first task

Configuration Settings

Customize interface behavior and preferences