openai / openai/codex

Chrome extension reads outer Haravan page but cannot access #app-embed-iframe

Open
#40,205 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app browser bug
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of the Codex App are you using (From “About Codex” dialog)?

26.818.41705 (build 6971)

What subscription do you have?

Plus

What platform is your computer?

Darwin 25.5.0 x86_64 i386

What issue are you seeing?

The ChatGPT/Codex Chrome side panel connects successfully and can read the outer Haravan admin page, but it cannot access the content inside #app-embed-iframe on the Haravan theme editor.

The outer page title, navigation, store name, and theme name are returned correctly. However, no iframe content is exposed: no file tree, filenames, CodeMirror editor text, or inner controls.

The Chrome plugin and extension were cleanly reinstalled once, the same Chrome profile is being used, and umacha.myharavan.com is allowed. The problem still occurs.

No edits, saves, or publishing actions were attempted.

What steps can reproduce the bug?

Feedback ID: 01a02d80-8670-7d00-87c3-0399d3ad7e97

What is the expected behavior?

After website access is approved, Codex should be able to inspect the inner content of #app-embed-iframe, including the theme file tree and editor text, or return a clear supported-access error explaining why the iframe cannot be reached.

Additional information

Feedback ID: 01a02d80-8670-7d00-87c3-0399d3ad7e97

ChatGPT macOS app version: 26.818.41705
Build: 6971
Platform: Darwin 25.5.0 x86_64 i386

The same Chrome connection can read full content from normal Haravan admin pages such as /admin/dashboard/activities. The limitation appears specifically when content is embedded inside #app-embed-iframe.

A clean reinstall was performed once. Repeating the reinstall did not appear appropriate because the outer-page connection is already working.

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.

Research direction

Start with the Chrome side panel's website-access handling and reproduce against the Haravan theme editor using the #app-embed-iframe selector and the provided Feedback ID. Compare access to the outer admin page with the iframe content; done means the theme file tree and editor text are exposed, or a clear supported-access error is returned.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.