Codex App: detachable workspace panels for documents, review, browser, and computer use

Open
#34,720 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Domain
desktop

Research direction

Start by tracing how the App opens Documents, Review, Files, Browser, and Computer Use surfaces, and where window size and position are managed. Done means a detached mode can reuse a separate window, remember its size and position, and return the surface to the main Codex window without forcing the chat window wider.

Written by the indexing model from the issue text.

Description

app browser computer-use enhancement
What variant of Codex are you using?

App (and CLI, but this is for the codex app).

What feature would you like to see?

The Codex chat is useful at a relatively compact window size, but opening documents, Review, Files, Browser, or other workspace surfaces forces the whole app to become much wider.
It would be useful to detach these secondary surfaces into their own windows:

  • Keep the main chat window compact (or in the size you set).
  • Open a document or tool in a separate window when detached mode is enabled.
  • Remember the detached window’s size and position.
  • Reuse the same detached window for subsequent documents/tools.
  • Allow toggling the surface back to the main Codex window.
  • This would also be useful for giving Browser or Computer Use agents more screen space without making the chat window permanently large.
Additional information

If needed, I can share some Screenshots of the little problem. It's not really a problem, but adds friction.
Thanks for considering!
Codex is evolving into an amazing product, tell Tibo he is the goat.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.