Miblo for GitHub Copilot CLI
GitHub Copilot CLI connects through a hooks file of Miblo's own (miblo setup copilot), which Copilot loads next to yours.
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
- Copilot 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 Copilot CLI: run miblo setup copilot in a terminal (or /miblo:setup copilot in Claude Code).
- Sessions show on Miblo from your next activity.
miblo setup copilot- What changes: a hooks file of Miblo's own, ~/.copilot/hooks/miblo.json (or $COPILOT_HOME/hooks/), which Copilot loads next to your other hooks.
- Don't also install Miblo's Claude Code plugin into Copilot: each session would show twice.
- What shows: working, needs you (permission prompts and questions) and finished. Copilot reports no usage limits.
- On Windows, the hooks run through Git for Windows' sh.
- Undo: miblo setup copilot --remove.
From your phone
With Miblo+, you reply to your GitHub Copilot CLI sessions from your phone, wherever you are; every reply asks for your phone's passkey. Approvals keep GitHub Copilot 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.