Windows Computer Use: launch_app fails with "node_repl exec context not found" after healthy read calls

Summary

On Windows, Computer Use can retain a healthy enough runtime for list_windows() and list_apps() while every attempt to relaunch an absent desktop application through launch_app() fails with the internal error:

Error: node_repl exec context not found

This prevents the documented recovery path when the required target application is no longer running.

Environment

• Codex Desktop on Windows
• Provenance-attested personal Computer Use wrapper
• Target application used for reproduction: Omnissa Horizon Client
• Filesystem permission profile: unrestricted

Reproduction

1. Initialize the provenance-attested Computer Use runtime.
2. Call list_windows() and list_apps(); both return normally, but the target application is absent.
3. Attempt the documented explicit executable launch:

await sky.launch_app({
  app: "C:\\Program Files\\Omnissa\\Omnissa Horizon Client\\horizon-client.exe",
});

4. Observe Error: node_repl exec context not found.
5. Dispose the Computer Use runtime, reset the Node REPL kernel, initialize a fresh runtime, and retry. The same error occurs.
6. Retry with the previously returned process-style application identifier. The same error occurs.
7. Reinitialize and call list_windows() or list_apps() again; read-only enumeration still succeeds.

Expected behavior

launch_app() should start the executable and return normally. If the executable cannot be launched, it should return an application-specific launch error that identifies the failed operation.

Actual behavior

launch_app() fails with an internal Node REPL execution-context error. A clean runtime reset does not repair it, while read-only application/window enumeration remains functional.

Impact

An agent cannot follow the documented recovery path for an absent target application. Continuing would require an unrelated UI or shell fallback, which may be unavailable or inappropriate under Computer Use routing rules.

Additional observations

• The failure is narrower than reports where the entire Node REPL or Computer Use runtime cannot initialize.
• Both the explicit .exe path and process-style identifier reproduce the error.
• No application window existed to approve or target after the failed relaunch.

Start by reproducing the Windows sequence with the Computer Use runtime: compare launch_app() with the successful list_windows() and list_apps() calls, then retry after disposing the runtime and resetting the Node REPL kernel. No source file or test is identified in the report, so locate the launch_app and Node REPL execution-context entry points first. Done means the executable launches normally or returns a specific application launch error instead of the internal context error.