Single-tab management: switch to localStorage-based

[mnm-matin]

Switch to LocalStorage-based single tab management

Problem:
Current multi-tab detection forces users to close the original tab when opening the app in a new tab, leading to poor UX as users must manually hunt down and close tabs.

Solution:
Replace the BroadcastChannel implementation with a simpler LocalStorage-based approach, inspired by WhatsApp Web's tab management:

• New tabs automatically become active
• Existing tabs show "Use here" prompt instead of forcing closure
• Simplified code with fewer dependencies and edge cases

Changes:

• Rewrote useSingleTabEnforcer to use localStorage and the storage event
• Updated ProviderSingleTab to show a WhatsApp-style "Use here" button
• Eliminated complex state management, timers, and race condition handling

Testing:

• Open multiple tabs - verify only one is active
• Click "Use here" - verify tab becomes active and others show prompt
• Close active tab - verify another can claim ownership

[vercel]

@mnm-matin is attempting to deploy a commit to the Token Fabrics Pro Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
big-agi-open-next	Error		Sep 12, 2025 10:11pm
open-v2-dev	Error		Sep 12, 2025 10:11pm

[enricoros]

Thanks for the pr @mnm-matin very smart solution!

I'd merge it right away, but need to take some time to merge this because it's on the critical path for the new boot sequence that will be present in the upcoming version (and needs careful initialization and dependency between components, including this). So I'll have to revisit this once I release the very large change I'm working on.

Thanks for submitting!

[mnm-matin]

np, happy to contribute to a great project with super responsive devs 🚀🚀