Computer Use selects the browser-only runtime instead of the native Windows connector
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.908.40834
What subscription do you have?
Full access (Plus Subscription)
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
Bug: @Computer routes native Windows requests to a browser-only CUA runtime.
When I invoked @Computer in Codex Desktop for Windows and asked it to access any native Windows application, the active connector reported:
- Native apps: none
- Desktop windows: none
- Browser tabs: none
- Native app controls: unavailable
This was incorrect: the Windows desktop was present and the native Computer Use helper was running. Initializing @oai/sky in the active browser-only session also failed with: Trusted RPC service is not configured: sky.
The problem is not specific to LM Studio or any other target application. It is a connector-routing/configuration problem.
What steps can reproduce the bug?
Feedback ID: 01a09a73-4933-7411-ae67-3e843311dacb
What is the expected behavior?
When a user invokes @Computer for a Windows desktop task, Codex should automatically select the native Computer Use runtime and expose the Windows app/window APIs. The request should not be routed to a browser-only cua_repl session, and restarting Codex should not regenerate a browser-only surface when the native computer-use plugin is enabled.
Additional information
The native runtime used CUA_REPL_ENABLED_SURFACES=browser,computer and trusted the sky service (@oai/sky/service). It successfully returned the installed-app inventory and controlled Calculator; the display changed from 0 to 7 after a native click. No credentials, personal files, or sensitive data were entered or uploaded. This is a Codex app/plugin routing issue, not an LM Studio issue.
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 by reproducing the Windows case using feedback ID 01a09a73-4933-7411-ae67-3e843311dacb, then trace @Computer routing between the browser-only cua_repl session and the native Computer Use runtime. Check the CUA_REPL_ENABLED_SURFACES setting and @oai/sky/service configuration; done means native Windows apps and windows are exposed instead of browser-only surfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100