browser-lease-manager

Browser session bleed is prevented by enforcing a single-owner lease per origin, serializing tab access to stop race conditions and cross-task conflicts. A lease state machine manages active, cooldown, and retired states to ensure deterministic tab ownership.

Browser tab lease management handles automated recovery by tracking health metrics like lastHealthAt and failureCount. The lease state machine transitions through active, cooldown, and retired states, persisting to the user's home directory to enable session handoff across restarts.

Yes, you can maintain browser tab ownership across restarts through session handoff. The lease system persists lease states to the user's home directory, ensuring continuity and deterministic tab ownership even after transient failures or application restarts.

The best way to serialize browser tab access is acquiring a per-origin browser lease. This enforces a single-owner lifecycle for tabs, preventing race conditions and session bleed by managing the tab lifecycle through a state machine with active, cooldown, and retired states.

A lease state machine is needed for browser tab lifecycle management to handle active, cooldown, and retired states automatically. It tracks health with lastHealthAt and failureCount, ensuring automated recovery from transient failures and preventing cross-task conflicts on the same origin.

Yes, per-origin browser lease management works for workflows requiring one active tab per profile. The lease model ensures a single active tab per origin, account, or profile, preventing conflicts and managing session handoff across restarts.