Continuing Codex work on Android

Back to the Codex learning hub

Goal and the Android's role

The Android sends requests and displays results; the connected host provides source files, terminal, dependencies and signed-in websites. Installing ChatGPT on the phone does not install Codex CLI or synchronize computer folders into a phone file manager. Read the mobile overview and Remote host setup to distinguish connection, task and execution.

Before starting: prepare the host and account

Update ChatGPT desktop on your Mac or Windows computer, use the same account/workspace as the Android and confirm Codex access. Extract the Small Steps pack, copy expected into codex-android-lab and retain the original. Check the five source files on the host before pairing. Use this fictional practice project rather than private production work.

Install or update official ChatGPT from Google Play, verifying OpenAI as publisher. The Google Play account is distinct from the ChatGPT login; confirm the intended host-matching account/workspace inside the app. With personal/work profiles or managed apps, identify which ChatGPT instance is open. Matching icons do not establish matching authentication or policy. Complete SSO, MFA or passkey requirements before Remote.

Add your own identification file on the host

Create remote-check.txt in codex-android-lab, replacing 01 below with your own marker. Inspect any existing file; do not overwrite another task's file. This sixth file supplements the five website files. Use a unique marker per copy, never an account, password or pairing code. Privately note the marker and full path; omit the marker from the later prompt.

ANDROID-PRACTICE-01

Step 1: scan into Remote with Camera

On the desktop host, open Settings → Connections → Control this Mac or PC, choose Set up or Add, authenticate and display the QR code. On Android, use a supported camera or scanner, frame the full code and open its detected link. Google documents Camera and Quick Settings scanning for Pixel; other brands follow their own instructions. Do not upload the QR image to a chat for model-assisted pairing.

If detection fails, check framing, focus and glare; on Pixel also check Camera scan suggestions. If Android asks which app should open the link, choose official ChatGPT and verify the intended work profile. If the link stays in the browser, check app version and login before restarting setup from the host. Do not change all URL defaults for one pairing or publish pairing links, codes or account screenshots.

Confirm account, workspace and host in the phone setup. Success should show the host in Remote and let you select codex-android-lab and open a Codex task. A login-complete page alone is insufficient. If the listed machine is wrong, revisit the intended host's pairing setup. Diagram 1 is the Android entry, 2 the selected host and 3 the verifiable project result.

Step 2: send a precise file-read request

Paste the following into the host project's task composer in Remote. Check that keyboard autocorrection has not altered filenames or function names. This is a prompt, not a terminal command for Android. Send once, observe the response and record identifying task information so you can return after switching apps.

Read this Small Steps project without changing files. Confirm the working directory and inspect app.js and core.mjs. Identify the localStorage key, the field that records completion, and the function that rejects blank task titles. Cite the file for each answer. If a file is unavailable, report that instead of guessing.

Expect mokaair-codex-todo-v1 from app.js, completed and addTask's blank-title check from core.mjs, and the actual working directory. Generic todo-app advice is insufficient; ask which file was inspected. For a wrong directory, stop and select the correct host/project. A plausible explanation alone does not prove the connection reached your files.

Read a marker unique to this copy

Read remote-check.txt from this task's project now.
Quote its exact content and report the absolute file path and the tool used to read it.
Do not edit files or infer the marker from earlier messages.
If the file is missing or cannot be read, report that limitation.

Compare the reply with the marker and path in your host-side note and with the tool read record. The host's displayed name and this file marker are different facts. To check freshness, wait for the task to finish, change and save only the marker on the host, then send the same read request without supplying the new value. A stale value, missing tool evidence or mismatched path remains unverified; check saved state, host and copy first.

Step 3: follow up, review approvals and inspect progress

In the same project, explain what happens when I add Read and Build, complete Read, and choose Completed. Then explain an empty task title. Separate code you inspected, tests actually run, and checks still pending. Do not edit or clear stored data.

With only Read and Build initially present, expect Completed to show only Read and blank titles to be rejected. Account for any other stored tasks; this read-only request leaves them unchanged. Separate inspected code, executed tests and pending UI checks. Verify the predicted behavior in the computer's local preview.

If an approval appears, inspect the operation, directory and scope against your request. This read-only exercise does not need new external accounts, website publication or deletion. Review long commands on the host if the phone view is insufficient. If no approval appears, inspect the original Remote task's state instead of repeatedly creating new tasks.

Step 4: leave and return to the same task

After the read-only response finishes, switch to another Android app, then return through recent apps or the home screen to ChatGPT → Remote and the same host/task. Navigation gestures/buttons vary by phone, so no universal position is assumed. Inspect the last response, then request a fresh directory read; cached text does not prove the host is online. If the login environment differs, check personal/work profiles before recreating projects.

Notifications signal completion or attention; they do not validate results. Open the task even without a notification. If the host sleeps, disconnects or closes the app, restore it and inspect whether the previous request finished. For later writable tasks, avoid resending create/submit actions merely because the phone disconnected. This read-only exercise teaches recovery first.

Completion checks and common misunderstandings

A host's localhost URL entered in Android browser points to the phone, not the computer. Review host-provided results or screenshots in Remote and use the computer for local preview; public preview/deployment is a separate step. Manage access through host setup, and check task cancellation separately. Signing out does not automatically delete pairings.

Finish in the same task with a handoff of host/directory, inspected content, unrun tests and next steps, then verify on the computer. Android does not need Node.js to invoke host tools; dependencies belong on the execution host. Continue with cross-device work and context handoff. Switching to iPhone uses equivalent checks without rewriting the project.

On the host, remove only the remote-check.txt created in this exercise. Keep the five website files and never delete or overwrite pre-existing files. The marker and code requests are read-only. Record pairing or product operations you did not perform as untested.

Back to the Codex learning hub

Read the full description

Three numbered stages: identify the starting point, perform the exercise, and verify the result. Original illustration, not a product screenshot.

• AI tools
• Tutorials
• Codex