Why is the browser session still running after my code finishes?

A cloud browser session may remain active after code finishes or a connection closes, so it needs to be ended explicitly. In the Browser playground, completing a code run does not close the session. Click Stop when you no longer need it and confirm that it has ended.

In the playground: click Stop when you no longer need to view or interact with the page.

With the SDK: put session.close() in a cleanup path such as finally so closing is attempted after success, failure, or cancellation.

If your program exits unexpectedly: sign in and check the current project in session management. Close sessions you no longer need and confirm they are no longer active.

If closing fails, check the session’s actual status before retrying. Ending sessions promptly releases their concurrency slots.