openai / openai/codex

Browser “Always ask” approval setting is ignored; new sites open without prompting

Open
#40,122 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

In the Codex desktop app on Windows, browser approval is set to Always ask, but Codex can open previously unapproved websites without showing an approval prompt.

This is a safety-sensitive failure mode because the restrictive setting appears to fail open.

Expected behavior

When browser approval is set to Always ask, Codex should request approval before opening a new website or domain.

Actual behavior

Codex opens new websites or domains without presenting the configured approval prompt.

Steps to reproduce
  1. Open Codex desktop.
  2. Set browser approval to Always ask.
  3. Ask Codex to navigate to a website or domain that has not already been approved.
  4. Observe that the website opens without an approval prompt.
  5. Repeat with other unapproved domains.
Environment
  • Windows 11 25H2, build 26200.9168
  • Codex desktop 26.818.5229.0
Troubleshooting and evidence
  • Reproduced across multiple websites or domains.
  • The behavior persisted after restart and reset troubleshooting.
  • Session logs and browser logs were submitted through the in-app Safety feedback flow.
  • Further reproduction notes are available privately if needed.
Related issue

Issue #36953 appears related to persistent browser-permission state, but describes the opposite failure mode: a site remains blocked after a rule is removed. This report is separate because Always ask is being bypassed and the behavior fails open.

Additional note

The private in-app feedback receipt has intentionally been omitted from this public issue. It can be provided directly to OpenAI Support or maintainers through a private channel.

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

No files, tests, or entry points are mentioned. Reproduce the issue on Windows with browser approval set to “Always ask,” then trace the desktop browser-permission handling and its treatment of unapproved domains. Done means every new website or domain triggers the configured approval prompt instead of opening automatically.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.