Windows Codex app missing “\control other devices"” tab in Settings > Connections

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

Version 26.611.62324 • Released Jun 17, 2026

What subscription do you have?

Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I want to control codex remotely from my windows pc, under the connections tab the "control other devices" tab is missing. Displayed are "control this pc" and "ssh"

What steps can reproduce the bug?

Opening the connection settings

What is the expected behavior?

control other devices tab being displayed and I can control

Additional information

Same issue here.

same. also connect from mac to pc constantly loops between "Connection failed" and "Connecting"

Me as well

Same issue, hope the capability to control other devices get added to Windows as well

Please add this feature

Pleaaaaaaaase

Please add this feature

Would also like to highly request this feature be available from Windows!

still an issue as of mid-July 2026

Still an issue. Frustrating that this is available on Mac but not on Windows, and that the documentation does not provide any indication that it's a Mac-only feature.

As a workaround for the missing “Control other devices” option, I tried connecting through Settings → Connections → SSH to another Windows machine.

Regular SSH works and public-key authentication succeeds, but the Codex app appears to assume that every remote host uses a POSIX shell. The remote Windows OpenSSH server uses cmd.exe, so Codex’s Bash shell-detection command fails:

Authenticated using "publickey".
/usr/bin/bash: -c: line 2: syntax error: unexpected end of file from `if` command on line 1
'tcsh)' is not recognized as an internal or external command,
operable program or batch file.

I confirmed that:

The remote host is Windows.
Its default SSH command processor is C:\Windows\System32\cmd.exe.
codex is installed and available on the remote PATH.
Normal interactive SSH access works correctly.

It looks like the SSH connection flow does not detect the remote OS/default shell before sending Bash-specific commands.

Expected behavior: Codex should detect whether the remote shell is cmd.exe, PowerShell, or a POSIX shell and use compatible commands. Alternatively, if native Windows SSH hosts are unsupported, the UI should report that clearly instead of displaying a generic SSH connection failure.

As another workaround, I am trying a separate SSH server inside WSL so Codex receives the Bash environment it expects.

Did you guys try this temp solution : #28919 (comment)

Not in a rush with this, so waiting for the official solution for now.

Same issue here as of September 2, 2026 on two Windows PCs in Spain.

Setup:

Desktop PC intended to be the always-on host
Windows laptop intended to control the desktop remotely
Both using the Codex/ChatGPT Windows app

On the host, Settings → Connections → Control this PC → Add → Computer successfully generates a pairing code and explicitly instructs me to enter it under Settings → Connections → Control other devices on the other computer.

However, on both Windows PCs the Connections screen only shows:

Control this PC
SSH

The Control other devices tab is completely missing, so there is nowhere to enter the generated pairing code and Windows-to-Windows pairing is impossible.

This is especially frustrating because the UI itself advertises the computer-to-computer pairing flow. Please enable/fix Control other devices on Windows, or clarify the rollout/status in the UI and documentation.

I also experience this issue on the Fedora Linux latest release of Codex, installed via RPM.

Adding another strong +1 from a Windows user.

Windows-to-Windows Remote Control is an urgently needed workflow for users who keep one Windows machine online as their main Codex host and need to access it from another Windows PC. Mobile Remote is useful for quick checks, but it is not a practical replacement for a desktop interface when managing multiple chats, reviewing diffs, reading terminal output, and working for extended periods.

The current setup flow is also very confusing: the Windows host can generate a computer pairing code and explicitly instruct the user to open Settings → Connections → Control other devices on the second computer, but that tab does not exist in the Windows app—even when both machines are fully updated.

There is clearly substantial demand for this feature. Could the Codex team please confirm:

Whether first-party Windows controller support is actively planned or in development;
Whether there is an estimated release window, even a rough one;
If no ETA is available, whether the Windows UI and documentation can at least be updated to clearly state the current limitation.

Please consider prioritizing this. For users whose primary computers are both Windows machines, this missing capability significantly limits the usefulness of Codex Remote.

I can reproduce this on Windows as well. In Settings > Connections, the Windows app shows only “Control this computer” and “SSH”; the “Control other devices” tab is missing. The same account can successfully connect to/control the Windows host from the ChatGPT mobile app, so the host-side Remote Control setup and account pairing appear to be working. The missing functionality is specifically Windows desktop -> another Windows device. Expected: the Windows desktop app should expose “Control other devices” (as shown in the Mac UI) so a second Windows PC can pair with and control the host. Current workaround: mobile Remote Control works, but Windows-to-Windows control cannot be initiated from the GUI.

Current status on Windows Remote Control:

Tested on the current Windows Codex build: Released 5 Sept 2026

About: 26.901.41123
MSIX/package: 26.901.5003.0

On this build, the renderer CDP endpoint still opens, but the Electron main-process inspector no longer becomes available. That breaks the older bootstrap path which depended on the main inspector.

A renderer-only path does work on this build. In testing:

renderer endpoint: ready
main inspector: unavailable
renderer-only bootstrap selected
renderer bridge verification succeeded
bridgeProof=True
launcher reached Active

The current public openai/codex repository contains the remote-control backend pieces such as transport, enrollment, pairing, status, and client-management RPCs, but the Windows Desktop UI gate, Electron bridge/preload layer, and remote-control-device-key.node implementation do not appear to be present in the public repo.

So at the moment this looks like a Desktop-package-layer issue rather than something that can be fixed cleanly with a PR against the public Rust repository.

The renderer-only behavior can be tested here:
https://github.com/drarvindc/codex-remote-launcher

Current tested release:
https://github.com/drarvindc/codex-remote-launcher/releases/tag/v0.3.0

I ended up taking a different route and now have a working standalone Windows implementation:

Codex Remote Launcher https://github.com/drarvindc/codex-remote-launcher

Rather than rebuilding or patching the Codex package, this starts the installed Codex Desktop directly in the required debug/Special configuration and applies the runtime bridge needed for:

Settings → Connections → Control other devices

Confirmed working after a clean Windows reboot on Codex Desktop 26.825.6671.0.

What is working for me:

Control other devices appears on Windows

remote device enrollment/connection works

remote projects open normally

remote text updates are effectively real-time

closing Codex and relaunching through the launcher works

no Administrator privileges required in the tested setup

The implementation intentionally avoids:

modifying ChatGPT.exe

modifying app.asar

changing C:\Program Files\WindowsApps

taking ownership/changing WindowsApps ACLs

killing/taking over an already-running Codex process

background watcher/lifecycle machinery

The flow is deliberately simple:

Codex closed → launcher → Special Codex → runtime bridge → remote enabled

If Codex is already running, the launcher refuses safely and asks you to close it first.

Windows Control other devices connected

Remote project connected and usable

Current release:

v0.1.0 pre-release https://github.com/drarvindc/codex-remote-launcher/releases/tag/v0.1.0

This is still experimental and unofficial and relies on undocumented/internal Codex behavior, so a future Codex update may break it.

Credit also goes to:

https://github.com/naipi11/CodexRemote-fix

https://gist.github.com/hunterbeach/dc4b74bda0e045e33f308099182b4f80

Those projects/research were very useful in understanding the Windows runtime path. This standalone implementation uses a minimal direct-launch architecture rather than the earlier takeover/lifecycle approach.

I am using this now, and I can't thank you enough for it!

Still reproducible on Windows as of 2026-09-06.

In Settings > Connections, the Windows Codex app only shows:

Control this computer
SSH

There is still no Control other devices tab, so this Windows machine cannot act as the controller for another Codex host through the first-party Remote Control flow.

This is especially confusing because the current Codex help documentation describes Windows as being able to control other devices. The UI on this machine is in Chinese, where the two visible tabs are 控制此电脑 and SSH.

Expected behavior: Windows should expose the same Control other devices pairing/controller flow available on supported controller platforms, including Windows-to-Windows remote control.

I have a current screenshot showing the missing tab and can provide the exact Codex app build number if useful.

Still issue on Windows as of 2026-09-07.

Even the Open AI already rolled- out the latest "State-of-the-art" Gpt 6 Astra. This feature on Windows is still missing.

Really don't know why on earth they do not want to fix this...

The secondary PC shows ability to control from other PCs and gives a pairing code and instructions to connect from primary PC, but "control other devices" tab is not visible in the Codex for Windows app. Looks like an incomplete rollout which has been like this for numerous months now. Is there any ETA on this being available?

same here, trying to control my macOS codex from Windows.

ChatGPT-RemoteTab-Patch-26.901.6511.0.zip

Fix for hidden “Control other devices” tab in ChatGPT for Windows

Problem

In some recent versions of ChatGPT for Windows, the “Control other devices” functionality is already implemented in the application, but the corresponding tab is not visible under:

Settings → Connections

This prevents the Windows application from starting the authorization flow required to remotely control another Windows or macOS device.

The issue was reproduced on:

ChatGPT for Windows
Version: 26.901.6511.0
Architecture: x64

The important finding is that the feature itself is already present in the application code.

Root cause

Inspection of the application's JavaScript bundle shows that the tab is explicitly defined as:

id: `access-other-devices`

with the label:

defaultMessage: `Control other devices`

The application evaluates an additional feature-control condition before adding this tab to the Connections interface.

The relevant logic can be simplified as:

y = ft(`782640499`);
xe = !y;

showControlThisPC = be;
showControlOtherDevices = be && xe;

Therefore:

Control this PC
    → requires the general remote-control availability condition

Control other devices
    → requires the same condition
    → PLUS an additional feature flag

If this additional flag evaluates to the state that hides the feature, “Control this PC” may still be available while “Control other devices” is completely removed from the UI.

The tab is not merely disabled. It is excluded from the list of tabs rendered by the Connections page.

Exact file modified

This is not a configuration tweak.

The modification is made directly to the JavaScript bundle shipped inside ChatGPT's Electron app.asar archive.

For the tested build:

ChatGPT version: 26.901.6511.0
Architecture: x64

the ASAR archive in the patched copy is located at:

%LOCALAPPDATA%\ChatGPT-RemoteTab-Test\26.901.6511.0\
app\resources\app.asar

Inside app.asar, the exact JavaScript file modified is:

webview/assets/remote-connections-settings-6c39d6ca5d5c.js

Therefore, the complete logical path of the modified file is:

%LOCALAPPDATA%\ChatGPT-RemoteTab-Test\26.901.6511.0\
app\resources\app.asar
    └── webview/assets/remote-connections-settings-6c39d6ca5d5c.js

The relevant minified code is:

be=cn(),xe=!y,Se=T==null

and the patch changes it to:

be=cn(),xe=!0,Se=T==null

In practice, this is a one-character change:

- xe=!y
+ xe=!0

Since:

!0 === true

the additional UI-level gate for “Control other devices” is forced to true.

The surrounding logic then becomes, conceptually:

showControlThisPC = be;
showControlOtherDevices = be;

The patch therefore removes only the additional visibility gate while leaving the remaining logic untouched.

Authentication, permissions, device authorization and general remote-control availability checks are still handled normally by ChatGPT and OpenAI services.

Download

Download the complete patch package:

ChatGPT-RemoteTab-Patch-26.901.6511.0.zip

SHA-256:

c742414812b862628503a6853277cd1c5bc250904782564f002f7e6785eb520e

The package contains:

INSTALL_PATCH.cmd
LAUNCH_PATCHED_CHATGPT.cmd
REMOVE_TEST_COPY.cmd
Patch-RemoteTab.ps1
patch-manifest.json
README.txt
TECHNICAL_ANALYSIS.md
TEST_REPORT.md

The patch is intentionally distributed as a complete package rather than as a single modified application file.

The official Microsoft Store installation is not overwritten.

Installation

1. Download and extract the ZIP

Download:

ChatGPT-RemoteTab-Patch-26.901.6511.0.

[ChatGPT-RemoteTab-Patch-26.901.6511.0.zip](https://github.com/user-attachments/files/32002015/ChatGPT-RemoteTab-Patch-26.901.6511.0.zip)

zip

Extract the entire archive to a normal folder.

Do not run individual scripts directly from inside the ZIP.

2. Run the installer

Double-click:

INSTALL_PATCH.cmd

Run it as a normal user.

Do not run it as Administrator.

The installer verifies the installed ChatGPT version and creates a separate test copy.

When prompted, confirm the operation.

The patched copy is created under:

%LOCALAPPDATA%\ChatGPT-RemoteTab-Test\26.901.6511.0\

which normally corresponds to:

C:\Users\<username>\AppData\Local\ChatGPT-RemoteTab-Test\26.901.6511.0\

The official ChatGPT Microsoft Store installation remains unchanged.

3. Launch the patched copy

After the patch has been successfully applied, launch:

LAUNCH_PATCHED_CHATGPT.cmd

The patched instance uses the modified app.asar from the test copy.

Unlocking the feature

In the patched ChatGPT application, open:

Settings
→ Connections
→ Control other devices

The previously hidden tab should now be visible.

Then:

Open Control other devices.
Follow the normal ChatGPT setup flow.
Allow ChatGPT to open the browser when requested.
Authenticate using the same ChatGPT account.
Grant the requested remote-device permission.
Complete the authorization flow in the browser.
Return to ChatGPT and complete the setup.

This browser authentication / permission step is important.

What happens after authorization

After completing the authorization flow:

Close the patched ChatGPT copy completely.
Make sure no patched ChatGPT process remains open.
Start the original, unmodified ChatGPT Windows application from the Start menu.
Open:

Settings
→ Connections

At this point, “Control other devices” should also be available in the original ChatGPT application.

The original application's files remain unmodified.

This behavior strongly indicates that the effective feature entitlement / authorization is controlled server-side.

The patch only exposes the already implemented UI entry so that the browser-based authorization flow can be reached.

Once the account/device has completed that authorization flow, the original application receives the resulting server-side state and exposes the feature normally.

Why this points to a server-side lock

The patched copy only changes the UI visibility condition.

It does not:

- implement Remote Control
- bypass authentication
- emulate device permissions
- patch the official Microsoft Store application
- modify the original ChatGPT app.asar

Yet, after browser authentication and permission approval are completed through the patched copy, the functionality becomes available in the original app as well.

This strongly suggests that the effective authorization / entitlement state is stored remotely and associated with the ChatGPT account and/or device.

In other words:

The Windows client already contains the feature.

A client-side feature gate can hide the setup UI.

The patch exposes the setup UI.

The actual authorization is then completed through OpenAI's normal server-side flow.

After authorization, the official unmodified application can use the feature normally.

Removing the patch

Once “Control other devices” is visible and working in the original ChatGPT application, the patched copy is no longer required.

First, close all ChatGPT processes.

Then double-click:

REMOVE_TEST_COPY.cmd

Follow the removal prompt.

Alternatively, the test copy can be removed manually.

Open:

Win + R

and enter:

%LOCALAPPDATA%

Then remove:

ChatGPT-RemoteTab-Test

The full path is normally:

C:\Users\<username>\AppData\Local\ChatGPT-RemoteTab-Test\

For this specific build, the application copy is located at:

C:\Users\<username>\AppData\Local\ChatGPT-RemoteTab-Test\26.901.6511.0\

Deleting the entire:

ChatGPT-RemoteTab-Test

folder also removes the separate test profile and any remaining files associated with the patched copy.

Do not uninstall the official ChatGPT application.

After removal, simply start ChatGPT normally from the Windows Start menu.

Connecting another Windows PC or macOS device

Once the functionality has been unlocked in the original application, the patch is no longer involved.

Open the official ChatGPT application and go to:

Settings
→ Connections
→ Control other devices

You can then proceed with the normal pairing flow for another supported computer.

The target can be:

Windows

or:

macOS

Complete the authorization / pairing flow shown by ChatGPT on the machines involved.

From that point onward, the official ChatGPT application can be used normally.

Important notes

This patch does not add Remote Control to ChatGPT.

The functionality is already present in the Windows application.

The patch only exposes a UI entry that is hidden by an additional feature-control condition.

This workaround does not bypass authentication, permissions or device authorization.

The normal OpenAI authorization flow still has to complete successfully.

This is also not a configuration-file modification.

It is a source-level modification of the JavaScript bundle shipped inside ChatGPT's Electron app.asar archive.

The exact modified file for this build is:

webview/assets/remote-connections-settings-6c39d6ca5d5c.js

inside:

app\resources\app.asar

The filename:

remote-connections-settings-6c39d6ca5d5c.js

is specific to ChatGPT Windows build:

26.901.6511.0

Future builds may use a different content hash in the filename.

Do not blindly apply the same modification to another version without first locating and verifying the corresponding remote-connections-settings-* bundle.

Tested configuration

OS: Windows
ChatGPT version: 26.901.6511.0
Architecture: x64

Patched copy:
%LOCALAPPDATA%\ChatGPT-RemoteTab-Test\26.901.6511.0\

Modified file inside app.asar:
webview/assets/remote-connections-settings-6c39d6ca5d5c.js

Change:
xe=!y
→
xe=!0

Observed result:
- “Control other devices” exposed in patched copy
- browser authentication completed
- requested permission granted
- patched copy closed
- original ChatGPT application reopened
- “Control other devices” also available in the original application
- patched copy can then be removed
- another Windows PC or macOS device can subsequently be connected using the official application

Support

If this workaround saved you some time or helped you unlock the feature, you can support further investigation and updates here:

☕ [Buy me a coffee](https://buymeacoffee.com/marcello.montanino)

If you test this workaround on a newer ChatGPT Windows build, please report the exact version number and whether the same behavior is still present.

This is working for me now in Codex on W11-W11, on both my company laptop and account and my personal account and PC. Much thanks.

yes they finally fixed it

Its working now. Thank you very much

Navigation Menu

Windows Codex app missing “\control other devices"” tab in Settings > Connections #28919

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

42 remaining items

Windows `Control other devices` connected

Remote project connected and usable

Fix for hidden “Control other devices” tab in ChatGPT for Windows

Problem

Root cause

Exact file modified

Download

Installation

1. Download and extract the ZIP

2. Run the installer

3. Launch the patched copy

Unlocking the feature

What happens after authorization

Why this points to a server-side lock

Removing the patch

Connecting another Windows PC or macOS device

Important notes

Tested configuration

Support

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Windows Codex app missing “\control other devices"” tab in Settings > Connections #28919

Description

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

Activity

alessandrotesoro commented on Jun 21, 2026

ivawzh commented on Jun 22, 2026

gatethegreat commented on Jun 23, 2026

nyavana commented on Jun 29, 2026

rnisthal commented on Jul 1, 2026

tksuns12 commented on Jul 3, 2026

FlyAndNotDown commented on Jul 8, 2026

Blueteak commented on Jul 10, 2026

ilnytskyi commented on Jul 14, 2026

jfloersch commented on Jul 14, 2026

ilnytskyi commented on Jul 14, 2026

42 remaining items

DNAshx commented on Sep 2, 2026

SrPedro69 commented on Sep 2, 2026

claytonwramsey commented on Sep 2, 2026

pxlsy2000 commented on Sep 4, 2026

hhhz1118 commented on Sep 5, 2026

drarvindc commented on Sep 5, 2026

asaph-xxx commented on Sep 5, 2026

Windows Control other devices connected

Remote project connected and usable

Tristan-sdu commented on Sep 6, 2026

Underdog87 commented on Sep 7, 2026

matthewlilley commented on Sep 7, 2026

projectamuna commented on Sep 8, 2026

m121212 commented on Sep 9, 2026

Fix for hidden “Control other devices” tab in ChatGPT for Windows

Problem

Root cause

Exact file modified

Download

Installation

1. Download and extract the ZIP

2. Run the installer

3. Launch the patched copy

Unlocking the feature

What happens after authorization

Why this points to a server-side lock

Removing the patch

Connecting another Windows PC or macOS device

Important notes

Tested configuration

Support

scaepz commented on Sep 11, 2026

ilnytskyi commented on Sep 11, 2026

BunBnnuy commented on Sep 11, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Windows `Control other devices` connected