Skip to content
Troubleshooting

Troubleshooting

When something doesn’t work, start here. This section covers the most common issues across install, licensing, startup, MCP, providers, sessions, and packs, with fixes aligned to the current Valdr app and UI.

Quick triage

Start with these checks whenever something feels off:

  1. Confirm how Valdr was started. valdr and valdr ui start the web app on 127.0.0.1:<port> (default 7777). MCP hosts should launch valdr pm.
  2. Check System Monitoring. Use it to confirm the process is alive, find the exact PM DB Path, and inspect CPU, memory, and event-loop health.
  3. Check your license in the UI. Open Settings > Settings and confirm the current status and tier.
  4. If the issue is MCP-specific, inspect your MCP host config. Confirm it launches valdr pm, uses the expected --pm-home, and has the right working directory and environment variables.

By category

Still stuck?

If you’ve worked through the relevant section and still need help:

  • Copy the Version, Runtime, Platform, and PM DB Path fields from System Monitoring
  • Open an issue at projectviking-ai/valdr with what you expected, what happened, and how you started Valdr
  • Local-first: share only what you’re comfortable sharing from your machine