Feature Request: Allow Computer Use and browser activity to be restricted to selected displays

What variant of Codex are you using?

Codex desktop app on macOS (Computer Use and Chrome/browser use)

What feature would you like to see?

Please add an officially enforced display allowlist for Computer Use and browser activity in the Codex desktop app.

Problem

I regularly use a MacBook connected to external monitors. During meetings, the built-in display may be shared with other participants. I want Codex to continue working on an external monitor without any possibility of Computer Use or browser activity appearing on, focusing, or otherwise interacting with the screen-shared display.

The same boundary is useful outside meetings: it lets users reserve a display as a clean, uninterrupted workspace while Codex operates elsewhere. Prompt instructions can express this preference, but they do not provide a dependable product-level boundary.

Desired behavior

Let users select which active displays Computer Use and browser tools are permitted to use. The restriction should be enforced by the tooling and should cover:

• Viewing or capturing a disallowed display
• Clicking, typing, focusing, or scrolling on it
• Opening, moving, or resizing windows onto it
• Pop-ups, authentication dialogs, permission prompts, downloads, and newly launched applications
• Windows that partially overlap a disallowed display

If every allowed display disconnects or the display topology changes unexpectedly, the task should pause and ask the user what to do. It should never silently fall back to a disallowed display.

A persistent setting with an optional per-task override and a visible indicator of the currently allowed displays would make the boundary easy to understand and audit.

Additional information

Example setup: a MacBook built-in display plus two external monitors. The built-in display is used for a meeting or focused personal work, while one or both external monitors are available to Codex.

Displays should be resolved from current system metadata rather than display order or a previously observed numeric ID, since IDs, coordinates, and topology can change after reconnecting or rearranging monitors.

This is primarily a privacy and workflow-isolation request, not only a window-placement preference. When a display is excluded, the user should be able to rely on a fail-closed guarantee that Computer Use and browser activity cannot expose content or interrupt work there.