Miblo for Qwen Code
Alibaba's Qwen Code connects through hooks in its settings.json (miblo setup qwen), 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+)
- Yes
- Qwen Code's own permission prompts reach your phone; what it allows by itself stays allowed.
- 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, Miblo Hub or the Claude Code plugin.
- Connect Qwen Code: run miblo setup qwen in a terminal (or /miblo:setup qwen in Claude Code).
- Sessions show on Miblo from their next activity.
miblo setup qwen- What changes: Miblo's hooks go into hooks in ~/.qwen/settings.json (or $QWEN_HOME), keeping everything else, comments included. Before every change the file is copied to settings.json.miblo-backup-<time> (the newest 3 are kept).
- What shows: working, needs you (permissions) and finished. Qwen Code reports no usage limits.
- With Miblo+: approve from your phone (once, deny, deny with a reason), the whole conversation on your phone and replies when it ends its turn; idle inside tmux or GNU screen, it gets them right away.
- Undo: miblo setup qwen --remove.
From your phone
With Miblo+, Qwen Code'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 Miblo Desk: Miblo Hub and Miblo Remote (with a free Miblo account) already show your sessions. Miblo Desk puts it all on a screen on your desk, with a pet.