Codex Chrome Extension should support user-approved local hostname allowlist for hosts mapped to loopback

What variant of Codex are you using?

App,CLI

What feature would you like to see?

I use Codex Desktop with the Codex Chrome Extension for local web development.

My local dev app must be opened as:

http://dev.alipay.com:8080/#/

because the app behavior and CORS reproduction depend on the real hostname. My /etc/hosts maps this hostname to loopback:

127.0.0.1 dev.alipay.com

Chrome can open the page manually, and curl confirms the local server is reachable. However, Codex Chrome Extension / Browser Use appears to treat this URL as a non-local external hostname. It can list and claim the tab, but content-level operations such as evaluate, DOM reads, screenshots, and navigation hang or time out.

Expected behavior:
Codex Chrome Extension should support a user-approved local hostname allowlist, for example:

dev.alipay.com -> 127.0.0.1

The extension should only allow this when the hostname currently resolves to loopback addresses such as 127.0.0.1 or ::1. If the hostname no longer resolves to loopback, the allowlist entry should not apply.

This would preserve the current security model while enabling local development workflows that require a production-like hostname for CORS, cookies, origin checks, or environment detection.

Observed behavior:

• http://127.0.0.1:8080/#/ works with Chrome Extension automation.
• http://localhost:8080/#/ works with Chrome Extension automation.
• http://dev.alipay.com:8080/#/ is reachable in Chrome and curl, but Chrome Extension content operations time out.

Environment:

• macOS
• Codex Desktop
• Codex Chrome Extension
• /etc/hosts contains: 127.0.0.1 dev.alipay.com

Additional information

_No response_