Repository navigation
Codex Desktop Computer Use plugin visible but runtime tools are not injected #29921
Description
Environment
- Codex Desktop: 0.142.0
- OS: Windows
- Model tested: GPT-5.5 Medium
- Computer Use plugin: installed, visible in Settings, and enabled
- Repository / project context: local Codex Desktop thread
Problem
When I start a new thread with @Computer, Codex recognizes the Computer Use plugin label and can read the plugin SKILL.md, but the actual callable Computer Use runtime tools are not available in the thread.
The model can explain that Computer Use should use node_repl/js and the sky runtime, but it cannot actually call those tools.
Missing tools / capabilities
The new @Computer threads do not expose:
mcp__node_repl__jsnode_repl jsjs_resetsky.list_apps()sky.list_windows()get_window_state()
Expected behavior
A new @Computer thread should expose the Computer Use runtime so Codex can call sky.list_apps(), select a window, capture it with get_window_state(), and interact with Windows apps.
Actual behavior
The model says the plugin is present but no Computer Use execution tools are available. It either reads the Computer Use SKILL.md, searches for node_repl/js, or says the tools are not injected. It cannot screenshot or control Windows windows.
Local checks
Plugin files exist locally:
C:\Users\11815\.codex\plugins\cache\openai-bundled\computer-use\26.609.41114
C:\Users\11815\.codex\plugins\cache\openai-bundled\computer-use\26.609.41114\scripts\computer-use-client.mjs
config.toml includes:
js_repl = true
[plugins."computer-use@openai-bundled"]
enabled = true
[marketplaces.openai-bundled]
source_type = "local"
source = '\\?\C:\Users\11815\.codex\.tmp\bundled-marketplaces\openai-bundled'Troubleshooting already tried
- Reinstalled Codex Desktop
- Restarted Codex Desktop
- Fully exited Codex processes
- Opened new threads
- Disabled/re-enabled Computer Use plugin
- Confirmed plugin files exist locally
- Confirmed Computer Use appears in Settings
- Restored
openai-bundledmarketplace and plugin cache - Tried explicit prompts asking not to use shell / PowerShell /
Get-Process
Important observation
The plugin is visible in Settings, so installation/discovery appears to work. The failure is specifically that the Computer Use runtime tools are not injected into the model/tool list for new @Computer threads.
Request
Please investigate why Codex Desktop on Windows is not injecting node_repl/js or the Computer Use sky runtime tools for enabled Computer Use plugin threads.
Activity
github-actions commentedon Jun 24, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
loveq8888 commentedon Jun 26, 2026
I am seeing the same issue on Windows Codex Desktop.
Feedback ID: 019f0240-11b0-7922-b18a-a99d61013412
Summary:
Computer Use plugin is installed and enabled, but the privileged Computer Use node_repl/nativePipe runtime is not injected into agent sessions.
Manual node_repl MCP can expose node_repl/js, but it is not privileged:
{
"hasNodeRepl": true,
"hasConfig": false,
"hasNativePipe": false,
"nodeReplEnvKeys": [],
"nodeReplNodeModuleDirs": null,
"skyNativePipeDirectory": null
}
computer-use-client.mjs fails with:
Windows Computer Use Sky runtime is unavailable
Codex Desktop: OpenAI.Codex 26.616.10790.0
Computer Use plugin: 26.616.51431
Windows sandbox is set to unelevated.
etoqeyeyise49-lang commentedon Sep 30, 2026
Additional Windows observation on September 30, 2026, using Codex Desktop 26.928.21956: two independently created local tasks delegated by dot had Computer Use instructions available but no callable UI execution tools.
Reproduction:
The second task inspected its exposed catalog of 330 tools and found no matching execution tool or tool-discovery entry point. Neither task obtained a desktop screenshot. The failure occurred before native-window enumeration or capture, rather than as a failed screenshot call.
Read-only local diagnostics showed node_repl and cua_repl reaching ready status in other task contexts. This does not establish that either affected delegated task received usable tools. Separate conversation-resume/remote-transport errors were also observed; their relationship to missing tool exposure is unproven.
Expected: an eligible local task should receive the supported Computer Use execution interface. If dot-created tasks are unsupported or subject to a capability gate, please surface that explicitly rather than providing skill instructions without callable tools.
Verification limits:
Could maintainers clarify the supported diagnostic/recovery path for tool registration and capability propagation into dot-created Windows tasks? The recovery criterion is a fresh delegated task receiving callable tools and capturing an actual read-only desktop screenshot.
Private identifiers, local paths, credentials, screenshots, and raw logs are omitted.