openai / openai/codex

Codex Remote Control rejects verified MFA login on Windows

Open
#41,747 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app auth bug remote windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Hi OpenAI Support,

I am unable to enable Codex Remote Control in the ChatGPT Windows app. The app displays “Couldn’t update remote
control availability.”

My goal is to continue an existing Codex CLI session running in Warp on this Windows PC through ChatGPT Remote on
my Android phone.

Account and environment:

  • Account email: available privately on request
  • Plan: ChatGPT Max
  • Workspace: Personal account
  • ChatGPT desktop app: 26.825.6671.0
  • Codex CLI: 0.151.0
  • Windows: 10.0.26200
  • Phone: Samsung SM-S928U

I confirmed that the desktop app and phone use the same ChatGPT account and workspace. I restarted the app,
completed multiple fresh logins, enabled MFA, completed password plus phone-push MFA, completed password plus
email-code MFA, and added a 1Password passkey.

The issued credentials record successful MFA, but Remote enrollment still returns HTTP 403 with “Multi-factor
authentication required.”

Endpoint:

POST /backend-api/wham/remote/control/server/enroll

Recent failures:

  • August 31, 2026 at 00:59:09 UTC, request ID: 42dceaab-539e-464d-9f8d-79a9c20b3624
  • August 31, 2026 at 01:11:54 UTC, request ID: 72d50507-1bfd-4b2f-88e9-2c83d9a48c3e

Could you please review or reset the Remote Control enrollment and MFA state for this account and advise how I can
complete the Windows and Android pairing?

Thank you.

Tony Rivas

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies the POST /backend-api/wham/remote/control/server/enroll endpoint and two request IDs associated with HTTP 403 responses. Start by tracing the enrollment and MFA handling for this endpoint, then reproduce the Windows login and Android pairing flow; done means verified MFA permits enrollment and Remote Control pairing succeeds.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authentication, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.