[macOS 26.715.12143] Enabling “Control this Mac” briefly shows mobile device, then fails with remote-state / single-instance errors
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos
- Domain
- desktop
Research direction
Start by reproducing the failure from Settings → Connections → Control this Mac in ChatGPT Desktop for macOS 26.715.12143, then trace the “Failed to update remote status” and apparent single-instance errors. Done means Allow connections remains enabled, the Mac registers as a remote-control host, and the discovered mobile device remains available without retries.
Written by the indexing model from the issue text.
Description
What version of the Codex/ChatGPT App are you using?
ChatGPT Desktop for macOS 26.715.12143.
What subscription do you have?
ChatGPT Prolite.
What platform is your computer?
macOS. Exact macOS version and CPU architecture are not available at the time of reporting.
What issue are you seeing?
In Settings → Connections → Control this Mac, enabling Allow connections does not persist.
On the first attempt, the user's mobile device appears briefly in the remote-control UI, then the app reports an error equivalent to:
Failed to update remote status.
On the second attempt to enable the toggle, the app reports:
Unable to enable remote control. Please make sure only one ChatGPT instance is running.
The user reports that only the current ChatGPT macOS app is intentionally in use. They also fully quit/restarted ChatGPT and checked for duplicate ChatGPT/Codex/ChatGPT Classic instances before retrying.
This looks like either:
- a stale local single-instance/remote-control lock,
- duplicate host enrollment being detected incorrectly, or
- a race while updating the remote-control host state after the mobile device is discovered.
Steps to reproduce
- Launch ChatGPT Desktop
26.715.12143on macOS. - Open Settings → Connections → Control this Mac.
- Turn on Allow connections.
- Observe that a signed-in mobile device appears briefly.
- Observe the error: Failed to update remote status.
- Turn on Allow connections again.
- Observe the error asking the user to ensure only one ChatGPT instance is running.
Expected behavior
The toggle should remain enabled, the Mac should register as a remote-control host, and the mobile device should remain available without requiring multiple retries.
Actual behavior
The remote-control state fails to update, and subsequent attempts are blocked by an apparent false-positive single-instance check.
Additional information
- Keep this Mac awake is enabled.
- The failure occurs in the new unified ChatGPT macOS app UI under Connections.
- A screenshot is available showing the affected Control this Mac → Allow connections toggle, but it could not be attached through the connector used to submit this report.
- No exact duplicate was found when searching the existing
openai/codexissues for the single-instance error text.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·