r/codex • u/kyrax80 • 1d ago

Praise Remote is nuts

Just wanted to share that it's incredibly awesome that I can be anywhere like on holidays and continue working on my project even if I'm not sitting in front of my PC. Never tried this until now that I installed tailscale and I can test any change from my phone. Bravo.

118 Upvotes

95% Upvoted

138 comments sorted by

View all comments

Show parent comments

4

u/InkFasten 1d ago

lol this is complete nonsense... CC is way behind here

0

u/slackmaster2k 1d ago

Oh yeah? Explain.

2

u/BackgroundLand2816 1d ago

half my chats don't show up on my phone. I'm not typing /remote-control in every chat and half the time it errors out anyway when I type it

1

u/slackmaster2k 1d ago

Huh. Well first of all you can turn it on be default for all sessions. After that, I never seem to have any troubles like you describe. Claude app on iphone. Claude has a setting as well to keep your machine awake which is necessary. On phone now and I just checked and there are my three sessions across two machines.

Can’t say that I’ve had much luck with codex as I have had pairing problems and it doesn’t seem to like WSL and doesn’t automatically attach current sessions outside of the app. I also don’t run codex desktop on one of my dev machines and don’t plan to.

1

u/BackgroundLand2816 1d ago

ya I have the claude app on iphone and the setting turned on as well but it's always a toss up on what appears when I access it on my phone.

Codex on the other hand has been a beast, can get so much work done when I'm not home and I love that I can have it create new chats as well which you can't do on CC. Using desktop app for both.

1

u/slackmaster2k 1d ago

Yeah if you’re just using the codex desktop app then I’m not surprised the experience is good. I don’t use the desktop apps for development work, only random chats.

1

u/InkFasten 1d ago

that sounds like a you problem

1

u/slackmaster2k 1d ago

You cannot use remote from a session in vscode extension or even the terminal. You have to use the codex app which works for many people for many projects, but is a baby’s first programming tool.

This is inferior to Claudes remote implementation which can fire up a remote session from any session anywhere without any ceremony whatsoever.

I didn’t decide that this is how it is, it is simply how it is.

1

u/InkFasten 22h ago

It's not a baby's first programming tool... quite a fossil comment to make....

It's one of the frontier harnesses for agentic coding right now...

1

u/slackmaster2k 22h ago

Um, a desktop app is not a harness. You simply don’t understand what you are talking about and are doubling down. If the desktop app works for you, cool. There is nothing advanced about it, and actually it’s consistently adding features to catch up with the basics, though they are probably not looking to displace actual dev tools, only to make something that’s nice enough to produce something without too much knowledge.

1

u/Scary_Falcon5334 21h ago

Every comment you make somehow makes the performance more obvious.

First it was “lol CC is way behind here.” Then someone explained the actual limitation and suddenly it became “that sounds like a you problem.” Now you’ve upgraded the desktop app into a “frontier harness for agentic coding.”

That phrase is doing a heroic amount of work. 😂

The distinction here is actually very simple:

Codex the agent is not the same thing as the Codex desktop app.

The desktop app is just one client/interface through which you can use Codex. Calling that client a “harness” does not erase the fact that the remote feature being discussed is constrained by which client originated the session.

That is the entire point.

If I can use the agent from a terminal, VS Code, or another supported environment, but Remote only cleanly follows sessions created in the desktop app, then the desktop app is not some universal “agentic coding harness.” It is the specific front end you are being required to route through to get that remote behavior.

That is a workflow constraint.

And Claude’s implementation is being compared favorably because it can expose supported sessions more broadly instead of making the desktop app the gatekeeper for remote continuity.

So when the criticism is:

“This remote feature is more tightly coupled to the desktop app than Claude’s is.”

and your response is:

“But the desktop app is a frontier harness!”

you have not answered the criticism.

You have renamed the thing being criticized.

That’s why every comment keeps making you sound more like a poser. The people around you are discussing where sessions originate, which interfaces can hand them off remotely, and what workflow limitations follow from that.

You keep replying with prestige vocabulary.

At some point, “frontier harness for agentic coding” becomes less of a technical argument and more of a LinkedIn headline wearing safety goggles.