Add Safari support to the Codex browser extension on macOS

What variant of Codex are you using?

Codex App on macOS

What feature would you like to see?

Please add first-class Safari support to the Codex browser extension on macOS, including tab mentions and browser control for signed-in workflows. The current extension supports Chromium-based browsers but not Safari.

Safari support would give Mac users a native-browser option and let them choose the browser that performs best for long-running operational workflows.

Additional information

In a controlled Hostaway inbox comparison on this Mac, Chrome showed sustained resource use: the legacy inbox measured 16.4–21.9% CPU and 331–345 MB memory, while the new inbox measured 22.8–44.6% CPU and 479–491 MB. Safari/WebKit support would let users compare and potentially reduce that overhead while retaining Codex automation capabilities.

I searched the existing open issues for Safari browser-extension support and did not find a direct duplicate.

Start by locating the existing Chromium-based browser extension and its Codex App on macOS integration, then trace how tab mentions and browser control are exposed. Done means delivering first-class Safari support for signed-in workflows and documenting or testing the supported Safari behavior; the issue names no files or tests.