openai / openai/codex

Windows Browser Use fails before reading attached Chrome tab: "Unable to load browser request-header policy"

Open
#44,112 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment

  • Windows 11
  • Codex desktop app
  • ChatGPT browser extension for Chrome
  • Chrome extension side panel opens successfully
  • Chrome is shown as connected in Settings → Computer Use
  • The target domains are not present in the blocked-sites list

Issue

Codex can see the metadata of an explicitly attached Chrome tab, including its tab ID and URL, but cannot connect to or read the page.

Exact error:

Unable to load browser request-header policy. Retry the browser command.

Steps to reproduce

  1. Open https://vk.ru/target_vk63 in Chrome.
  2. Open the ChatGPT extension side panel.
  3. Open the current Codex task in the side panel.
  4. Explicitly attach the selected Chrome tab to the task.
  5. Ask Codex to inspect the page.
  6. Browser Use fails before reading or interacting with the page.

Troubleshooting completed

  • Confirmed that vk.ru and vk.com are not in the blocked-sites list.
  • Restarted the Browser Use session.
  • Retried direct tab connection by tab ID.
  • Tried both the built-in browser and browser-extension route.
  • Confirmed independently that https://vk.com/ and https://vk.ru/target_vk63 are reachable from the same computer and return HTTP 200.
  • The issue occurs before target-page content is read.

Expected behavior

Codex should connect to the explicitly attached Chrome tab and either read it or display a clear site-specific permission request.

Privacy

No authentication data, cookies, access tokens, account identifiers, or page content are included in this report.

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 by reproducing the attached Chrome-tab flow on Windows and trace the Browser Use entry point that loads the browser request-header policy. Compare the built-in browser and browser-extension routes, then verify that the attached tab can be read or that a clear site-specific permission error is shown.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.