Reference

CodexPocket is built for continuing Codex work while you are away from the Mac. The day-to-day flow usually lives in the iPhone, Mac, and Usage sections, but when you are unsure what a term means or how something behaves, this section is the fastest place to sort it out.

What this section explains

• Where things run Check which work happens on the Mac and what the iPhone is responsible for.
• What works well and what to watch for See which tasks fit the iPhone well and which ones are usually faster back on the Mac.
• Glossary Look up short explanations for terms such as Host, Bridge, Project, and Thread.
• Display language See where to change the language for the docs, the iPhone app, and the Mac app.
• Why the Mac is required See the companion model, network assumptions, permissions, and data flow in one place.
• App Store feature brief Share the value, core flow, and launch scope in a short page made for editorial context.
• Release tracks and updates Decide whether you should read stable or next.

Three assumptions to keep in mind first

• The real Codex process, workspace access, and Git operations all happen on the Mac.
• The iPhone is the screen you use to open a Project, continue a Thread, and check status.
• When you are stuck, the fastest places to inspect are General, Bridge, Pairing, Logs, and Details on the Mac.

Common questions this section answers

• The iPhone disconnected. Did the work stop too? Start with Where Things Run.
• How far can I go from the iPhone alone? See What Works Well and What to Watch For.
• I want a quick explanation of queue or steer. Open Glossary.
• I changed the language, but project names and answers did not change. See Display Language.
• Why does an iPhone app need a Mac in the first place? Open Why the Mac Is Required.
• I need the public page to use for an App Store featuring nomination. Open App Store Feature Brief.
• I am not sure whether this page matches my app version. See Release Versioning.