Feature: Isolate browser sessions per task or project
Problem
The in-app browser appears to share cookies and other website session data across Codex tasks. This prevents parallel tasks from using different accounts on the same service.
Example:
- Task A signs in to
example.comwith Account A. - Task B signs in to the same site with Account B.
- Returning to Task A shows Account B's session.
This is inconvenient and can also cause actions to be performed in the wrong customer, organization, test, or production account.
Requested feature
Add selectable browser-session isolation:
- shared, matching the current behavior
- isolated per project
- isolated per task
An isolated context should have its own cookies, local storage, and authentication state. The selected mode should be visible in the UI.
Expected behavior
Task A can remain signed in as Account A while Task B uses Account B on the same website.
Related issues
- #39552 notes that in-app browser tabs share one persisted storage partition.
- #23314 requests multiple browser tabs, which does not provide cookie isolation.
- #21145 requested external browser profiles; this request is specifically about isolation inside the in-app browser.
Feedback requested
Is this only my workflow, or would others also benefit from per-task or per-project browser sessions? I would especially be interested in use cases involving multiple customers, organizations, environments, or user roles.
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Thanks for the suggestion. I reviewed #40117, but I believe the use cases are distinct.
#40117 requests temporary private sessions whose state is discarded when closed. This issue requests persistent, isolated browser sessions per task or project so multiple accounts on the same service can remain signed in and be used concurrently.
The underlying browser-context isolation may be related, but the required lifecycle and expected behavior are different.