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

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.

Still reproducible on the current Microsoft Store Windows build as of 15 July 2026.

Environment

• Codex desktop app: 26.707.9981.0; Microsoft Store reports no update available
• Windows 11 Pro 10.0.26200 x64
• ChatGPT Pro
• Both computers signed into the same ChatGPT account

Actual behaviour

• Settings → Connections shows “Control this PC” and “SSH”.
• “Control other devices” is absent.
• This PC can be controlled from the other computer.
• The other computer can generate a Computer pairing code instructing me to enter it under Settings → Connections → Control other devices, but that tab is absent here.
• Opening codex://settings/connections/devices does not expose the missing tab.

Expected behaviour
Windows Codex desktop should expose “Control other devices” so this PC can act as the controller, matching the documented desktop-to-desktop flow.

This appears asymmetric: hosting works on Windows, but controlling another desktop from this Windows PC is unavailable.

Additional implementation clue from inspecting the shipped Windows app bundle (this is an inference, not a confirmed root cause):

• The packaged renderer still contains the complete Control other devices settings component and its route.
• That tab is conditionally omitted by a separate feature gate (identifier 782640499). In the current bundle, the tab is included only when the gate evaluates false.
• The Control this PC → Add → Computer dialog still unconditionally tells the user to enter the code at Settings → Connections → Control other devices.
• The broader features.remote_connections=true setting controls a different Connections-level path and does not restore the hidden controller tab.

This creates an impossible UI state on Windows: the host/pairing-code flow is enabled and directs users to a controller flow that the same shipped app hides. If controller mode is intentionally unavailable on Windows, the Computer option/instructions should be platform- or gate-aware; otherwise the controller tab should be exposed when computer pairing is offered.

The pairing code and account identifiers are intentionally omitted.

same issue here

That tab is missing on the Windwos Codex Desktop as well.

@russlib @ScottKemp @tibo-openai

I was able to patch the flag that was causing the tab to be hidden and get the OAUTH flow + device activation code input to work. Added a device successfully after that and everything seemingly works perfectly. The functionality is all there and feature complete. Perhaps someone forgot to enable the feature flag for the Windows build?

<img width="2489" height="1243" alt="Image" src="https://github.com/user-attachments/assets/6c4cca09-800b-468a-9171-cd036e8679da" />

@russlib @ScottKemp @tibo-openai I was able to patch the flag that was causing the tab to be hidden and get the OAUTH flow + device activation code input to work. Added a device successfully after that and everything seemingly works perfectly. The functionality is all there and feature complete. Perhaps someone forgot to enable the feature flag for the Windows build? <img alt="Image" width="2000" height="999" src="https://private-user-images.githubusercontent.com/31630310/623443552-6c4cca09-800b-468a-9171-cd036e8679da.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODQzMzYyNTUsIm5iZiI6MTc4NDMzNTk1NSwicGF0aCI6Ii8zMTYzMDMxMC82MjM0NDM1NTItNmM0Y2NhMDktODAwYi00NjhhLTkxNzEtY2QwMzZlODY3OWRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA3MTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNzE4VDAwNTIzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRlMTdiZjU1OGU4M2JhODY4MWVkMjVhZTUzMDE3MjAzZDgwZjUwYTlkM2MzZWNjY2ZhZWQwMjA3M2ZmOGFjY2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.DB8cC2S0Trm_cVvsF14S8pjlEdBmIEGbKaP86IUlGF8">

Can you share how?

I have the same issue on the windows build

Same here...

@russlib @ScottKemp @tibo-openai I was able to patch the flag that was causing the tab to be hidden and get the OAUTH flow + device activation code input to work. Added a device successfully after that and everything seemingly works perfectly. The functionality is all there and feature complete. Perhaps someone forgot to enable the feature flag for the Windows build? <img alt="Image" width="2000" height="999" src="https://private-user-images.githubusercontent.com/31630310/623443552-6c4cca09-800b-468a-9171-cd036e8679da.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODQ0OTEyMjcsIm5iZiI6MTc4NDQ5MDkyNywicGF0aCI6Ii8zMTYzMDMxMC82MjM0NDM1NTItNmM0Y2NhMDktODAwYi00NjhhLTkxNzEtY2QwMzZlODY3OWRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA3MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNzE5VDE5NTUyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2ZmJlYTkxOWQ4NDI5MjE5ZmUzYzU5ODBmZGEzOTk0OTRmY2FlYzUwZDE4ZTFjMjBiZTllN2VjYzM1M2JiYmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.XNXu_mgcn0EvoTQdEIFSXWfgwGUMONAymjLrHFHefg4">

please tell us how to fix this @h5kk

> @russlib @ScottKemp @tibo-openai > I was able to patch the flag that was causing the tab to be hidden and get the OAUTH flow + device activation code input to work. Added a device successfully after that and everything seemingly works perfectly. The functionality is all there and feature complete. Perhaps someone forgot to enable the feature flag for the Windows build? > <img alt="Image" width="2000" height="999" src="https://private-user-images.githubusercontent.com/31630310/623443552-6c4cca09-800b-468a-9171-cd036e8679da.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODQ0OTEyMjcsIm5iZiI6MTc4NDQ5MDkyNywicGF0aCI6Ii8zMTYzMDMxMC82MjM0NDM1NTItNmM0Y2NhMDktODAwYi00NjhhLTkxNzEtY2QwMzZlODY3OWRhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA3MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNzE5VDE5NTUyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI2ZmJlYTkxOWQ4NDI5MjE5ZmUzYzU5ODBmZGEzOTk0OTRmY2FlYzUwZDE4ZTFjMjBiZTllN2VjYzM1M2JiYmYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.XNXu_mgcn0EvoTQdEIFSXWfgwGUMONAymjLrHFHefg4"> please tell us how to fix this @h5kk

@h5kk please, thanks!

@lijiachen417 @hatson321 I was able to patch it too on those builds: 26.623 and the current 26.715 build.

I encountered two obstacles :
First, flipping the feature flag on to get the tab to show. Even with the tab active, enrollment wouldnt work and would throw with Remote control device keys are only available on macOS and there is a missing remote control package, so it dies before oauth : remote_control_authorize_failed in codex-desktop-*.log (localappdata)

I used sol to help write a patching script that builds a copy of the app, then patch it so your original is untouched and you can just pin the patched copy as you go, still update the release copy and patch as you go until its fixed upstream. But sol wouldnt let me hack into codex app's internals, and no, I am not going to "Apply to be part of the Cybersecurity Research Program" as per the api errorMsg. So I just did the sane thing, asked Kimi K3 and it didnt need much guidance.

Warnings : Its obviously unsupported, the file backed key used for signing can be decrypted by any process running in userspace priv.

Here is the repo https://github.com/zdaar/codex-hacks

Bonus : it also contains a patch to hack away (disable) the diff collecting pannel that can slow your wsl maching to a crawl and straight up lock it in some cases : Codex Desktop on Windows eagerly runs review-summary Git snapshots on restored workspaces, causing CPU/IO spikes #30820

Edit : Screenshot

<img width="752" height="612" alt="Image" src="https://github.com/user-attachments/assets/d3566367-7c32-451c-ae65-b6467bc44e3b" />