[macOS app] Website card “Open in” stalls on local HTML loading screen while inline file link works

What version of the Codex App are you using?

26.908.70816, build 9275, bundle identifier com.openai.codex. Verified from the installed application's metadata, rather than the About dialog.

What subscription do you have?

Not included.

What platform is your computer?

macOS 26.5.2, Apple Silicon (arm64).

What issue are you seeing?

Two ways of opening an intended local HTML artifact in the desktop app produce different results:

• Using the generated Website card's Open in action opens a view that remains on the HTML page's initial loading message for more than 20 seconds, without visible startup progress.
• Clicking the blue inline file link in the conversation opens a working interactive preview inside Codex.

The affected user identified this difference manually. No HTML changes were made between the failing and successful observations.

What steps can reproduce the bug?

Observed workflow in the affected existing task; a reduced public reproduction has not yet been established:

1. Have a local, self-contained interactive HTML artifact available in a Codex task, with a generated Website card and an inline file link.
2. Open it through the Website card's Open in action.
3. Observe the page remaining at its initial loading screen.
4. Open the intended artifact through the inline file link in the conversation.
5. Observe that it loads and becomes interactive inside Codex.

The exact destination and execution context used by the card were not captured, so byte-for-byte identity of what the two views actually loaded has not been verified.

What is the expected behavior?

Both entry points should open the intended current artifact and allow it to initialize. If an entry point cannot run the artifact, it should give an actionable explanation instead of appearing to load indefinitely.

Additional information

The cause is unconfirmed. Please compare the Website card's opening route with the inline local-file link route, including target resolution and preview initialization.

This report intentionally excludes source code, project names, repository details, local paths, screenshots, assets, logs, account information, and task/session identifiers. No project files are attached.

Related but not identical: #32078 concerns Windows and reports failures for multiple opening routes; this report concerns macOS with a working inline file link.

No source files, tests, or project entry points are identified in the report. Start by comparing the Website card's Open in route with the inline local-file link route on macOS, then reproduce the differing behavior and verify that both open the intended current artifact or provide an actionable error.