You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: mobile companion to view and control Codex desktop sessions #14164
I would like a mobile companion experience for Codex App so I can view and control an active desktop session from my phone.
A concrete version of this would be:
See the current desktop session status, transcript, pending tasks, and terminal/tool activity from a phone.
Send follow-up instructions or approvals from the phone while the main Codex session keeps running on desktop.
Resume, pause, or stop a desktop task remotely.
Get mobile notifications when Codex needs approval, finishes a task, or gets blocked.
This would be similar to the remote/mobile control workflow people use with Claude Code, where the desktop or local agent does the work, but the phone acts as a lightweight control surface.
Why this would help:
Many Codex tasks run for a while, so it is useful to monitor progress away from the desk.
Approval steps currently require being back at the desktop at the right moment.
For longer coding or debugging tasks, a phone view would make Codex much more practical in real workflows.
Even a first version with read-only session viewing + push notifications + simple reply/approve actions would already be very useful.
Additional information
A few implementation directions that could work:
Pair a phone with the signed-in desktop Codex app.
Expose an optional secure remote session channel for the active desktop task.
Support read-only mode first, then remote input / approval actions.
The key thing is not full IDE editing on mobile. The valuable part is being able to supervise and steer a desktop Codex session from a phone.
Reacted by w3struk, Andrea Panizza, Ali Uraish , Mutahhar bin Muzaffar, su21, ruebixcube, brendan042, Lukman Nakib, 404sand808s, Javier Punzano and 1 more
Keep your existing ssh + tmux + Codex workflow, and use Telegram only as the remote layer for status, approvals, and follow-up input.
Why It Matters
No workflow rewrite: keep using local tmux + Codex instead of switching to a browser dashboard or remote desktop
Actually remote-usable: not just logs, but approvals, interrupts, and follow-up input
Clear multi-task control: one control topic plus task-specific topics for parallel work
Phone-friendly by design: useful when you are away from your machine but still need to keep work moving
Lower setup friction: one-command installer plus launchd service support
Activity
github-actions commentedon Mar 10, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Asuka-wx commentedon Apr 2, 2026
I built a Telegram bridge to control Codex from my phone
Turn local Codex sessions on macOS into a Telegram control surface you can actually use from your phone.
https://github.com/Asuka-wx/codex-telegram-bridge
One-line positioning:
Keep your existing ssh + tmux + Codex workflow, and use Telegram only as the remote layer for status, approvals, and follow-up input.
Why It Matters
No workflow rewrite: keep using local tmux + Codex instead of switching to a browser dashboard or remote desktop
Actually remote-usable: not just logs, but approvals, interrupts, and follow-up input
Clear multi-task control: one control topic plus task-specific topics for parallel work
Phone-friendly by design: useful when you are away from your machine but still need to keep work moving
Lower setup friction: one-command installer plus launchd service support
CyberMew commentedon Apr 29, 2026
@linear What ticket number is this a duplicate of?