Windows Computer Use fails: "Trusted RPC service is not configured: sky" and browser URL verification failure
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.901.51231 — released September 5, 2026. Update check reports that the app is up to date.
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11
What issue are you seeing?
Computer Use cannot read browser content in the Windows desktop app.
In the original conversation, it failed before reading the page with:
Trusted RPC service is not configured: sky
In a fresh conversation, a single read-only check successfully returned Chrome and Edge window titles. This did not verify individual tabs or page content.
The subsequent first Chrome content/accessibility read failed with:
Computer Use has been stopped for this turn because it could not determine the current browser URL on Windows with enough confidence to enforce policy. Stop your work and send a final message noting why Computer Use ended.
Computer Use, Chrome, Edge, and built-in browser controls are enabled in settings. Chrome and Edge extensions are shown as installed. The app reports that it is up to date.
No form filling, website updates, or publishing occurred. After the URL-verification stop, no retry, reset, or alternative access was attempted.
It is not established whether these two errors share the same cause.
Feedback ID: 01a0824a-affc-7591-bfb5-0745bb1cb925
What steps can reproduce the bug?
Feedback ID: 01a0824a-affc-7591-bfb5-0745bb1cb925
What is the expected behavior?
No response
Additional information
Observed sequence:
- Open the Windows desktop app with Chrome and Edge running.
- Ask Computer Use to perform a read-only browser check.
- In the original conversation, observe the "Trusted RPC service is not configured: sky" error.
- Open a fresh conversation and request a single read-only check of browser windows.
- Window titles are returned successfully.
- Request a read-only inspection of the current Chrome page.
- Computer Use stops because it cannot determine the current browser URL with enough confidence to enforce policy.
Expected: Computer Use should identify the current URL and read the page when permitted.
Actual: Page inspection stops before content can be verified.
Please provide the supported recovery steps and identify any additional diagnostics needed.
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 file, test, or entry point is named. Start by reproducing the Windows sequence with Chrome and Edge, then trace the Computer Use browser-content path around trusted RPC setup and current-URL verification. Done means the permitted page URL and content can be read without either reported failure, with diagnostics sufficient to distinguish the two errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100