Windows: Computer Use works in local @Computer session but tools are absent in dot-delegated tasks after reboot #49588

Summary

Computer Use works in an ordinary local Windows desktop session when explicitly invoked with @computer, but tasks started on the same authorized computer by a dot do not receive the required Computer Use tool entry points. This is an additional reproduction of the symptom reported in #49458; please consolidate if appropriate.

Environment

• Windows x64, OS build 10.0.26200.0
• Windows package manifest version: 26.928.1915.0
• Application package.json version: 26.928.20755
• Computer Use plugin version: 26.928.20755
• Observed September 30, 2026

The package and application versions were verified as metadata within the same installed package; the difference is not being presented as evidence of mixed installations.

Reproduction and observed results

1. Connect and authorize the Windows computer for dot tasks. Connection, attachment, and task authorization report normal.
2. In an ordinary local desktop session, explicitly invoke @computer. The user confirmed that application enumeration and a window screenshot succeed.
3. Ask the dot to create a task on the same computer and use official Computer Use to enumerate applications and capture a non-sensitive window.
4. The task can execute ordinary local commands and read the installed Computer Use skill, but its exposed tool inventory lacks node_repl, a compatible native Computer Use entry point, and a tool-discovery route for obtaining one. Application enumeration and screenshot capture therefore cannot be attempted through the documented entry point.
5. Reproduce in a fresh delegated task with the Computer Use skill explicitly preloaded: the same omission occurs.
6. Reboot the entire Windows computer, reconnect, and start another turn in the diagnostic delegated task: the entry point is still absent.

Diagnostic observations

Read-only checks found the Computer Use plugin enabled, its runtime present, and a node_repl process running. Recent service logs reported a successful handshake with js and js_reset capabilities. These observations do not establish successful capability routing into the affected delegated tasks, nor do they establish the underlying cause.

Both existing and fresh delegated tasks reported the same missing tool entry points. No persistent security, network, or application configuration changes were made during these checks. No unsupported desktop-control workaround was used.

Expected result

An authorized dot-delegated local task should receive the supported Computer Use tools, or clearly report that this task surface is unsupported and provide the supported activation path. Reading/preloading the skill alone should not leave a task with instructions for unavailable tools without an actionable diagnostic.

Impact

CLI development and tests can proceed, but delegated GUI validation cannot. Local @computer success does not currently provide a usable Computer Use path for the dot's development tasks.

Please investigate capability registration/exposure for dot-delegated Windows tasks. The root cause remains unconfirmed.

This report intentionally excludes private project code, machine names, screenshots, account details, task/conversation identifiers, and raw logs.