Architecture: How should users be prompted to install the Chrome extension...

Documentation for Sessions

🏗️ Architecture: How should users be prompted to install the Chrome extension...

Date: 2026-02-11
Time: 17:59:54 UTC
Session: gspace1-105.22
Agent: angular
Confidence: 85%
Status: ✅ Documented

📋 Decision Context

Question:

How should users be prompted to install the Chrome extension?

Task: Session 105.3: Extension install prompt

🎯 Decision Made

Chosen:

Shared ExtensionInstallPromptComponent in @libs-ux/embeddable-bridge, added to all 3 app layouts. Non-intrusive bottom banner, dismissible for 7 days.

Options Considered:

Per-app prompts
Shared component in embeddable-bridge
No prompt — just docs

💭 Reasoning

Extension detection via window.GOGRAB_AI_EXTENSION_LOADED (already set by inject.js). The component is shared in embeddable-bridge because embedding is infrastructure, not AI-specific. 7-day dismiss persistence prevents nagging. Shown after a 3-second delay to avoid interrupting initial page load. Placed in all three app layouts so users encounter it regardless of which app they use.

📁 Files Involved

libs/libs-ux/embeddable-bridge/src/lib/components/extension-install-prompt.component.ts

🔗 Related

Decision ID: dev_1770832794302_uhh24w7
Session: 105
Workspace: gspace1

Auto-generated by MCP Smart Consolidation