fddfcfd2a6
User report after the v0.4.0 desktop agent landed: > agente devuelve "LLM call failed: Failed to fetch" "Failed to fetch" is a network-layer error, not 401. Root cause: the OSS CORS allow_origins list only included http://localhost:517[3-5] (vite dev) and settings.FRONTEND_URL. The desktop bundle runs from either tauri://localhost (macOS/Linux) or http://tauri.localhost (Windows) - both cross-origin to velxio.dev - so the browser blocked the agent's POST /api/pro/agent/llm preflight before the backend ever saw it. Added all three Tauri scheme variants to the allow list. After this lands + a backend restart the desktop agent's fetch reaches the real /api/pro/agent/llm and the dual-auth dep from v0.4.0 Phase 1 gets to do its job (Bearer license-key → resolved User → quota check → upstream LLM proxy). Origins added: tauri://localhost # macOS / Linux (Tauri 2.x default) http://tauri.localhost # Windows (Tauri 2.x default) https://tauri.localhost # older Tauri 2.x releases allow_credentials stays True - the existing cookies-from-web flow still works, the Tauri origins just don't have any cookies to send. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| api | ||
| core | ||
| database | ||
| mcp | ||
| models | ||
| schemas | ||
| services | ||
| utils | ||
| __init__.py | ||
| main.py | ||