#1186·Vane

[BUG] chatModels reset to empty array on container restart — Anthropic provider

Author: sbolognesi1Created Aug 20, 2026Updated Aug 26, 2026
Labelsbug

Description

When using the Anthropic provider, chatModels is always reset to an empty array [] every time the container restarts, even if the config.json was manually edited with correct model entries before startup.

Environment

  • Vane version: itzcrazykns1337/vane:latest (pulled 2026-08-20)
  • Deployment: Docker (single container, bundled SearxNG)
  • NAS: Synology DS220+ (DSM 7.x)
  • Provider: Anthropic Claude
  • Model attempted: claude-haiku-4-5-20251001

Steps to reproduce

  1. Stop the Vane container
  2. Edit config.json in the volume (/home/vane/data/config.json) and add a valid entry to chatModels:
json
   "chatModels": [
     {
       "name": "Claude Haiku 4.5",
       "key": "claude-haiku-4-5-20251001"
     }
   ]
  1. Restart the container
  2. Check config.json again — chatModels is empty []

Verified facts

  • The Anthropic API key is valid: direct curl to https://api.anthropic.com/v1/models from inside the container returns the full model list ({"data":[...]}) with no errors
  • SearxNG is running and responding correctly on localhost:8080 with JSON format enabled
  • The /v1/models API call succeeds but the returned models are not persisted to config.json
  • Every restart resets chatModels to [], making the provider unusable

Expected behavior

chatModels should either be populated from the API response on startup and persisted, or the manually configured entries should be preserved across restarts.

Actual behavior

chatModels is always [] after container restart. All searches return empty results (Error: is empty) because no chat model is configured.

Log output

Note: the "Unauthorized" error appears intermittently even with a valid API key — possibly a race condition during startup before the key is fully loaded.

Workaround

None found. Provider temporarily replaced with Groq as a workaround.