If Pairing Does Not Finish
Pairing is not just "scan the QR code." After the iPhone saves the Host, the initial setup continues with a few more steps:
- confirm that the iPhone can reach Bridge
- import the
Projectlist - prepare the first workspace
- finalize the Host for normal use
That is why even if the QR scan succeeds, the problem can still be somewhere inside the pairing flow.
Where to look first
On the Mac
CodexPocketMacis running- in
General,RuntimeisRunningandHealthis visible - in
Pairing, QR,Copy Pairing URL, andCopy Pairing Codeare available - in
Details, bothCodex CLIandShellare detected
On the iPhone
- in
Hosts, check the Host state,Connection Test, andRetry Setup - in
Settings, check camera, local network access, andTimeout
Common causes and fixes
The QR code will not scan
Check these first:
- camera permission is allowed on the iPhone
- the QR code on the Mac is clearly visible
- glare or distance is not making the scan harder
If the camera is unavailable, use Copy Pairing URL or Copy Pairing Code from Pairing on the Mac, then paste it into the same screen on the iPhone.
Setup stops after Save as Host
The initial setup can continue for as long as 300 seconds. On the first connection, the Mac sometimes needs a little time to prepare Codex.
If it looks stuck, check these in order:
- in
Generalon the Mac, confirm thatRuntimeisRunning - check whether
Generalon the Mac shows any prerequisite warnings - confirm that the Mac and iPhone are on the same network
- run
Retry SetupfromHostson the iPhone
If the first setup fails, closing the waiting screen returns you to the previous screen and opens a sheet that shows the stage where it failed and the error details. You can close the sheet there and retry from the same place.
Even if you see Host initial setup did not finish within 300 seconds, the Host itself remains saved. Try Retry Setup before deleting it.
You see Authentication failed
This usually means the token on the iPhone no longer matches the token on the Mac. A common case is that Regenerate Token was used on the Mac while the iPhone still kept the old token.
Use one of these fixes:
- show the QR again in
Pairingon the Mac and import it again on the iPhone - if you use manual entry, replace the token with the newest one
If the old Host stopped working right after token regeneration, pairing again is the fastest fix.
You see Bridge URL or Token is not set
This is more common when the Host was added manually. The connection fails if either of these is missing:
Bridge HostorBridge URLBearer Token
If you are unsure, QR is safer than manual entry because it imports both the endpoint and token together.
The QR scans, but the connection fails somewhere else
The current release assumes the same local network. You can use the iPhone away from the Mac physically, but the Mac still has to be visible on the same network.
Pairing or follow-up connection will fail in cases such as:
- the Mac and iPhone are on different Wi-Fi networks
- the iPhone switched over to mobile data
- local network permission is off on the iPhone
Mac-side prerequisites that often block pairing
Check these in Details on the Mac:
Codex CLIbothcodexandcodex app-server --helpneed to workShellan executable shell needs to resolvegitnot required for pairing itself, but required for branch features
Also, if an old dev.codexpocket.bridge.plist remains under ~/Library/LaunchAgents, it can conflict with the app-managed Bridge. If General or Details shows warnings, clear those first.
When pairing again is the faster last resort
Pairing again is often faster if any of these are true:
- you used
Regenerate Tokenon the Mac - you changed the Bridge port
- you edited a manually entered Host many times and no longer trust which values are correct
- the Host is saved, but
Retry Setupkeeps ending in authentication or missing-field errors
In that case, delete the old Host on the iPhone and import it again from Pairing on the Mac.