VS Code extension: support multiple independent Codex views in the same window

What variant of Codex are you using?

VS Code extension

What feature would you like to see?

Please allow developers to open more than one independent Codex view inside the same VS Code window.

A practical first version could support two instances:

• one Codex view in the Primary Side Bar;
• another Codex view in the Secondary Side Bar.

Each view should be attached to its own Codex thread/session, so both can remain visible and active at the same time. The goal is not to mirror the same UI in two places, but to let each view follow a different task.

Possible commands could include:

• Codex: New Codex View
• Codex: Open Thread in Primary Side Bar
• Codex: Open Thread in Secondary Side Bar
• Codex: Move Thread to New View

Ideally, users could create additional instances when needed, while still being able to use only one view during simpler workflows.

Why this matters

Codex already supports concurrent work, but the current VS Code interface exposes only one sidebar view. This forces developers to keep switching between threads, open another VS Code window, or use a different interface just to monitor parallel tasks.

A common workflow is:

• one Codex agent implements a feature;
• another Codex agent reviews code, investigates a bug, analyzes tests, or prepares the next change;
• the developer monitors both and answers questions as they appear.

With two visible Codex views, a developer could follow an implementation in one sidebar while simultaneously following a review in the other. This would be especially useful for developers using multiple monitors, ultrawide displays, or complex editor layouts while keeping a single VS Code workspace and window.

Benefits for developers

• Less context switching between active threads.
• Easier supervision of parallel agents.
• Faster responses when one task requests approval or clarification.
• Better separation between implementation and review work.
• No need to duplicate the entire VS Code window.
• The same workspace, terminals, files, source control state, and extensions remain available to both Codex sessions.
• Lower risk of working in the wrong window or losing track of which task belongs to which workspace.

Suggested UX

Each Codex view instance could keep its own:

• selected thread;
• task status and progress;
• input box;
• approval requests;
• unread/activity indicator.

The current single-view behavior could remain the default. Users who need parallel workflows could explicitly create a second view and place it in the other sidebar.

This is complementary to requests for opening Codex sessions as editor tabs, such as #20951, but addresses a different workflow: continuously monitoring two independent Codex sessions side by side without leaving a single VS Code window.