frontend-multi-tab

Isolating multiple frontend sessions within a single page requires a container-driven architecture with a factory-based TabState generator. This provides independent per-tab state and backend connections, preventing cross-talk between parallel workspaces.

Yes, you can maintain separate WebSocket connections per tab without backend changes. The architecture uses hidden persistent sessions to keep background connections alive, avoiding reconnect delays when switching between multiple isolated instances.

The best way to manage per-tab state isolation is using reusable TabBar and VibeSession components with a factory-based TabState generator. This ensures each tab maintains its own lifecycle and state independently within the shared container.

Yes, this multi-tab UI pattern supports multiple terminal panels and independent API clients. Each tab runs its own backend instance, making it suitable for multi-window chats and parallel workspaces with complete UI isolation.

Hidden persistent sessions prevent reconnect delays by keeping background WebSocket and HTTP connections alive in the DOM. When switching back to a tab, its state and connection remain active, ensuring seamless transitions without re-establishing network links.