Troubleshooting

Common issues and how to fix them.

Ollama not running / model not found

Symptoms: Chat fails with a connection error or “model not found.”

  • Start Ollama: ollama serve
  • Pull a model: ollama pull qwen2.5-coder:7b or ollama pull llama3.2
  • Check ravenkit.agent.ollamaUrl (default http://localhost:11434) and ravenkit.agent.model

Extension not loading

Symptoms: RavenKit commands don’t appear or the panel doesn’t open.

  • If you built from source, run pnpm compile in apps/ravenkit and ensure dist/extension.js exists.
  • Open Help → Toggle Developer Tools and check the Console for errors.
  • Reload the window: Command Palette → Developer: Reload Window.

Tools not executing

Symptoms: Corvus responds but file/terminal actions don’t run.

  • Some tools require approval; check for a prompt in the chat or notification.
  • Ensure the workspace is trusted and you have read/write access to the project folder.
  • Check Developer Tools console for errors when a tool runs.

Stacksolo / sync issues

Symptoms: Sync fails, “offline,” or conflict messages.

  • Run RavenKit: Authenticate with Stacksolo and sign in again.
  • Check ravenkit.stacksolo.apiEndpoint and network access.
  • For conflicts, use RavenKit: Resolve Sync Conflict or set ravenkit.stacksolo.conflictResolution to local or remote.

CLI (corvus) not found or fails

If you use the corvus CLI from the terminal:

  • Build the extension first: from apps/ravenkit, pnpm compile. The CLI is node dist/agent-cli.js.
  • Run from the project folder you want as scope, or use --dir /path/to/project.

Get started · Commands · Configuration