Skip to content

Android 1.2026.265 (27): Codex Remote repeatedly returns to “Authorize this phone” after successful browser authorization #48777

Description

@elkowalski1989

I cannot finish pairing my Android phone with Codex running in WSL. The phone opens the browser login, recognizes the correct ChatGPT account, and asks me to authorize access. After I authorize, it briefly shows “Pairing…” and returns to “Allow this phone to access ChatGPT on your computer.” The same cycle repeats on every attempt.

My environment:

  • ChatGPT Android app: 1.2026.265 (27)
  • Computer: Windows with Codex running in WSL
  • Codex CLI: 0.157.1
  • Running app-server daemon: 0.157.1
  • Subscription: ChatGPT Pro
  • Authentication: ChatGPT login
  • The saved Codex login email matches the account used during phone authorization.

To reproduce:

  1. In WSL, run:

    codex remote-control start
  2. The command reports that the machine is available for remote control.

  3. Generate a pairing code:

    codex remote-control pair
  4. Start the Remote pairing flow on Android.

  5. Tap “Authorize this phone.”

  6. Complete the browser login with the same ChatGPT account used by Codex.

  7. Confirm the account and tap “Authorize.”

  8. The phone returns to the app, briefly shows “Pairing…”, and then displays “Allow this phone to access ChatGPT on your computer” again.

  9. Repeating authorization produces the same result.

I expect authorization to complete and the phone to finish pairing with the computer. Instead, the app repeatedly sends me through the login and authorization flow without completing the connection.

I have confirmed the following:

  • The daemon reports that it is running.
  • The CLI and running daemon both report version 0.157.1.
  • The host successfully generates a pairing code.
  • The saved host login email matches the phone login.
  • The reported authenticator-app MFA workaround did not resolve the loop.

These reports appear related:

I have not established whether my failure is in the Android app, the authorization callback, or backend device enrollment. Similar reports on other host operating systems suggest that WSL may not be the cause.

Please investigate the Android Remote authorization and device-enrollment flow for 1.2026.265 (27). Is there a confirmed fixed build or a supported recovery procedure? Please also specify which sanitized diagnostics would help identify the failed step.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CLIIssues related to the Codex CLIauthIssues related to authentication and accountsbugSomething isn't workingremote

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions