Architecture: Should every GoGrab app have a native AI panel, or rely on t...

Documentation for Sessions

🏗️ Architecture: Should every GoGrab app have a native AI panel, or rely on t...

Date: 2026-02-11
Time: 17:59:43 UTC
Session: gspace1-105.20
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Should every GoGrab app have a native AI panel, or rely on the Chrome extension?

Task: Session 105.3: Native AI panels in all GoGrab apps

🎯 Decision Made

Chosen:

Every GoGrab app (space, admin, dev) gets a native AI panel. Chrome extension becomes an enhancement layer.

Options Considered:

Native panels in all apps + extension as enhancement
Extension-only approach (no native panels)
Native panel only in gograb-space, extension for others

💭 Reasoning

Native panels ensure the AI is always accessible without requiring extension installation. The extension provides additional capabilities (cross-origin page context, screenshot capture, external site support) but is not a prerequisite. This improves onboarding and reduces friction for new users. Pattern: AIPanelStateService + AiPanelTabsComponent from @libs-ai/vitto-hub are shared across all three apps.

📁 Files Involved

apps/gograb-admin/src/app/core/layout/admin-main-shell/admin-main-shell.component.ts
apps/gograb-dev/src/app/app.ts
libs/libs-ai/vitto-hub/src/lib/components/ai-panel-tabs/ai-panel-tabs.component.ts

🔗 Related

Decision ID: dev_1770832783483_hr9et0f
Session: 105
Workspace: gspace1

Auto-generated by MCP Smart Consolidation