upvote

points

by pickleRick2438 hours ago |
comments
upvoteby weird-eye-issue1 hours ago|
next
[-]
For major new features on my SaaS this is exactly what I do on my phone/laptop sometimes over days or weeks. I never look at the code until I get a feeling that it's far enough along and then I will hop into the actual code and start manually making changes or using CC locally to make the changes iteratively over weeks until it's ready for release. In the early stages of a major new feature/product it can be counterproductive to closely monitor the AI. Of course like you said in your comment this requires very very strong knowledge of the code base and a lot of experience with using the agents in the first place. But once you can do this sort of workflow it's very powerful because you can do this in parallel with other work (just an hour or two per day over a week or two on your phone can get you to a really good first draft even on a major new feature/product. And of course I'm not saying it's ready for production that can still take weeks but that's not really the point)
reply
upvoteby nextaccountic8 hours ago|
prev|
next
[-]
But what if the code is on my laptop? Alongside the tools needed to work with it

Case in point, I have a Rust project with a target/ directory with about 10GB. Compile times from scratch takes about 10 minutes. (I do not love this)

With this mobile app I need to upload the code to the cloud, right? Or does OpenAI expects me to compile huge projects on my phone?

reply
upvoteby pickleRick2438 hours ago|
parent|
next
[-]
No, the phone connects to your local device. This isn't "codex web" on mobile. Basically you work through your desktop on your phone. So to be clear, there are security risks (you can wipe your entire desktop from your phone).
reply
upvoteby andy12_4 hours ago|
parent|
[-]
Not if you use Linux; app not available yet.
reply
upvoteby odiroot2 hours ago|
parent|
next
[-]
You can run Codex Desktop on Linux. It's on AUR already. Granted, just a repacked ASAR from Windows version but still does work quite well. Haven't tested connection to mobile yet but the integration with cloud environments already works.
reply
upvoteby andai3 hours ago|
parent|
prev|
[-]
The announcement doesn't make this very clear, but I think this talks to the Codex CLI, not the Codex App? (Or possibly both)
reply
upvoteby andy12_3 hours ago|
parent|
[-]
For now it appears that it talks only to the Codex App. Some users in this thread are saying that apparently the Codex CLI will support it on the next official release.
reply
upvoteby cortesoft7 hours ago|
parent|
prev|
next
[-]
Not sure about how it works with Codex now, but with Claude you can just start a terminal session of claude code with your code checked out locally on your computer, and then enable remote control which lets you control that session from your phone.

So basically, it is like you are typing on your terminal on your computer from your phone.

reply
upvoteby skybrian8 hours ago|
parent|
prev|
next
[-]
I tried Codex web. It kinda sucks and OpenAI doesn't seem to be promoting it? Look elsewhere if you want a Linux VM in the cloud. (I quite like exe.dev and they do have good mobile support.)
reply
upvoteby az2267 hours ago|
parent|
[-]
It's beyond terrible. Like they're routing to gpt4o mini with low effort behind the scenes. Just let us pick the model and the effort.
reply
upvoteby LoganDark8 hours ago|
parent|
prev|
[-]
The processes you're controlling are on your computer, similarly to Claude remote control.
reply
upvoteby 5 hours ago|
prev|
next
[-]
deleted
reply
upvoteby LoganDark8 hours ago|
prev|
next
[-]
I've been vibe-refactoring a fork of get-shit-done (a skill collection for coding agents) for about the past week. I've had to revisit the same ideas multiple times because the agent doesn't always get it right at first, but it's still so much faster than I could have been at the same work + it's already mostly working (I've been dogfooding it for a day or two now). And I have gotten by just bringing up issues I notice from the LLM's implementation comments, rather than actually inspecting the code even once so far.

(The refactor's been to support Jujutsu VCS.)

reply
upvoteby bugbuddy4 hours ago|
prev|
[-]
> i.e. not looking at the actual code

You must be kidding me.

reply
upvoteby andai3 hours ago|
parent|
next
[-]
> There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists.

https://x.com/karpathy/status/1886192184808149383

Forgetting code exists is by definition not suitable for serious work. However, OP said in the following paragraph, that this would be a first draft, and that the code would actually be reviewed and tested properly before being integrated.

At which point it is by definition no longer vibe coding, because you do care about the code! It's just an AI assisted workflow, but now we call all of those vibe coding for some reason. (Naming things is hard!)

If vibe coding means not caring about the code, then a literal translation of the term would be "not caring about coding" coding.

reply
upvoteby paulcole8 minutes ago|
parent|
[-]
> Forgetting code exists is by definition not suitable for serious work

This is just like everyone who says, “An iPad is not suitable for serious work.”

By which they (and you) generally mean, “What I do is serious work. What you do is unserious work.”

I think I do serious work – I mean they pay me for it? And I have only copy/pasted and just run whatever code’s been generated by AI for the past 12 months or so. Whenever I can I just let the AI run it itself.

Sad to learn that I’ve been so unserious all this time.

> Naming things is hard!

Indeed.

reply
upvoteby magicalhippo4 hours ago|
parent|
prev|
next
[-]
What OP said works quite well for a lot of tasks, and if you've set up base instructions on coding style they (Codex, Claude) generate code accordingly.

A key point is that after the "vibe" session you should also have a lot of tests written. So they can easily refactoring the code afterwards if there are major aspects you don't like when you get back to your desktop.

reply
upvoteby scrollaway4 hours ago|
parent|
prev|
next
[-]
I find funny the trend of software engineers being shocked at the idea that someone would issue a set of instructions to a coder and not look at the code, or only glance at it.

How do you think the world has worked for the past thirty years? AI has just caught up with human skill is all.

reply
upvoteby rvz3 hours ago|
parent|
prev|
[-]
Unbelievable. This is the silent de-skilling of this industry.

Imagine saying that you don't need to look at the roads or have no hands on the wheel whilst driving because someone-else said that the car can 'drive' itself; therefore, no need for anyone (including taxi drivers) to learn how to drive.

Just because a machine can generate plausible looking code does not mean you don't need to look at it or not know how it works or why it doesn't work.

reply