Skip to main content

​
What You’ll Learn

Common troubleshooting procedures, diagnostic steps, and known issue workarounds for Verdent for VS Code.
Detailed troubleshooting for top user-reported issues is being compiled from support data. This page provides general diagnostic procedures. Contact support@verdent.ai for specific issues not covered here.

​
Quick Diagnostics

  • Service Errors (Most Common)
  • Installation & Setup
  • Authentication & Account
  • Performance
  • Image Errors

​
”Service is experiencing high traffic. Please try again later!”

This is the #1 most common error users encounter. It indicates the Verdent service is temporarily overloaded.When it happens:
  • During peak usage times
  • When backend services are under heavy load
  • Temporary service degradation
Recovery steps (in order):
1

Roll Back Message

If the error persists, roll back the most recent message:
  • Click the rollback/undo button in the chat interface
  • Resubmit your request after a brief wait
2

Start New Session

If errors continue, start a fresh session:
  • Click the ”+” (New Session) button in the top bar
  • This clears context and tool approvals
  • Resubmit your request in the clean session
3

Wait and Retry

Wait 30-60 seconds and try your request again. Most service issues resolve quickly.
If the issue persists for more than 5-10 minutes across multiple sessions, check the Verdent status page or contact support@verdent.ai.

​
Tool-Specific Issues

  • file_edit Failures
  • bash Failures
  • Search Issues

​
file_edit Failures

Error: “Failed to find exact match”Causes:
  • Text changed since last file_read
  • Whitespace differences (tabs vs spaces)
  • String not unique in file
Solutions:
# 1. Read file again to get current state
file_read("file.js")

# 2. Use larger context string for uniqueness
file_edit("file.js",
  old_string="function foo() {\n  return 42;\n}",
  new_string="...")

# 3. For multiple identical strings, use replace_all
file_edit("file.js", old_string="TODO", new_string="DONE", replace_all=true)
Always read the file immediately before editing to ensure you have the current state.

​
Subagent & Configuration Issues

  • Subagent Not Invoking
  • Built-in Subagents
  • AGENTS.md Rules
  • MCP Connection

​
Subagent Not Invoking

Problem: Custom subagent doesn’t activate automaticallyChecklist:
  • File location: ~/.verdent/subagents/[name].md
  • Valid YAML frontmatter with name and description
  • Invocation policy matches usage (strict requires @-mention)
  • “When to use” guidelines match request pattern
  • No syntax errors in markdown file
Test manually:
@subagent-name perform task
Use explicit @-mention to verify the subagent works before troubleshooting automatic invocation.

​
Known Issues & Workarounds

  • Binary Files
  • Large Files
  • Platform Differences

​
Binary File Limitations

Issue: Cannot edit images, PDFs, compiled binariesWorkaround:
# Use bash to call external tools
bash("convert input.png -resize 50% output.png")
bash("pdftotext document.pdf output.txt")
Binary file modifications require external tools invoked via bash commands.

​
Getting Additional Help

​
Support Channels

For specific issues not covered here: When reporting issues, include:
  1. Verdent version (from Extensions panel)
  2. VS Code version
  3. Operating system
  4. Error messages (exact text)
  5. Steps to reproduce
  6. Expected vs actual behavior

​
Diagnostic Information Collection

To help support diagnose: 
# VS Code version
bash("code --version")

# System info
bash("uname -a")  # Unix
bash("systeminfo")  # Windows

# Verdent logs location
# Check VS Code Output panel → Verdent

​
See Also

FAQs

Frequently asked questions

Limitations

Known limitations and constraints