🏗️ Architecture: How to migrate Chrome extension from ai-panel-core to vitto-...

Date: 2026-02-27
Time: 00:22:26 UTC
Session: gspace1-149.4
Agent: architecture
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How to migrate Chrome extension from ai-panel-core to vitto-chat (plugin-based)?

Task: Session 149: Phase 2 - Extension panel migration

🎯 Decision Made

Chosen:

Created VittoChatPanelComponent at /panel-v2 route that renders with all Session 149 plugins. Dual-route strategy keeps /panel (old) alongside /panel-v2 (new). Chrome extension sidepanel.js updated to load /panel-v2 by default. Same URL param parsing and auth bootstrap as the old ExtensionPanelComponent.

Options Considered:

• No alternatives documented

💭 Reasoning

Dual-route strategy enables safe rollback during migration. The new panel composes all 10+ plugins based on user tier (developer gets everything, platform_user gets basics). VittoChatPanelComponent mirrors the auth bootstrap pattern from the old ExtensionPanelComponent (lines 157-193) but outputs to the vitto-chat plugin system instead of the monolithic ai-panel config.

📁 Files Involved

• apps/gograb-ai/src/app/pages/vitto-chat-panel/vitto-chat-panel.component.ts
• apps/gograb-ai/src/app/app.routes.ts
• apps/vitto-chrome-extension/sidepanel/sidepanel.js

🔗 Related

• Decision ID: dev_1772151746203_vawlvvt
• Session: 149
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation