Miblo for OpenCode
OpenCode connects through a small Miblo plugin (miblo setup opencode) that only watches its events and never blocks anything.
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, idle sessions too
- Approve from your phone (Miblo+)
- Yes
- Each session's tokens and cost show in miblo status.
- 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 OpenCode: run miblo setup opencode in a terminal (or /miblo:setup opencode in Claude Code).
- Restart OpenCode, which loads its plugins at startup.
miblo setup opencode- What changes: one small file, ~/.config/opencode/plugins/miblo.js (under $XDG_CONFIG_HOME when set). opencode.json is not touched; a different miblo.js already there is saved in ~/.config/opencode/miblo-backup/ first.
- It only watches OpenCode's events and never blocks or changes anything.
- What shows: working, needs you (permissions and questions) and finished; each session's tokens and cost show in miblo status. No usage limits.
- Undo: miblo setup opencode --remove.
From your phone
With Miblo+, OpenCode'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.