Miblo for Codex
OpenAI's Codex CLI connects through hooks Miblo adds to its configuration (miblo setup codex), next to yours.
What shows
- Working
- Yes
- Needs you
- Yes
- Finished
- Yes
- Usage limits
- Yes
- Status and alerts on your phone (free)
- Yes
- Reply from your phone (Miblo+)
- Yes, idle sessions too
- Approve from your phone (Miblo+)
- Yes
- The 5-hour and weekly limits come from Codex's own session files, when you sign in with a ChatGPT plan.
- Nothing more leaves your computer: only the session's folder name, its state and the tool in use. No prompts, replies, files or diffs.
On Miblo's screen
How to connect
- Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
- Connect Codex: run miblo setup codex in a terminal (or /miblo:setup codex in Claude Code).
- Open Codex, run /hooks and trust the Miblo hooks. Codex only runs a new hook after that.
- Sessions show on Miblo from your next activity.
miblo setup codex- What changes: Miblo's hooks go into ~/.codex/hooks.json (or $CODEX_HOME), next to yours; the original is saved once as hooks.json.miblo-backup.
- No trusting again: the hooks run a fixed copy of Miblo's launcher in ~/.codex/miblo/, so updates never change them.
- What shows: working, needs you (approvals) and finished.
- Limits: the 5-hour and weekly ones come from Codex's own session files (~/.codex/sessions), after its first response, when you're signed in with a ChatGPT plan. An API key has no such limits.
- Undo: miblo setup codex --remove takes out only Miblo's hooks.
From your phone
With Miblo+, Codex's permission requests reach your phone with the exact command, and you reply to the session from wherever you are. Every approval and every reply asks for your phone's passkey.
You don't need the gadget: the Miblo app and your phone (with a free Miblo account) already show your sessions. The gadget puts it all on a screen on your desk, with a pet.