Miblo for Gemini CLI
Google's Gemini CLI connects through hooks in its settings.json (miblo setup gemini), keeping everything else, comments included.
What shows
- Working
- Yes
- Needs you
- Yes
- Finished
- Yes
- Usage limits
- No
- Status and alerts on your phone (free)
- Yes
- Reply from your phone (Miblo+)
- Yes, at the end of the turn
- Approve from your phone (Miblo+)
- No
- Gemini CLI does not report usage limits, so Miblo shows its sessions and alerts.
- 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 Gemini CLI: run miblo setup gemini in a terminal (or /miblo:setup gemini in Claude Code).
- Sessions show on Miblo from your next activity.
miblo setup gemini- What changes: Miblo's hooks go into the hooks of ~/.gemini/settings.json (or $GEMINI_CLI_HOME/.gemini/), keeping everything else, comments included. Before every change the file is copied to settings.json.miblo-backup-<time> (the newest 3 are kept).
- Comments inside hooks itself make setup stop and say what to do.
- With Gemini's folder trust on, hooks run only in trusted folders.
- What shows: working, needs you (confirmations) and finished. Gemini reports no usage limits.
- Undo: miblo setup gemini --remove.
From your phone
With Miblo+, you reply to your Gemini CLI sessions from your phone, wherever you are; every reply asks for your phone's passkey. Approvals keep Gemini CLI's own flow.
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.