Skip to main content
This quickstart guide will have you using Verdent’s Plan-Verify-Code workflow in under 15 minutes. You’ll install the extension, complete your first task, and understand the core workflow when working with Verdent for VS Code.

What You’ll Learn

  • Install Verdent for VS Code from the marketplace
  • Authenticate and verify your setup
  • Complete your first AI-assisted task
  • Understand execution modes (Manual Accept, Auto-Run, Plan Mode)
  • Use essential features for daily coding

Prerequisites

Before you begin, make sure you have:
  • Visual Studio Code installed on your system
  • An active internet connection
  • A Verdent subscription account (or start with the 7-day free trial)

Step 1: Install Verdent

  • Visual Studio Code Marketplace
  • Extensions Panel
  • Command Line
Visit the Verdent extension page and click Install.

Step 2: Start Using Verdent

1

Open Visual Studio Code

Open Visual Studio Code in your project folder.
2

Access Verdent

Click the Verdent icon in the sidebar or press Ctrl+L (Windows/Linux) / Cmd+L (macOS).
3

Sign In

Sign in when prompted to authenticate with your Verdent account.

Step 3: Your First Task

Let’s start with a simple, non-destructive task that demonstrates Verdent’s understanding of your workspace. Open a project in VS Code, then try one of these prompts in the Verdent input box:
What kind of project is this?
Verdent will analyze your workspace structure, read key files, and explain what type of application you’re working on. This demonstrates context awareness without making any changes. You should see:
  • Verdent analyzing files in your workspace
  • A summary of your project type, technologies, and structure
  • No file modifications (read-only analysis)
Try these follow-up prompts:
Explain what this project does
What dependencies does this project have?
Show me the main entry point of this application
Each prompt helps you verify that Verdent can access your workspace and understands your codebase.
These exploratory prompts are perfect for understanding unfamiliar codebases. Verdent reads files as needed without requiring you to manually add context.

Step 4: Making Your First Code Change

Now let’s make Verdent create something. Try this simple task:
Create a hello_world.txt file with a greeting message
What happens:
  1. Verdent proposes the change You’ll see a preview showing the file to be created and its contents
  2. Permission request In Auto Run Mode (the default), Verdent will auto-approval when creating the file
  3. You approveL Click “Accept” or approve the change
  4. File created Verdent creates the file and confirms completion
Understanding permissions: Manual Accept Mode ensures no unwanted modifications occur without your approval. You’ll see permission prompts for:
  • File edits and creations
  • Command executions
  • Tool usage (first use of each tool type)
This gives you full control and helps you learn what operations Verdent performs for different tasks.
Manual Accept Mode is the recommended starting point for new users. Once comfortable, you can switch to Auto-Run Mode or Plan Mode for different workflows.

Step 5: Using Plan Mode for Complex Tasks

Plan Mode is Verdent’s read-only planning mode where you can review approaches before execution. Let’s try it: Switch to Plan Mode: Click the Switch Mode button in the input box and select Plan Mode Try a planning task:
Suggest ways to build a website for my project
What happens:
  1. Verdent analyzes your project It reads files and understands your project structure and requirements
  2. Creates a detailed plan Shows what technologies to use, what pages to create, and how to structure the website
  3. No modifications Plan Mode is read-only. Verdent cannot modify files until you explicitly approve
  4. Interactive clarification Verdent may ask questions about design preferences, target audience, or features before finalizing the plan
Why use Plan Mode:
  • Safe exploration - Understand unfamiliar codebases without accidental changes
  • Code review - Analyze quality and architecture before making modifications
  • Strategic planning - Break down complex tasks into reviewable steps
  • Uncertainty reduction - Verdent asks clarifying questions to remove ambiguity
Use Plan Mode for any task where you want to review the approach before committing to execution. It’s particularly valuable when learning how Verdent thinks about your codebase.
To execute the plan: After reviewing the plan, Verdent presents two options:
  • Choose Edit to request modifications or ask clarifying questions
  • Choose Start Building to switch to Agent Mode and begin execution

Step 6: Understanding Execution Modes

Verdent offers multiple execution modes to match different workflows: Permission Modes:
ModeDescriptionWhen to Use
Manual AcceptRequests permission on first use of each toolLearning and general development with maximum control
Auto-Run(default)Automatically accepts safe operations (file reads, web searches); file edits and commands still require approvalTrusted projects and rapid prototyping
Plan ModeRead-only mode for analysis and planning without file modificationsComplex tasks and code review
Skip PermissionsFully autonomous operation bypassing all promptsIsolated, safe environments like automated testing or sandboxes
Additional Mode:
  • Think Hard Mode - Maximum thinking budget for complex reasoning and architectural decisions
Skip Permissions Mode removes all safety checks. Only use in isolated, disposable environments where mistakes have no consequences.

Essential Actions

Here are the key actions you’ll use daily in Verdent for VS Code:
ActionHow to AccessDescription
Open VerdentCmd+L / Ctrl+L or click sidebar iconOpens the Verdent panel
New SessionClick “New Session” in top barStart a fresh conversation with clean context
Add ContextClick “Add Context” buttonReference files with @-mentions
Add ImagesClick “Add Images or Files” buttonUpload screenshots, mockups, or diagrams
Switch ModeClick “Switch Mode” buttonToggle Agent/Plan/Chat modes
Change ModelClick model selectorChoose Performance/Balance/Efficiency presets
Think HardClick “Think Hard Mode” buttonEnable extended reasoning for complex tasks
Switch PermissionsClick “Switch Permission” buttonChange permission mode
View HistoryClick “Project History” in top barBrowse past sessions
User CenterClick “User Center” in top barCheck credit balance and account info
SettingsClick “Settings” in top barConfigure MCP servers, subagents, rules

Pro Tips for Beginners

Before making changes, let Verdent understand your codebase:
Analyze the database schema
Explain the authentication flow
This builds Verdent’s context about your project and helps it make better suggestions.
Instead of: “fix the bug”Try: “fix the login bug in LoginForm.tsx where users see a blank screen after entering wrong credentials”Specific prompts lead to more accurate solutions and fewer iterations.
When working with code you don’t fully understand, use Plan Mode first:
Refactor the authentication module to use async/await instead of callbacks
Review the plan, choose Edit to ask clarifying questions and refine, then choose Start Building once confident.
For multi-step features, work incrementally:
1. Create a new database table for user profiles
Then after completion:
2. Create an API endpoint to get and update profiles
This maintains clarity and allows you to verify each step.
Explicitly reference files when needed:
@components/UserProfile.tsx refactor this component to use hooks
This ensures Verdent focuses on the right context for your task.
Verdent includes three built-in subagents:
  • @Explorer - Fast codebase exploration and file discovery
  • @Verifier - Quick code validation and checks
  • @Code-reviewer - Comprehensive security and quality review
Example:
@Explorer find all API endpoints in this project

Common Issues

  • Extension not visible in sidebar
  • Prompts don't get responses
  • Permission prompts are too frequent
Solution: Restart VS Code. If still missing, verify installation in the Extensions panel (Cmd+Shift+X / Ctrl+Shift+X) and confirm “Verdent” appears in the list.

Getting Help

  • Discord Community: https://discord.com/invite/NGjXEZcbJq - Active community with real-time support
  • Documentation: Browse other guides in this documentation
  • Feedback: Use the Feedback button in Verdent’s top bar to report issues or suggest improvements

FAQs

Look at the input box at the bottom of the Verdent panel. The “Switch Permission” button displays your current mode (e.g., “Manual”, “Auto”, “Plan”). You can click it to switch modes.
Verdent will stop processing new requests until your credits refresh at the start of your next billing cycle, or you can purchase a one-time top-up to continue immediately.
Yes, each VS Code window operates independently. You can have Verdent open in multiple projects, and each maintains its own separate conversation context.
Click the “New Session” button in the top bar. This clears the current conversation history and gives Verdent a fresh context window for your next task.

Next Steps

You’ve installed Verdent, completed your first task, and learned the core workflow. Here’s where to go next: