Troubleshooting

Common issues and how to fix them.

Installation

pnpm: command not found

You haven't installed pnpm. Run:

npm install -g pnpm

ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL during build

One of the workspace packages failed to build. Scroll up in the output to find the actual TypeScript error. Common causes:

  • Stale node_modules after pulling new changes โ€” wipe and reinstall
  • Editing a src/ file with a syntax error
rm -rf node_modules pnpm-lock.yaml
pnpm install
pnpm -r build

Cannot find module '@openvesper/core'

You ran a CLI command before pnpm -r build finished. Internal packages need to be built so their dist/ exists. Re-run the build.

Runtime

No LLM provider configured

Set at least one API key in ~/.openvesper/.env:

echo "ANTHROPIC_API_KEY=sk-ant-..." >> ~/.openvesper/.env

Rate limit exceeded

Your LLM provider is throttling you. Either wait, upgrade your plan, or switch to a different provider for that agent:

node apps/cli/dist/index.js -a auto -p groq -q "your query"

Tool fails with HELIUS_API_KEY required

Some Solana-specific tools (holder distribution, creator analysis) require a Helius RPC key for higher rate limits. Get a free key at helius.dev and set it:

echo "HELIUS_API_KEY=your-key" >> ~/.openvesper/.env

Cron / Heartbeats

Scheduled job not running

Check that:

  • The job is enabled: node apps/cli/dist/index.js cron list
  • The scheduler daemon is actually running (not just registered)
  • Your machine is on at the scheduled time

๐Ÿ’ก OpenVesper's scheduler runs in-process. For always-on scheduling, run the CLI under systemd, pm2, or in a Docker container that stays running.

VSCode extension

Extension installed but no panel

Open the command palette (Cmd/Ctrl+Shift+P) and run OpenVesper: Open Chat.

API key not saving

The extension stores keys in VSCode's encrypted secretStorage. If saves are failing, check that VSCode has permission to write to its config directory.

Still stuck?

Open an issue at github.com/openvesper/openvesper/issues with:

  • What you ran
  • The full error message
  • Your OS and Node version (node --version)

What's next?