browser-tabs

Prevent browser tab hijacking by enforcing strict tab ownership in a shared browser, requiring each session to capture and reuse the tab's targetId for all navigation and interaction actions.

Tab isolation separates browsing contexts across sessions by using the targetId identifier. Capturing and reusing targetId ensures that browser actions apply only to the correct tab, preventing cross-session state leakage.

Manage browser sessions to avoid state leakage by opening a new tab for each task, capturing its targetId, reusing that targetId for all subsequent actions, and closing the tab when finished to clean up state.

Yes, multi-session browser automation requires capturing targetId to enforce tab isolation, ensuring that opening, navigating, and interacting with tabs remains strictly bound to the correct AI session.

The best way to handle tab ownership is maintaining new-tab discipline: always open new tabs for work rather than reusing active ones, and close them upon task completion to guard against cross-session leakage.

One AI session interferes with another's tabs because of unmanaged tab ownership in a shared browser. Without capturing and reusing targetId, browser actions inadvertently execute on the active tab of a different session.