One of the issues with this new trend of vibecoding a million features, is that the (vibecoded) docs are labrynths of new features, and features that are deprecated or redundant with 2 month younger features.
But I can’t tell from these docs if the ChatGPT desktop app needs to remain running on your macOS/Windows host as a proxy, or if you can directly SSH from your phone to your Linux box with just Codex CLI.
When I tried it a couple of months ago, the CLI version didn't have that feature, it's only present on the desktop app. The docs you linked seem to confirm this:
>In the ChatGPT mobile app, open Remote to work with ChatGPT or Codex chats on a connected Mac or Windows device.
>Start in the ChatGPT desktop app on the host you want to connect.
>Open the ChatGPT desktop app on the host. Go to Settings > Connections > Control this Mac or PC,
Then there's the SSH thing
>Use an SSH host or managed remote development environment when the project already lives in a remote environment. Connect the desktop app host to that environment first;
>For SSH setup details, see connect to an SSH host.
At this point I feel that I need to combine it with other experimental vibecoded features? And the end result would be something that I can hack together with some ddns reverse polling thing. I know I can download an ssh terminal to my phone and connect to my computer by either opening a port, or doing some wacky network stuff. I don't see the value add in doing that by adding the commands I would have to run to some openai config file yaml like
> ssh-tunnel: tailscale > port: 8411
instead of making a bash script with
> tailscale -p 8411
tl;dr: The feature is desktop app dependent, and the desktop app is now on linux, rejoice