Skip to main content
Version: next

Start on Mac

The execution side of CodexPocket is the Mac. The iPhone is the control surface, so you can start as soon as Codex works normally on the Mac and CodexPocketMac can wait for connections.

Illustration of the Mac side acting as the CodexPocket control center

How to get CodexPocketMac

Download the Mac app Read the release notes Run from source

Note: download the .dmg from GitHub Releases, then install it on your Mac.

The current public Mac stable is 0.1.3. In the normal path, download the notarized DMG and start from there. Use the mac-app README Quickstart only when you want a source build for development or verification.

The short version first

If you already use Codex on the Mac every day, there is not much new to do.

  1. Launch CodexPocketMac.
  2. Confirm that codex is available.
  3. Confirm that the workspace you want is present in Codex App.
  4. Confirm that Bridge is running.
  5. Scan the pairing QR from the iPhone.

You only need Git when you want branch-related features. Most people do not need to touch ports, tokens, or manual project registration first.

Find the right page fast

If you want to...Read this page
know the minimum first checksFirst Things to Check
continue with a Codex App-based workflowInstall the Codex App
confirm the codex CLI setupInstall Codex CLI
enable Git for branch actions tooMake Git Available
add a project by handRegister a Project
finish with Bridge startupStart Bridge

What the Mac side is responsible for

  • starting and stopping Bridge
  • managing the Project list shown to the iPhone
  • running Threads and Exec through codex
  • showing the pairing QR
  • exposing state and logs

Where to look in the Mac app

  • General the place for Bridge on/off, launch-at-login, and the overall state
  • Projects the place to confirm the workspaces imported from Codex App and the projects shown on iPhone
  • Pairing the place to show the QR code, pairing URL, and pairing code
  • Details the place to confirm whether codex, git, and the shell were detected
  • Logs the place to inspect stdout and stderr when Bridge is not behaving

How to read this section