Computer Use native pipe path is unavailable on Windows - plugin disappears and blocks skill execution

Open 💬 1 comment Opened Jun 4, 2026 by sam-hajeri

What version of the Codex App are you using (From “About Codex” dialog)?

26.601.21317

What subscription do you have?

Plus

What platform is your computer?

Windows 11 Windows OS Version (from PowerShell): $([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" }) Please run this command in PowerShell and paste the output here.

What issue are you seeing?

Bug Description

The Computer Use plugin/skill has completely disappeared from the Codex Desktop App. When attempting to use Computer Use to execute tasks that involve browser automation (e.g., creating a new skill to open Edge browser), Codex fails before it can even open Microsoft Edge.

Error Message

The repeated error is:

Computer Use native pipe path is unavailable

This error occurs before Edge can be opened, indicating that the Windows Computer Use helper process or named pipe cannot be initialized.

Context

I attempted to create a custom skill using Computer Use to automate the .................. The skill was successfully created and validated (quick_validate.py returns Skill is valid!), but the live test is blocked because Computer Use fails with the native pipe path error.

The skill files are valid:

  • SKILL.md exists and is valid (includes handling for "Computer Use native pipe path is unavailable" by stopping cleanly)
  • agents/openai.yaml has the correct display name, description, and "....................................." default prompt
  • quick_validate.py passes

This issue is external to the skill files — the repeated blocker is the Windows Computer Use helper native pipe path being unavailable, which prevents any computer use tasks from running.

What steps can reproduce the bug?

  1. Open the Codex Desktop App on Windows 11
  2. Attempt to use the Computer Use plugin/skill
  3. Give Codex a task that requires browser automation (e.g., create a new skill, automate a web portal)
  4. Codex fails before opening Edge with the error:

``
Computer Use native pipe path is unavailable
``

  1. Restart Codex / clean session reset — the error persists
  2. Repeat multiple times — the error remains consistent

Additional detail: The Computer Use plugin initially disappeared from the Codex App interface before this error started appearing.

What is the expected behavior?

  1. The Computer Use plugin/skill should be visible and available in the Codex Desktop App
  2. When a task requiring Computer Use is given, Codex should successfully launch Microsoft Edge and perform browser automation
  3. The Windows Computer Use helper should properly initialize the native pipe path so that automation tasks can execute
  4. Custom skills that depend on Computer Use (like the "............................." skill) should be able to run their live tests without being blocked by the native pipe path error

Additional information

Environment

  • OS: Windows 11
  • Codex App: Desktop version (Version 26.601.21317 • Released 3 Jun 2026)
  • Browser: Microsoft Edge
  • Skill being developed: eservicesportal (custom skill for ............Eservices Portal automation)

Notes

  • This issue may be related to #26387 ("Browser and Computer Use plugins became unavailable in Codex desktop app")
  • The skill creation and validation is complete and working — only the live Computer Use test is blocked
  • The SKILL.md file has been updated to explicitly handle the "Computer Use native pipe path is unavailable" error by stopping cleanly and forbidding unsafe fallback automation
  • The error occurs even after a clean session reset and multiple retries

Related Files Verified

  • C:\Users\saawq\.codex\skills\eservicesportal-............SKILL.md — valid
  • C:\Users\saawq\.codex\skills\eservicesportal-..........\agents\openai.yaml — correct display name, description, and default prompt
  • quick_validate.py — returns "Skill is valid!"

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗