Skip to content

Regression: Computer Use tool-host missing in Windows app 26.707.12708 / CLI 0.144.5 #33595

Open

Description

@moscowresurs-eng

Computer Use tool-host is not exposed in Codex App 26.707.12708 / CLI 0.144.5

Component

  • Codex Windows desktop app: 26.707.12708.0
  • Bundled Codex CLI: 0.144.5
  • Bundled Computer Use plugin: 26.707.91948
  • OS: Windows 11 Professional, build 26200

Summary

New Codex tasks no longer receive the callable tool-host required by the
bundled Computer Use skill. The skill is discovered and its runtime starts, but
the execution tool described by the skill (mcp__node_repl__js, previously
reached through the code tool-host) is absent from the task toolset.

This worked in a prior session using Codex CLI 0.144.0-alpha.4, where the
session transcript contains real custom_tool_call events for exec and
successful mcp_tool_call_end events for the node_repl server. That session
successfully read the accessibility state of Claude Desktop.

In fresh sessions using CLI 0.144.5, the string mcp__node_repl__js appears
only in the injected Computer Use skill instructions; no callable tool with
that ID is published and no actual tool call can be made.

Steps to reproduce

  1. Install/start Codex for Windows 26.707.12708.0.
  2. Enable Computer Use for applications in Codex settings.
  3. Confirm the bundled Computer Use plugin is enabled.
  4. Start a completely new task after restarting Codex.
  5. Ask the agent to perform a passive Computer Use check, for example:
    list open applications and read the state of Claude Desktop without clicks,
    typing, messages, or model calls.
  6. Observe that the Computer Use skill is available, but the task has no
    callable Computer Use execution interface.

Expected result

The new task exposes the execution tool required by the bundled Computer Use
skill, allowing the documented bootstrap through
scripts/computer-use-client.mjs and then read-only list_apps / app-state
inspection.

Actual result

The skill is listed and readable, but the execution tool is absent. The agent
cannot run the documented bootstrap and must report that Computer Use cannot be
called.

Diagnostics already performed

  • Verified that
    scripts/computer-use-client.mjs exists in the bundled plugin.
  • Verified that the bundled plugin cache matches the plugin shipped with the
    installed Codex app.
  • Verified that the local Computer Use runtime processes start.
  • Verified that computer_use = true, code_mode_host = true, and
    code_mode = true do not restore publication of the tool.
  • Confirmed that the legacy js_repl feature is marked removed; it was not used
    as a workaround.
  • Restarted Codex and reproduced in a newly created task.
  • Repaired an unrelated WindowsApps PowerShell alias problem by installing
    PowerShell 7.6.3 MSI at C:\Program Files\PowerShell\7\pwsh.exe; direct
    PowerShell execution now works, but Computer Use remains unavailable.
  • The failure occurs before screenshot capture or application interaction, so
    it is not a Windows Graphics Capture error.

Regression evidence

  • Working session: CLI 0.144.0-alpha.4
    • real custom_tool_call name=exec
    • successful mcp_tool_call_end for node_repl
    • successful read-only accessibility inspection of Claude Desktop
  • Failing sessions: CLI 0.144.5
    • no exec code tool-host in the task toolset
    • no callable mcp__node_repl__js
    • reproduced after restart in a fresh task

Impact

Computer Use is effectively unavailable even though the bundled plugin,
settings, runtime, and skill are present. This blocks Windows application
automation and also prevents delegating a narrow desktop-control subtask while
keeping the main task on another model.

Privacy

No authentication tokens, cookies, private chat contents, or auth-cache
contents are included in this report.

Activity

  1. added
    bugSomething isn't working
    appIssues related to the Codex desktop app
    windows-osIssues related to Codex on Windows systems
    tool-callsIssues related to tool calling
    on Jul 16, 2026
  2. github-actions commented on Jul 16, 2026

    @github-actions
    Contributor
  3. DKWien commented on Jul 16, 2026

    @DKWien

    Same regression confirmed on Windows App 26.707.12708.0 /
    CLI 0.144.5 / plugin runtime 26.707.91948.

    Feedback ID:
    019f698e-bf47-7473-bbf8-996ffce6f1e8

  4. moscowresurs-eng commented on Jul 17, 2026

    @moscowresurs-eng
    Author

    CORRECTED / partial recovery observed on 2026-07-17:

    The original missing-tool-host condition is no longer current in this session. The callable Node/Computer Use surface is now exposed in the same Codex Windows installation.

    Environment:

    • Codex Windows package: 26.707.12708.0
    • Computer Use plugin: 26.707.91948
    • Windows 11 Professional build 26200
    • bundled Node runtime selected by Codex log: 24.14.0

    Passive test matrix:

    • list_apps: PASS
    • list_windows: PASS
    • get_window for packaged Claude Desktop: PASS
    • get_window for a Chrome control window: PASS
    • get_window_state for packaged Claude Desktop: TIMEOUT / no response
    • get_window_state({ include_screenshot:false, include_text:true }) for packaged Claude Desktop: TIMEOUT / no response
    • the same accessibility-only get_window_state for the Chrome control window: TIMEOUT / no response

    This narrows the current fault downstream of helper discovery, enumeration, and canonical window-handle resolution. It is not limited to Graphics Capture and is not Claude-specific, because accessibility-only state also hangs and the Chrome control reproduces it.

    The bundled computer-use-client.mjs transport keeps pending JSON-RPC requests without an internal timeout, so a missing native-helper response leaves the caller pending indefinitely.

    No window activation, focus change, click, key input, message, screenshot content, token, cookie, or auth-cache content was included in this test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appbugSomething isn't workingcomputer-usetool-callsIssues related to tool callingwindows-osIssues related to Codex on Windows systems

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions