Skip to content

Windows: dot-started tasks fail with “setup refresh had errors”, but direct local Codex chats work #51882

Description

@Whanzo

What version of the Codex App are you using (From “About Codex” dialog)?

26.1002.52244

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

My dot assistant can no longer execute commands on my connected Windows PC. Both existing tasks and newly created diagnostic tasks fail before even a basic Get-Location command runs.
Exact error:
exec-server rejected request (-32603): helper_unknown_error: setup refresh had errors
The same Get-Location command works when I run it directly in a separate local Codex chat. This is blocking dot-coordinated Blender/Unity work that previously worked.

What steps can reproduce the bug?

Connect the Windows PC to dot. It shows as connected and authorized.

Ask dot to start or resume a task on that PC.

Have the task run Get-Location.

It fails with the setup-refresh error before executing the command.

Run Get-Location directly in a separate local Codex chat. It succeeds.

What is the expected behavior?

Tasks started or resumed through dot should execute commands on the connected, authorized PC, as they did previously. Get-Location should return the current directory without a setup error.

Additional information

  • Platform: Windows
  • App: ChatGPT desktop, “Powered by Codex & OWL”
  • Version: 26.1002.52244
  • Release date shown in the app: October 7, 2026
  • This workflow worked a few days before the recent update
    Already tried:
  • Restarting the PC
  • Closing and reopening the desktop app
  • Disconnecting and reconnecting the PC
  • Installing the latest available desktop update
  • Testing both an existing task and a fresh diagnostic task
  • Changing chat permissions and retesting
    The same error persists. Direct execution in my local “Apex Continue” chat works, while tasks started or resumed through dot fail.
    The October 7 desktop incident is marked resolved, but this still occurs on the version above. I don’t know whether it’s related.

Activity

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 workingdotsIssues involving setting up ChatGPT dots or managing their ongoing work.remotetool-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