Alva Code

Troubleshooting

No agent available or connection failed

Check installation, sign-in, and model selection in that order.

Step by step

  1. No CLI found / command not found: open CLI Tools and install the chosen provider’s tool. If you installed it outside Alva, restart Alva so it can detect the changed environment.
  2. Installed but not authenticated: use the provider’s sign-in action and complete it. Signing into Alva is a separate login.
  3. Signed in but requests fail: check the selected provider and model, then read the exact provider error. The account may lack model access or have reached a usage limit.
  4. API key rejected: check that it belongs to the selected provider and run its test action.
  5. Local model unavailable: check that Ollama is running, the connection is enabled, and a model has finished downloading.
  6. Still stuck: keep the exact error and describe what you clicked. Once a working agent is available, paste the article context and your question into its chat.

Continue reading

Content version: 2026-10-07 · PDF ↓