Codex Desktop does not provide the Computer Use tool/plugin
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- desktop
Research direction
The report names Codex Desktop on Windows, the in-app browser, Computer Use, and agent-browser; begin by verifying whether the capability is supported and how these paths relate. Investigate the stated account, rollout, version, and region questions, and consider the issue complete when supported behavior and enablement steps—or an explicit limitation—are documented.
Written by the indexing model from the issue text.
Description
Description
I am using Codex Desktop on Windows. The in-app browser can be opened and browser comments can identify selected page elements, but Codex does not have a callable Computer Use/browser-control tool in the task. As a result, it can see the selected element but cannot click or interact with the current in-app browser tab.
I also tried the available browser automation path, but the agent-browser command was not available in the environment. This appears to be different from controlling the existing in-app browser tab anyway.
Expected behavior
Codex should either:
- provide the Computer Use/browser-control capability for the in-app browser, or
- clearly explain how to install or enable it.
Questions
- Is Computer Use currently supported in Codex Desktop for Windows?
- Is it a built-in capability, plugin, skill, or connector?
- How can I enable it for the current task?
- Are there account, rollout, version, or region requirements?
Environment
- Product: Codex Desktop
- OS: Windows
- Observed on: July 24, 2026
I can provide version information or diagnostic logs if needed.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
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.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·