🐛 Bugfix: Why does autoFlashState persistence fail in gograb-ai? Sessi...

Date: 2026-02-21
Time: 21:12:47 UTC
Session: gspace1-133.19
Agent: storage
Confidence: 99%
Status: ✅ Documented

📋 Decision Context

Question:

Why does autoFlashState persistence fail in gograb-ai? Sessions and chat messages are lost on every page refresh.

Task: Not specified

🎯 Decision Made

Chosen:

Add provideIntelligentStorage to gograb-ai app.config.ts

Options Considered:

1. Add provideIntelligentStorage to gograb-ai app.config.ts
2. Use localStorage directly instead of autoFlashState
3. Add a custom IndexedDB persistence layer

💭 Reasoning

Root cause: gograb-ai was MISSING the storage system provider entirely. Without provideIntelligentStorage (or provideAutoFlashPersistence), the FlashStateHydratorService has no IndexedDB backend registered. It falls back to createFallbackStorage() which uses localStorage — unreliable, size-limited, and silently loses data. The fix is adding ...provideIntelligentStorage({ namespace: 'gograb-ai' }) to the providers array, same as gograb-space has. This registers the IndexedDB adapter, enables autoFlashState to properly persist and hydrate, and fixes session/message persistence across refreshes. The error was completely silent — autoFlashState catch blocks only console.warn, making it invisible.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1771708367654_wfka9sg
• Session: 133
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation