WORKFLOW 04 · POCKET TO PRODUCTIONDirection travels. Execution stays close to the files.
01 · PHONEStart or steerOpen the same Codex task, give direction, answer questions, review progress, and approve bounded actions.
02 · MACExecute locallyThe desktop app keeps access to the repository, terminal, browsers, and the exact working state.
03 · EVIDENCEReturn to proofRead the diff, screenshots, tests, deploy result, and live verification—not a vague “done.”

§1Remote Codex is not remote desktop

I am not squeezing a desktop UI onto a phone. I am continuing the same agent task from another screen. The Mac does the work because it holds the source, tools, credentials, and browser state. The phone is where I direct, clarify, approve, and inspect.

That distinction matters. Remote desktop asks me to operate a distant computer. Remote Codex lets me operate the work.

§2The setup I use

  1. On the Mac, I open the project in the Codex desktop app and sign in to the same account and workspace I use on my phone.
  2. I enable remote access for that desktop session and leave the app running.
  3. I keep the Mac awake, connected to the internet, and available to the tools the task needs.
  4. On the phone, I open Codex, choose the connected desktop environment, and continue the task.
09:12 PHONE — “Check the current live design before touching the page.”09:18 MAC — Source and production reconciled.09:26 PHONE — Approved the production deploy and IndexNow.09:34 EVIDENCE — Desktop, mobile, headers, feed, sitemap, and live URL verified.

The host must remain awake, online, and running the Codex desktop app. If any one of those conditions disappears, the remote control surface has nothing to connect to. OpenAI’s remote connections guide is the current setup reference.

§3Keeping the Mac available with Amphetamine

MAC UPTIMEAwake is infrastructure.

Amphetamine keeps an awake session alive

I use the macOS utility Amphetamine to prevent idle sleep during a remote work window. I choose a bounded duration or a clear trigger, keep power connected for long sessions, and end the session when the work is finished.

Closed-lid caveat: Amphetamine does not magically override every macOS closed-display rule. Apple’s reliable closed-display setup requires power and an external display. Without that setup, closing the lid may still put the Mac to sleep.

The safe mental model is simple: Amphetamine helps prevent idle sleep; it is not a guarantee that a closed, unplugged MacBook will remain remotely available. I test the exact physical setup before depending on it.

§4How the work moves between us

The best remote tasks are not giant instructions sent into a black box. They are checkpoints. I provide intent and authority. Codex inspects the live truth, makes the bounded change, and returns evidence. If a decision would change scope, publish publicly, spend money, or affect another person, it comes back to me.

BRIEFOne outcomeBOUNDARYWhat may changeCHECKPOINTWhat needs approvalPROOFWhat closes the task

This page is an example of that loop. I asked for the story. We checked the current live design instead of trusting an old template, saved the typography and colour system as durable context, built the page, deployed it, and tested the public result on desktop and mobile.

§5Prompts that work well from a phone

Inspect first. Tell me which production source is current.

Continue the same task. Do not widen the scope.

Show me the exact copy before publishing.

Deploy to production, then test the live URL on mobile
and desktop. Submit the changed URL to IndexNow only
after the live checks pass.

Short prompts work because the task already carries its files, decisions, and history. The thread becomes operational memory: not perfect memory, but enough continuity to avoid starting from zero every time I change devices.

§6The guardrails matter more remotely

The compact rule

  • The phone directs.
  • The Mac executes.
  • The thread preserves context.
  • Amphetamine protects the work window.
  • Evidence closes the loop.