Field notes / Windows / 9 October 2026

dot + Codex: helper_unknown_error: setup refresh had errors

A working local session. An unresolved handoff. A case study in checking what actually worked.

By Cosmik Ventures Observed and reviewed 9 October 2026

Supported repair not demonstrated. This record documents one case and supported setup checks. It is not a universal fix.

If your dot cannot coordinate a local Codex task on Windows, this may be the error you are searching:

exec-server rejected request (-32603): helper_unknown_error: setup refresh had errors

In our case, a dot-delegated task failed while a separate ordinary local Codex session could still work. We also observed messages exchanged through a UI-based method. After checking that method against current Computer Use guidance, we are not recommending or reproducing that route. We have not demonstrated a supported repair of the original dot-to-local-Codex coordination failure.

This record separates the working local session from the unresolved handoff so that a promising result does not become an unsupported fix claim.

The environment in this case

Platform: Windows desktop; exact Windows OS build not established for this report
Reported desktop app: 26.1002.52244
Reported app build: 13536, production channel
Separately reported CLI: 0.162.0-alpha.2
Observation date: 9 October 2026

The desktop app, its build, and the CLI have different version identifiers. These details describe this case and do not establish that every installation on the same version is affected.

What failed and what worked

The delegated route returned the exact error above before its requested command ran. Ordinary local Codex remained usable in a separate session on the same computer. That comparison shows a difference in observed behavior between the two paths. It does not identify the underlying cause.

Other public reports describe a closely matching pattern. Issue #51882, opened 8 October 2026, reports failed dot-started or resumed tasks and a successful ordinary local command. Issue #51735, opened 7 October, also reports delegated tasks failing before execution while ordinary local sessions work. Issue #51931, opened 8 October, reports both difficulty reading a local task and a delegated execution failure.

These are reports from users. They do not establish a shared cause or an official repair.

Why we are not recommending the apparent workaround

We wanted dot and Codex to exchange work without a person copying every message. An observed exchange used computer control to operate the ChatGPT interface. OpenAI's current Computer Use documentation excludes automating ChatGPT itself. We are not recommending or reproducing that route.

That limit applies to the Computer Use method. Official dot documentation separately describes supported local Work and Codex tasks. A supported task-creation capability does not mean that the failing setup in this case has recovered.

Supported connection checks

The following is the documented connection flow, not a fix for helper_unknown_error. If your computer is already connected and authorized, record that fact instead of assuming that repeatedly reconnecting it will repair this failure.

On the relevant computer, open your dot's profile in the ChatGPT app.
Under Computers, find Your computer and inspect its access status. If you are choosing to connect it, select Allow access.
Review the confirmation before allowing access. Keep the computer online and the desktop app open for local work.

Check the current interface and official connection guide if these labels differ. dot's computer permission is separate from connecting a computer to Codex or enabling Work Sync.

What to preserve for troubleshooting

Keep a redacted record of the full error, the date and time, the current app version, which task failed, whether the requested command started, and any successful ordinary-local comparison. A result in a local chat does not prove that dot can read it or send the next instruction.

Keep private paths, account details, credentials, and unrelated conversation content out of public reports. Do not copy a proposed ownership, sandbox, or security change from another case without establishing that it applies to yours.

Questions people searching this error may have

Does this fix helper_unknown_error: setup refresh had errors?

No. The supported dot-coordination failure remains unresolved in this case. This page documents the observed behavior and legitimate setup checks.

Can dot and Codex work together at all?

Official documentation describes dot creating local Work or Codex tasks and continuing existing local Codex tasks on a connected computer. That documented capability is separate from whether a particular failing installation is working now.

Does a working local Codex session mean the bridge is repaired?

No. Local execution, reading a result, delivering a follow-up, and completing the next step need separate evidence.

Is the UI-based method a supported alternative?

We are not recommending it. The method conflicted with the current Computer Use boundary for automating ChatGPT. We are not recommending or reproducing that route.

Was this the first discovery of the problem or a unique fix?

We have not established that. Closely matching public reports already exist. This case does not demonstrate an official or universal fix.

Current conclusion

A local success is one part of the test.

The ordinary local session was usable. A supported dot-to-local-Codex handoff remains unverified in this case. A future recovery claim should show the supported route completing a task, returning its result, receiving a follow-up, and completing that follow-up without manual message relay.

Sources and review date

Official documentation and public issue reports checked 9 October 2026. Issue reports describe individual observations and may change as investigations continue.

Readable public text and clear titles can help discovery. Search engines and AI systems are not guaranteed to index, retrieve, rank, or cite this page.