Session Lifecycle
Follow a Cloud Browser session from startup through readiness, takeover, recovery, and close.
A Cloud Browser session has one authoritative identity and a bounded lifetime.
Starting
Noxgild allocates hosted browser resources and returns a session ID. Keep that ID while the session becomes ready.
Ready and active
Once ready, the same session carries navigation state, browser state, viewer access, and the current controller.
Human takeover
Human takeover changes who controls the existing session. It does not create another browser session.
Recovery
When supported, runtime recovery can replace an unhealthy runtime while preserving the logical session identity.
Closing
Close the session when the work is finished. After closure, do not treat stale viewer frames as an active browser.
See Start a session and Viewing and control.