Feature request: Add a remote visual preview/control mode for Codex mobile

Open 💬 2 comments Opened May 23, 2026 by GGBondBlueWhale

Hi Codex team,

I would like to suggest adding a remote visual preview / remote control mode to Codex mobile.

Right now, Codex is very useful for editing, refactoring, and implementing changes, but mobile users still have a major gap when the task requires visual validation. For example, when working on UI, animations, layout, web apps, iOS apps, or any project where the final result must be visually inspected, the user often needs to be at a desktop computer to open the running app, test interactions, and verify the result.

A remote desktop-like feature inside Codex mobile would make this workflow much stronger. The idea is not necessarily to expose a full unrestricted desktop by default, but to provide a safe, session-based way for the user to view and interact with the development environment, preview window, simulator, browser, or running app directly from Codex mobile.

This would be especially useful when the user is temporarily away from their computer and only has an iPad or phone. In that situation, the user could still review UI changes, interact with the app, test flows, check animations, approve Codex changes, and continue development without waiting until they return to their desktop.

Some benefits:

  • Better UI and visual QA: users can directly inspect layout, spacing, colors, animations, responsiveness, and visual regressions.
  • Better mobile productivity: users with only an iPad or phone can still meaningfully continue development and review Codex work.
  • Faster approval loop: instead of asking Codex to describe visual results, the user can see and test the actual running app.
  • Better support for frontend, iOS, Android, game, and design-heavy projects.
  • Fewer incorrect merges: users can verify visual behavior before accepting or merging changes.
  • Stronger Codex mobile experience: mobile would become more than a code review interface; it would support real development validation.
  • Better collaboration with Codex agents: users can let Codex implement changes, then immediately open the preview remotely and provide visual feedback.
  • Useful for temporary travel, classes, meetings, commuting, or any situation where the user cannot access their main development machine.

Possible implementation ideas:

  • A secure temporary remote preview session tied to a Codex workspace.
  • Read-only visual preview by default, with optional user-enabled control mode.
  • Ability to open a browser preview, simulator, local app preview, or selected window.
  • Touch-friendly controls for iPad and phones.
  • Clear permission boundaries, session expiration, and user confirmation before enabling control.
  • Optional screenshot/recording tools so users can give Codex precise visual feedback.

I think this would be a very valuable feature for Codex mobile, especially for users who rely on Codex for UI-heavy projects and need to visually inspect and approve work while away from a desktop.

View original on GitHub ↗

2 Comments

hendryyeh · 3 months ago

This is a real gap — no community tool fully covers the integrated "remote visual preview + agent control" you're describing. A few partial workarounds while OpenAI considers this:

  • CodeVibe (https://quantiya.ai/codevibe) — iOS/Android companion for Codex CLI: send prompts, view diffs, approve file edits from mobile. Doesn't render a running-app preview, but covers the conversation + approval loop your last bullet mentions.
  • Codex Web (chatgpt.com on mobile browser) — OpenAI's own browser-based Codex experience is closer to desktop, including preview context, but lacks native mobile app polish.
  • VS Code Tunnel + vscode.dev in a mobile browser — gives you a real preview-pane workflow remotely, though no integrated agent loop.
  • For visual validation specifically, exposing your dev server via ngrok / a tunnel and viewing it in a separate mobile browser tab is the closest "live preview" pattern today.

Agreed the integrated version you're describing would be much better — leaving the upvote so OpenAI sees the demand.

GGBondBlueWhale · 3 months ago

One possible product/abuse-control approach: OpenAI could consider making remote phone/iPad visual control available only to paid Codex users, such as Plus, Pro, Business, and Enterprise users. This would help prevent people from registering free accounts and abusing Codex as a general remote-control tool, which could consume a large amount of platform bandwidth.