[Windows][Browser Use] Session-owned tab cleanup aborts active uploads at turn completion

Environment

• Codex/ChatGPT desktop app on Windows
• Bundled Browser Use / Chrome plugin version: 26.915.31945
• Existing signed-in Chrome/Comet session

Problem

Tabs created with Browser Use are automatically closed when the assistant finishes its turn or releases the browser-control session. This can silently cancel a user-visible operation that is still running in that tab, such as a large support-file upload.

The automatic cleanup is not communicated to the user or agent, and there is no apparent persist, detach, or handoff mechanism for a session-owned tab.

Reproduction

1. Use Browser Use to create a new Chrome tab with browser.tabs.new().
2. Navigate to a third-party support form.
3. Select a large local file using the site's native file picker and begin uploading it.
4. Return a final assistant response while the upload is still in progress.
5. The controlled tab closes automatically and the upload is aborted.

This reproduced more than once in the same task. Reopening the support page showed that the upload had not completed.

Expected behavior

One of the following:

• A tab with an active upload remains open after turn completion.
• Browser Use exposes an explicit persist / detach / handoff operation that converts a session-owned tab into a user-owned tab.
• The runtime blocks turn completion or clearly warns that pending work will be destroyed.
• Newly created tabs persist by default unless the agent explicitly closes them.

Actual behavior

The tab is silently cleaned up at normal turn completion, aborting the user's upload and losing progress.

Impact

This is especially disruptive for support bundles, cloud uploads, long-running exports, payment redirects, or any workflow where the user must continue interacting with a tab after Browser Use finishes. It also makes it difficult for an agent to safely hand control back to the user.

Suggested fix

• Track pending navigation/download/upload activity before session cleanup.
• Add an explicit tab lifecycle API such as tab.persist() or browser.tabs.detach(tabId).
• Clearly distinguish session-owned and user-owned tabs in the API/documentation.
• Never silently close a tab with an active upload; require explicit close or a confirmed cancellation.

Start with the browser.tabs.new() reproduction and trace the session cleanup performed at turn completion. Done means an active upload is not silently aborted, or an explicit persist, detach, handoff, warning, or confirmed cancellation path is implemented and verified with the described upload scenario.