Cloud browser ignores “Always allow” site permissions and repeatedly asks for access
Nobody has claimed this yet.
- 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.903.71938
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
I am seeing repeated cloud-browser permission prompts even though the relevant site permissions are explicitly configured as Always allow.
Configuration
In Site permissions:
- Default → Browsing: Always allow
- Default → Downloads: Always allow
- Default → Uploads: Always allow
- https://espn.com → Browsing: Always allow
- https://espn.com → Downloads: Always allow
- https://espn.com → Uploads: Always allow
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a090e1-3cf1-7fd0-a59f-57a3fb8d30d4
What is the expected behavior?
Expected behavior
Because both the default browsing permission and the explicit espn.com permission are set to Always allow, the cloud browser should access and read ESPN without requiring another ordinary site-access confirmation.
Actual behavior
The cloud browser asks for permission anyway. This occurs before any consequential action and on a simple read-only webpage request.
This makes unattended or scheduled Work tasks unreliable because the task can stop waiting for an approval that has already been granted in Settings.
I have reproduced this after adding an explicit ESPN-specific permission rather than relying only on the default rule.
Screenshots are available showing both the Always allow configuration and the subsequent Allow ChatGPT to access espn.com prompt.
Additional information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are named in the report. Start by reproducing the cloud-browser prompt with the listed default and espn.com “Always allow” rules, then trace the permission decision; done means a previously allowed read-only request no longer prompts and the relevant regression coverage passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authorization, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100