Miblo for Cursor
Cursor's own agent connects through hooks that cannot block anything (miblo setup cursor). The Claude Code extension inside Cursor uses the Claude Code plugin.
What shows
- Working
- Yes
- Needs you
- No
- 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
- Cursor has no “waiting for approval” hook that cannot also block commands, so Miblo shows working and finished, without “needs you”.
- 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
This is Cursor's own agent. The Claude Code extension inside Cursor uses the Claude Code plugin (Claude Code tab).
- Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
- Connect Cursor: run miblo setup cursor in a terminal (or /miblo:setup cursor in Claude Code).
- Restart Cursor.
miblo setup cursor- What changes: Miblo's hooks go into ~/.cursor/hooks.json, next to yours (backed up once, to hooks.json.miblo-backup). Only hooks that cannot block anything: your approval rules stay as they are.
- What shows: working and finished. Cursor has no hook for “waiting for your approval” that can't also block commands, so Miblo never shows “needs you” for Cursor.
- In the Cursor agent CLI (cursor-agent), a session shows working while tools run and finished when the run ends, or about 90 s after its last activity.
- Undo: miblo setup cursor --remove.
From your phone
With Miblo+, you reply to your Cursor sessions from your phone, wherever you are; every reply asks for your phone's passkey. Approvals keep Cursor'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.