🐛 Bugfix: Why did the VSCode extension's Vitto chat return 405 on prod...

Date: 2026-03-31
Time: 12:00:35 UTC
Session: gspace1-290.20
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Why did the VSCode extension's Vitto chat return 405 on production?

Task: Fix production Vitto chat 405 error in VSCode extension

🎯 Decision Made

Chosen:

Fixed getVittoApiDirectUrl() to use vitto-api.gograb.space instead of ai.gograb.space

Options Considered:

1. Fix getVittoApiDirectUrl() to hardcode the correct production URL
2. Add vittoApiUrl to the EnvironmentConfig type and resolve it properly
3. Use the environment-presets from @libs-foundational/api-config

💭 Reasoning

Root cause: getVittoApiDirectUrl() used this.environment.vittoUrl (https://ai.gograb.space) + '/vitto-api'. ai.gograb.space is the FRONTEND Angular app (gograb-ai), not the backend API. The frontend has no /engine routes → 405. The actual backend-vitto-api on Railway is at vitto-api.gograb.space. Verified: curl to ai.gograb.space/vitto-api/engine/agent-session → 405. curl to vitto-api.gograb.space/vitto-api/engine/agent-session → 401 (endpoint exists, needs auth). The web app's environment.prod.ts confirms: VITTO_API_URLS.production = 'https://vitto-api.gograb.space/vitto-api'.

📁 Files Involved

• apps/vitto-vscode-extension/src/services/config.service.ts

🔗 Related

• Decision ID: dev_1774958435629_7sgia5a
• Session: 290
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation