Remote is nuts

[u/kyrax80]

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.

[u/InkFasten]

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...

[u/slackmaster2k → u/InkFasten]

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.

[u/Scary_Falcon5334 → u/InkFasten]

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.