FIELD GUIDE / 05

Build an AI Passport play with Codex

Open the play project in Codex, turn the idea into a verifiable task, then build, install, and iterate on hardware.

STEP / 01

Prepare the play project and a test device

Start with an AI Passport play project that already builds, plus a device reserved for development. Record the dependencies, build command, and a recoverable play version so environment, code, and hardware failures remain distinguishable.

A programmable AI Passport connected over USB — Establish a build, flash, and recovery baseline first

Complete one clean build of the original project
Keep an official or known-good recovery build
Connect the test device with a data-capable USB cable

STEP / 02

Open the play project in Codex

Give Codex the complete play project as its workspace. First ask it to read the project instructions, hardware configuration, existing examples, and build scripts, then summarize the paths it plans to reuse before making changes.

Prompt for the Agent

Please download and use this project as a reference:
https://github.com/folotoy/ai-passport
Help me build a wooden-fish tapping app.

The Codex project screen shown in the video — Choose Codex and let it understand the complete project first

Tip
Complete project context is more reliable than isolated snippets and keeps implementation, testing, and the final play in one workflow.

STEP / 03

Turn the play into a verifiable task

Tell Codex who the play is for, what appears after startup, how the three buttons behave, and what a successful result looks like. Require a completed build and flashable artifact, not source code alone.

Describing an AI Passport play in Codex — Turn the idea into a task with hardware constraints and acceptance criteria

Context and core goal
Screens, states, and text
Short- and long-press behavior for Up, Down, and Confirm
Sound, Bluetooth, networking, and storage needs
Definition of done, build command, and play output

STEP / 04

Let Codex implement, build, and fix errors

Have Codex change the code, run the project's existing build or test commands, and continue from actual errors. At the end, ask for the changes, verification results, play path, and any remaining risks.

Codex working through the project task — Keep implementation, building, error correction, and handoff together

Tip
Keep the full build error in the same task when something fails. Do not skip verification or treat unbuilt source as the finished result.

STEP / 05

Install the Codex build on AI Passport

Open the local play installer, select the play produced by Codex, verify the target device, and start installation. Keep USB connected until writing finishes, then restart and confirm that the device boots.

A Codex-built play running on AI Passport — The result must start and run on real hardware

Select the artifact from the current build
Do not unplug or close the page during installation
Keep device logs and the build identity if anything fails

STEP / 06

Use the device, then return feedback to Codex

Play through the complete experience away from the computer. Check display readability, one-handed controls, startup time, and recovery behavior. Give the reproduction steps, visuals, and logs back to the same Codex task for a focused rebuild.

Testing a custom mini game on AI Passport — Use real interaction feedback to drive the next Codex iteration

Keep each iteration focused on a few reproducible issues
Save a source commit and play backup for every usable build
Add screens, rules, or connectivity only after the core flow is stable