ChatGPT mobile incorrectly blocks Codex Cloud when Remote Control is disabled

Open 💬 4 comments Opened Jun 28, 2026 by theophanemayaud

What issue are you seeing?

The ChatGPT mobile app appears to incorrectly gate the entire Codex mobile surface behind the Remote Control / mobile-remote entitlement.

In our workspace, Codex Cloud is enabled and works correctly from both:

  • Codex web
  • Slack

However, when opening Codex in the ChatGPT iOS app, the app shows:

Set up Codex Codex mobile is disabled by your workspace admin. Reach out to get access.

This happens even though hosted Codex Cloud sessions are available through other surfaces.

This looks like a permissions regression: disabling Remote Control should prevent controlling local/desktop Codex hosts from mobile, but it should not block access to hosted Codex Cloud sessions.

Expected behavior

When Codex Cloud is enabled for a workspace/user:

  • The ChatGPT mobile app should allow the user to view, start, manage, approve, and follow up on hosted Codex Cloud sessions.
  • Remote Control being disabled should only block mobile control of local/desktop/SSH Codex hosts.
  • A workspace should be able to allow mobile access to hosted Codex Cloud while still disabling remote access to user computers.

Actual behavior

The ChatGPT mobile app blocks the entire Codex tab and shows:

Codex mobile is disabled by your workspace admin.

This prevents access to Codex Cloud from mobile, even though Codex Cloud works from web and Slack.

Why this is a bug

Codex Cloud and Remote Control are different capabilities:

  • Codex Cloud runs hosted tasks in OpenAI-managed environments.
  • Remote Control allows a mobile or secondary client to control a Codex app environment running on a user’s computer or connected host.

Disabling Remote Control is a valid enterprise security policy. It should not force organizations to also lose mobile access to hosted cloud Codex sessions.

Currently, the only apparent workaround would be to enable Remote Control, but that is not acceptable for workspaces that intentionally prohibit remote access to local computers.

Steps to reproduce

  1. Use a workspace where Codex Cloud is enabled.
  2. Confirm that the affected user can use Codex Cloud from the web interface.
  3. Confirm that the affected user can use Codex Cloud from Slack.
  4. Disable Remote Control / mobile remote access for the workspace or user role.
  5. Open the ChatGPT iOS app.
  6. Navigate to Codex.
  7. Observe that the entire Codex mobile surface is blocked with:

Codex mobile is disabled by your workspace admin.

Impact

This blocks mobile management of Codex Cloud sessions for workspaces that disable Remote Control for security reasons.

It effectively bundles two separate capabilities:

<img width="706" height="1536" alt="Image" src="https://github.com/user-attachments/assets/b0c883a8-efeb-4864-99ce-309e054e8e96" />

Mobile access to hosted Codex Cloud sessions.

  1. Remote control of local/desktop Codex hosts.

These should remain independently controllable.

Environment

  • Platform: ChatGPT iOS app
  • App version: <fill in>
  • iOS version: <fill in>
  • Workspace type: <Business / Enterprise / Edu / other>
  • Codex Cloud: enabled
  • Codex Cloud works from web: yes
  • Codex Cloud works from Slack: yes
  • Remote Control: disabled
  • Screenshot attached: yes

Screenshot

Attached screenshot shows the ChatGPT iOS Codex tab displaying:

Set up Codex Codex mobile is disabled by your workspace admin. Reach out to get access.

Suggested fix

The mobile app should distinguish between:

  • can_use_codex_cloud
  • can_use_remote_control
  • can_use_local_host_remote_sessions

When Remote Control is disabled but Codex Cloud is enabled, the mobile app should still show hosted cloud Codex sessions and hide or disable only local/remote-host functionality.

What steps can reproduce the bug?

See description

What is the expected behavior?

Should allow web agent use though not remote

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗