🏗️ Architecture: Should the Studio dock layout include its own Vitto chat pan...

Date: 2026-03-08
Time: 01:04:43 UTC
Session: gspace1-188.6
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Should the Studio dock layout include its own Vitto chat panel, or reuse the main app's AI panel?

Task: S188: Studio chat architecture — single source of truth

🎯 Decision Made

Chosen:

Reuse the main app's AI panel (right side). No duplicate chat panel in Studio dock layout. VittoPageContextRegistry makes the single chat Studio-aware via page context registration. AIPanelCoreStateService.openWithContext({ contextType: 'vitto-studio' }) called on Studio init.

Options Considered:

1. Add studio-vitto-chat as dock panel (duplicate chat)
2. Reuse main app AI panel with VittoPageContextRegistry (chosen)

💭 Reasoning

Initial plan had a 'studio-vitto-chat' dock panel wrapping StudioChatPanelComponent. User correctly identified this as wrong — it would create two chat interfaces (one in dock, one in main app's right panel), confusing users about which to use. The main app's AI panel already receives context from VittoPageContextRegistry, which the Studio dock shell registers with page description, readable state, actions, and scoped tools. Adding another chat panel would: (1) duplicate state, (2) confuse users, (3) waste screen real estate, (4) break the single-chat plugin architecture. The fix: removed studio-vitto-chat panel entirely, changed dock layout from 3-column (sidebar|center|chat) to 2-column (sidebar|center), let the main AI panel handle all chat with Studio context injected.

📁 Files Involved

• libs/libs-structural/vitto-studio/src/lib/config/studio-dock-panels.config.ts
• libs/libs-structural/vitto-studio/src/lib/components/studio-dock-shell/studio-dock-shell.component.ts

🔗 Related

• Decision ID: dev_1772931883772_qn9dkzm
• Session: 188
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation