Browser security check unavailable; browser and task-coordination tools later missing
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)?
Version 26.903.71938
What subscription do you have?
Pro Plan
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
An existing project workflow is blocked because the assistant cannot operate the in-app browser or communicate with existing task conversations.
The browser tool previously returned this error when attempting to open a GPT editor page:
"Browser Use could not complete this action because a browser security check was unavailable. The admin-enforced policy could not be verified, so access was not granted."
In subsequent checks, browser-operation and task-coordination tools were no longer available to the assistant in this session. It is unknown whether this later tool unavailability shares the same root cause as the original browser error.
The user can manually open and access the relevant conversations. A signed-in browser tab is also open, but the assistant reports that it has no tools available to inspect or interact with it.
Troubleshooting already completed:
- Restarted the application.
- Restarted the entire computer.
- Checked the assistant's available tools again; browser-operation and task-coordination tools remained unavailable.
Expected behavior:
The assistant should be able to use authorized browser and task-coordination capabilities, subject to applicable security policies, or receive actionable guidance explaining why they are unavailable.
Actual impact:
The existing workflow cannot proceed with its required configuration checks, controlled QA execution, and task handoffs.
Please investigate the failed policy verification and the unavailable tools. We are not requesting that security controls be disabled or bypassed.
Feedback ID: 01a0889e-a87f-79e1-ad90-61bc378a24d7
What steps can reproduce the bug?
Feedback ID: 01a0889e-a87f-79e1-ad90-61bc378a24d7
What is the expected behavior?
When allowed by account and workspace policies, the assistant should be able to use the in-app browser and communicate with existing task conversations.
If these capabilities are unavailable or restricted, the app should provide an actionable explanation distinguishing a policy restriction from a technical failure, including the supported recovery steps.
Security controls should remain enforced. We are not requesting a bypass.
Additional information
The application and the entire computer have already been restarted. Browser-operation and task-coordination tools remain unavailable to the assistant in the affected session.
The user can manually access the relevant conversations and browser pages. This does not establish that the assistant has the same access.
Impact: the project workflow is blocked at required configuration checks, controlled QA execution, and task handoffs.
An in-app feedback report was successfully submitted:
01a0889e-a87f-79e1-ad90-61bc378a24d7
The root cause is unknown. Please clarify whether this is a policy-verification service failure, a session/tool-availability issue, or another problem, and provide supported recovery steps.
Private project content and conversation URLs have been omitted from this public report.
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
Start with the reported Feedback ID 01a0889e-a87f-79e1-ad90-61bc378a24d7 and the reproduction details for the Codex App session on Darwin. Trace whether the browser security-check failure and later tool unavailability share a cause. Done means identifying the failure category and providing supported recovery guidance without weakening security controls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100