openai / openai/codex

macOS: Computer Use blocks public WeChat articles while Chrome settings remain accessible

Open
#45,571 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug computer-use
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Summary

On macOS, Computer Use can inspect Chrome settings, but switching to an already-open public WeChat article terminates the tool session with a URL restriction. Browser settings show default browsing and downloads as Always allow.

Environment

  • Desktop app: 26.908.40834 (build 8881; bundle identifier com.openai.codex)
  • Google Chrome: 152.0.7977.84
  • Cached browser, chrome and unified-computer-use packages: all 26.908.40834, enabled in configuration
  • Chrome latest points to 26.908.40834

Reproduction

  1. Open https://mp.weixin.qq.com/s/YosYRQRrfaexYoPheYDBrA in Chrome.
  2. Ask the agent to inspect the public article and save its sheet music as a PDF.
  3. Computer Use can read chrome://settings/system.
  4. Switch to the existing article tab using Computer Use.
  5. The tool stops with: "This session has been stopped because Computer Use is not allowed on the current browser URL."

Additional observations

Earlier in the same workflow, Computer Use successfully displayed the title and sheet music screenshot of https://mp.weixin.qq.com/s/APx_DR_ORDCzERuR6POF4Q . Subsequent article access was refused. Rechecking after the user adjusted permissions produced the same refusal. No URL-policy bypass was attempted.

Expected behavior / question

Please clarify whether this is an intended domain restriction or an unexpected policy result. If access must be denied, an actionable explanation identifying the relevant policy category would help avoid repeatedly changing unrelated permissions.

Related reports

  • #27560: similar WeChat-domain rejection on Windows with mismatched plugin versions. We did not find that version mismatch here.
  • #24814: manually visible pages rejected for agent access on Windows.

These are symptom comparisons, not a confirmed common root cause. No private logs, account identifiers or screenshots are attached.

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 Computer Use URL-policy check that stops sessions on the current browser URL, then reproduce the behavior using the listed public WeChat article and Chrome settings steps. Compare the result with related issues #27560 and #24814. Done means determining whether this domain is intentionally restricted and providing an actionable policy-category explanation if access is denied.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, rust
Domain
desktop, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.