Windows-control connection isn’t available in this task on computer use

Open
#35,403 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust

Research direction

Start by reproducing the issue with the computer use plugin and server setup enabled: tag computer, then open Notepad on Windows. Trace why the Windows-control connection is unavailable and when the standard local app launcher is selected as fallback. Done means computer use opens Notepad without the repeated connection error.

Written by the indexing model from the issue text.

Description

app bug computer-use windows-os
What version of the Codex App are you using (From “About Codex” dialog)?

Version 26.721.41059

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Unable to apply computer use. I am getting this error message repeatedly "Windows-control connection isn’t available in this task on computer use". I have computer use plugin and server setup already enabled. I tried almost everything like clearing caches, plugins, uninstalling and so on but did not work anything.

What steps can reproduce the bug?

Step 1: tag computer (to define computer use)
Step 2: open notepad
Got this message: I’m using the Computer Use skill to open Notepad. The dedicated Windows-control connection isn’t available in this task, so I’m using the standard local app launcher as the fallback.

What is the expected behavior?

Notepad should open with "computer use" feature

Additional information

No response

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.