🏗️ Architecture: Should the vault route live under /vitto/connections/vault o...

Date: 2026-03-30
Time: 18:33:52 UTC
Session: gspace1-290.13
Agent: testing
Confidence: 93%
Status: ✅ Documented

📋 Decision Context

Question:

Should the vault route live under /vitto/connections/vault or at the app root level?

Task: Not specified

🎯 Decision Made

Chosen:

Moved vault from /vitto/connections/vault to /space/:spaceSlug/vault — platform-level feature, not a Vitto tool. Added cross-app navigation via getFrontendAppUrl() for Computer Use (gograb-ai) to link to vault (gograb-space).

Options Considered:

1. Keep under /vitto/connections/vault (discoverability via Vitto nav)
2. Move to /space/:spaceSlug/vault (correct ownership hierarchy, chosen)
3. Add to both locations with redirect

💭 Reasoning

The vault manages credentials for the user across ALL features (Computer Use, future automations, API integrations). Nesting it under /vitto implied it was a Vitto-specific tool. The route hierarchy should reflect ownership: vault belongs to the user/space, not to the AI assistant. Also critical: Computer Use runs on gograb-ai (port 6400, ai.gograb.space) while vault is on gograb-space (port 6200, app.gograb.space). Simple router.navigate fails cross-app. Created FRONTEND_APP_URLS constants + getFrontendAppUrl() helper that auto-detects production vs local via window.location.hostname. Links from Space Settings and User Preferences (same app) use router.navigateByUrl; links from Computer Use (different app) use window.open with resolved URL.

📁 Files Involved

• apps/gograb-space/src/app/app.routes.ts
• libs/libs-foundational/api-config/src/lib/environment-presets.ts
• libs/libs-ai/vitto-hub/src/lib/components/computer-use-panel/computer-use-panel.component.ts

🔗 Related

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

Auto-generated by MCP Smart Consolidation