codex - 💡(How to fix) Fix Auto-forward remote dev server ports to local machine in Codex Desktop remote sessions [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#21294Fetched 2026-05-07 03:42:33
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

App

What feature would you like to see?

Codex Desktop now supports remote development sessions, but local preview still requires manual SSH port forwarding.

When the agent starts or detects a dev server on the remote host, Codex should offer to forward that remote port to the local machine and make it available in the in-app browser/local browser, similar to VS Code Remote SSH port forwarding.

Example:

  • Remote session runs npm run dev
  • App listens on remote 127.0.0.1:5173
  • Codex Desktop automatically exposes it locally as http://127.0.0.1:5173 or another available local port
  • The in-app browser can open the forwarded URL directly

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING