Codex app launches VS Code Remote SSH on port 22 instead of configured 443

Summary

When opening a remote project in VS Code from the Codex app, the generated VS Code Remote SSH connection ignores the SSH connection's configured port 443 and instead attempts to connect to the default SSH port 22. This causes the VS Code connection to time out and prevents the project from opening.

Expected behavior

Codex should use the port configured on the SSH connection, in this case 443, when launching VS Code / VS Code Remote SSH for the remote environment.

For example, the SSH command or generated SSH config should include the configured port:

Port 443

or:

ssh -p 443 ...

Actual behavior

VS Code Remote SSH attempts to connect to port 22:

ssh: connect to host console.d.run port 22: Operation timed out

The connection command shown in VS Code's Remote SSH output does not include -p 443, even though the Codex app SSH connection configuration shows Port 443.

Steps to reproduce

1. In the Codex app, configure an SSH connection to a remote environment.
2. Set the SSH connection port to 443.
3. From Codex, click the VS Code entry point for the remote environment.
4. Observe the VS Code Remote SSH output.

Impact

Remote projects cannot be opened in VS Code from Codex when the remote environment is reachable on 443 but not on the default SSH port 22.

Evidence

Screenshots are available and should be attached to this issue:

1. VS Code Remote SSH output attempting port 22 and timing out.
2. The VS Code entry point used from the Codex app.
3. The Codex app SSH connection configuration showing Port 443.

Note: I attempted to attach the screenshots through the GitHub web issue UI, but Chrome automation was blocked by another extension UI. I will add the screenshots in a follow-up comment when the browser can accept file upload/paste automation.