Run Codex from your phone
What works
| Feature | Codex |
|---|---|
| Grid preview, status and Inbox | Yes |
| Chat and Terminal | Yes, with herdr's Codex hook |
| Remaining context ring | Yes |
| Blocked notifications | Yes, without Approve or Deny |
| Answering prompts | Terminal buttons or typing in the composer |
| Plan usage | Monthly credits for a credit-metered workspace |
| Resume in New task | Yes |
Set up
-
Install herdr's Codex hook, and run it again after every herdr update:
herdr integration install codexThe hook tells herdr which Codex session runs in each pane; Chat reads that session. herdr 0.9.5 installs version 10 of the hook, which removes the turn hooks 0.9.4 added (Codex warns "clamping Interrupt hook timeout" while they remain).
collied doctorwarns when it is missing or older, once Codex has its~/.codexfolder (or$CODEX_HOME). -
Start Codex tasks from the phone, or start Codex with
--no-daemonyourself.
Why --no-daemon
New Codex tasks started from collie run codex --no-daemon, so each pane reports its own session, including after /new or a resume. This costs a server startup and some memory per window.
Sessions already running on a shared daemon are not changed. To move one over, finish the current turn, then relaunch it in the same pane:
codex --no-daemon resume <session-id>
Use the session's real ID, not one guessed from the folder.
Plan usage
For a credit-metered workspace, the Usage view shows the monthly used and allowed credits and the reset date. collied reads them from the local Codex app-server every five minutes; Codex's sign-in token stays with Codex. The row clears after you sign out or switch to an account without a monthly limit.
Status and done alerts
herdr reads Codex's status from its screen. If Codex statuses or done alerts look wrong, see Troubleshooting.
Startup prompts
A startup prompt, such as folder trust or Codex's update picker, stops a new task with a message. Answer it in Terminal; collie never types into the update picker.