I Updated This Website From a Train With Codex

I made changes to this website while riding the train into work.

And I do mean riding the train.

I did not even get a seat. I was standing there with my phone in one hand, trying to keep my balance every time the train lurched, doing that little commuter shuffle where you pretend you meant to step sideways.

I used Codex remote connections from my phone. I told Codex what I wanted changed, checked in on the work, gave it a couple of nudges, and the update was live before I got to the station.

What changed

OpenAI added remote connections for Codex.

Here is the plain English version.

Codex still runs on your computer, where your website or app project already lives. Your phone connects through ChatGPT so you can send instructions, answer questions, approve steps, and check the work without sitting in front of the machine.

Your phone is the remote. Your computer is the thing doing the work.

This matters because nobody wants to turn their phone into a tiny programmer cave. Debugging a website with one thumb while standing near the train doors sounds like punishment from a very specific technology court.

Why this matters for vibe coding

When you build with AI, projects can get stuck for surprisingly small reasons.

Codex asks a question. It needs a yes before running something. It finishes a first pass and waits for you to review it. Or it does exactly what you asked, which is when you realize your first instruction was not as clear as it sounded in your head.

Normally, those little pauses mean the project sits there until you get back to your computer. With remote connections, you can keep the conversation moving from your phone.

That might mean approving a safe next step while waiting for coffee. It might mean asking Codex to simplify a section of copy. It might mean checking whether a small update worked while your laptop stays in your bag.

For creators, freelancers, side-project people, and “I have an idea but not a free Saturday” builders, those scraps of time add up.

My train test

My test was this site.

I did not have a nice little table setup. I did not have a quiet corner. I did not even have a seat.

I was standing on the train getting jostled around like every other commuter with a backpack and mild trust issues about public transit balance.

The website project was already set up on my computer, so Codex could use the same files and tools I use at my desk. I did not have to recreate the project on my phone. I was not installing packages or squinting at code like I was defusing a movie bomb.

The whole loop was simple. I gave Codex the change, checked what it came back with, asked for a tweak, and approved the next step. My computer handled the actual website work while I tried to remain upright like a professional adult.

By the time I got to the station, the update was live.

That felt weird in the best way. My website was no longer trapped inside the hours when I was physically sitting at my desk.

How I think about it

Remote Codex is useful when the work is small enough to explain clearly and easy enough to check from a phone.

I would use it for things like fixing a typo, updating a link, drafting a blog post, changing button copy, asking why a page is broken, or checking whether the site still builds.

I would slow down for payments, logins, database changes, private user data, big redesigns, or anything where “oops” would be expensive. Remote access does not remove the need to pay attention. Rude, but fair.

For everyday website work, though, this feels immediately useful.

Setup notes before you try it

The setup starts on the computer where Codex is already running. You turn on mobile access in the Codex app, scan a QR code with your phone, and finish connecting it in ChatGPT.

Before you depend on it, check the boring stuff: Codex is installed and signed in, the computer is awake and online, your ChatGPT mobile app is updated, both devices use the same account and workspace, and the project already works on that computer.

Also check your approval settings. If you are new to this, keep Codex on a short leash until you know what the buttons do.

If your computer goes to sleep or loses internet, the phone connection cannot do much. The phone is the remote. The computer is still the engine.

A good first prompt

If you want to try this without getting yourself into a mess, start with something boring and safe:

Please make a small copy-only update to the homepage.
Before editing, tell me what you plan to change.
After editing, summarize exactly what changed and run the normal build/check command.
Do not commit or deploy anything unless I explicitly ask.

That prompt keeps the job small, makes Codex explain the plan, and separates “make the change” from “ship the change.” You can get looser later. Start boring. Boring ships.

Why I care

The part that clicked for me was the feeling of staying connected to the project without dragging my whole setup around.

I still do not want to code from a phone. I want to keep a real project moving when I am away from my desk.

A commute, a waiting room, the five minutes before a meeting, the awkward little gap where you are too early to go in but too late to start anything serious: those moments can now be enough to move a project forward.

You are probably not going to finish a whole startup between two stops. Relax.

But one useful change, one quick check, one answer to Codex, one small push forward? That feels very real.

Yep. I have the train receipt.