Add a first-class Remote section to the Codex Desktop sidebar
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
Research direction
Start by reviewing the existing Remote Control infrastructure and the settings/connections workflow in Codex Desktop, then locate the sidebar entry point. Done should expose a persistent Remote destination where users can pair securely, select a primary workstation, continue or start work, inspect diffs and terminal output, approve actions, and monitor running sessions.
Written by the indexing model from the issue text.
Description
What feature would you like to see?
Please add a clearly visible Remote section to the Codex Desktop sidebar, matching the Remote entry in the ChatGPT mobile app.
Codex Desktop already has remote-control capabilities through settings/connections, but the workflow is difficult to discover and does not feel like a first-class part of the desktop product. A dedicated sidebar destination would make it obvious that one desktop can connect to and control another Codex host.
Requested workflow
- Codex runs on a primary workstation or build machine.
- A second computer running Codex Desktop signs into the same account or pairs securely.
- The second computer opens Remote from the sidebar.
- It selects the primary workstation.
- The user can continue existing threads, start new tasks, inspect diffs and terminal output, approve actions, and monitor running work.
This request is specifically about Codex-to-Codex remote control, not generic SSH access or remote server administration.
Suggested sidebar
Projects
Automations
Plugins
Remote
Why this would help
- Makes desktop-to-desktop Remote Control easy to discover.
- Provides feature parity with the ChatGPT mobile Remote experience.
- Lets users keep repositories, credentials, build tools, and execution on the host machine.
- Makes it practical to continue long-running Codex work from a laptop or another desktop.
- Creates a natural place for host status, pairing, permissions, active sessions, and connection diagnostics.
Ideally, this would reuse the existing Remote Control infrastructure and expose it as a persistent, first-class desktop surface rather than hiding it under settings.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- Avg merge
- 1m
- Merged PRs (30d)
- 1k
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openai/codex
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug CLI windows-os
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
macOS sandbox blocks hw.optional.arm64 sysctl, causing Flutter to misdetect Apple Silicon as x64 Openbug CLI sandbox
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug CLI TUI
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
CLI config enhancement skills
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
A-linter
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxc-project/oxc#26863 ·