# Miblo

> A desk gadget and app that show your Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode and Cursor sessions, tell you when the AI needs you and show your limits.

Miblo is made by Devyzi (Devyzi Internet Soluções LTDA), Brazil. Site: https://miblo.ai (Portuguese) and https://miblo.ai/en (English). Contact: contato@miblo.ai.

## Facts (English)

### What is Miblo?

A little desk cube that shows your AI coding sessions, tells you when one needs you and keeps your usage limits in sight.

Miblo shows the sessions of the AI coding tools on your computer: Claude Code (terminal, the desktop app's Code tab, the VS Code, Cursor and JetBrains extensions), Codex, GitHub Copilot CLI, Gemini CLI, OpenCode and Cursor's own agent. It runs on macOS, Windows and Linux, WSL included, and does not depend on Claude Code: the Miblo app finds the tools you have.

### Which AI coding tools does Miblo work with?

Claude Code, Codex, GitHub Copilot CLI, Gemini CLI, OpenCode and Cursor. Every one's sessions show in a single list.

- Claude Code: working, needs you, finished, usage limits.
- Codex: working, needs you, finished, usage limits.
- GitHub Copilot CLI: working, needs you, finished.
- Gemini CLI: working, needs you, finished.
- OpenCode: working, needs you, finished.
- Cursor: working, finished.
- Not supported (Cloud sessions) claude.ai/code and the cloud sessions started from the Claude desktop or mobile app. They run away from your computer and can't reach the Miblo on your network.
- Not supported (GitHub Copilot's Claude agent) it doesn't run plugin hooks.

- [Miblo for Claude Code](https://miblo.ai/en/tools/claude-code)
- [Miblo for Codex](https://miblo.ai/en/tools/codex)
- [Miblo for GitHub Copilot CLI](https://miblo.ai/en/tools/copilot-cli)
- [Miblo for Gemini CLI](https://miblo.ai/en/tools/gemini-cli)
- [Miblo for OpenCode](https://miblo.ai/en/tools/opencode)
- [Miblo for Cursor](https://miblo.ai/en/tools/cursor)

### How much does Miblo cost?

The app, the Claude Code plugin and the command line are free, with or without the gadget.

The Miblo gadget costs R$149.90 at the miblo.ai store, shipped within Brazil.

Miblo+, optional, costs R$9.90 a month or R$99.00 a year. Miblo on your phone, away from home. See the AI's latest messages, reply and approve permissions from anywhere, on any network.

- [Buy Miblo](https://miblo.ai/en/buy)
- [Miblo+](https://miblo.ai/en/plus)

### Can I control Claude Code and Codex from my phone?

Install the Miblo app on your computer and sign in with your Miblo account. On your phone, open miblo.ai/app, sign in to the same account and type the 6-digit code your computer shows. Your phone then shows your sessions and limits and tells you when a session needs you. With Miblo+, you also approve permissions, reply to the AI and start new tasks.

Yes, with Miblo+, in every AI tool Miblo shows: Claude Code, Codex, GitHub Copilot CLI, Gemini CLI, OpenCode and Cursor. While a session works, your reply goes in when it finishes its turn; when it's idle, it wakes up and answers (Claude Code, Codex and OpenCode). Every reply asks for your phone's passkey.

Yes, for free: your phone gets a notification when a session needs you, even away from your desk. The notification only says that a session needs you, never which one or what. Cursor has no such alert, because it does not report when it waits for approval.

- [Remote control](https://miblo.ai/en/remote-control)
- [Approve Claude Code permissions from your phone](https://miblo.ai/en/remote-control/approve-claude-code-permissions)
- [Reply to your AI from your phone](https://miblo.ai/en/remote-control/reply-to-ai-from-phone)
- [Check your Claude limits from your phone](https://miblo.ai/en/remote-control/claude-limits-on-phone)

### Do I need the gadget to use Miblo?

You don't need the gadget either: with no Miblo on your desk, the app, the pet and your sessions' status (on your phone too, with a free Miblo account) already work, and Miblo+ stays the paid part. The gadget adds a screen and a pet on your desk, and visits between Miblos. The installers ask whether you have one; without it, they finish with no error.

### How do I install Miblo?

You don't need the app: the command line and the plugin do everything. These are three ways to install the same Miblo on your computer; pick the one that suits you.

macOS or Linux: curl -fsSL https://miblo.ai/dl/install.sh | sh

Windows (PowerShell): irm https://miblo.ai/dl/install.ps1 | iex

- Plug Miblo into a 5 V / 1 A USB supply. The screen shows a QR code and the network name Miblo-Setup-XXXX.
- Scan the QR code with your phone (or join that network). The setup page opens by itself.
- Pick your Wi-Fi network and type the password. It must be 2.4 GHz with WPA2, and the same network as your computer.
- Once connected, the screen shows “Wi-Fi connected”, a 4-digit code and Miblo's IP.
- On your computer, download and open the Miblo app (below). It finds your AI tools, installs Miblo, turns on automatic updates and pairs. Rather not use the app? Use the command line or the plugin (Install section).

- [Download the app](https://miblo.ai/en/downloads)
- [Docs](https://miblo.ai/en/docs)

### Is Miblo safe? What leaves my computer?

Never in the way: every hook gives up within 3 seconds and always lets the AI carry on.

Privacy: nothing more leaves your computer than the session's folder name, its state and the tool in use. No prompts, replies, files or diffs.

- End-to-end encrypted (AES-256-GCM): the key is made on your computer and reaches each phone locked to that phone's own key. miblo.ai stores and relays only ciphertext.
- Notifications only say that a session needs you, never which one or what.
- The server keeps just the last encrypted frame, for 10 minutes, with no IP address.

### Who makes Miblo?

Miblo is made by Devyzi (Devyzi Internet Soluções LTDA) in Brazil. Contact: contato@miblo.ai.

# Documentation (English)

## Install

Source: https://miblo.ai/en/docs#install

You don't need the app: the command line and the plugin do everything. These are three ways to install the same Miblo on your computer; pick the one that suits you.

You don't need the gadget either: with no Miblo on your desk, the app, the pet and your sessions' status (on your phone too, with a free Miblo account) already work, and Miblo+ stays the paid part. The gadget adds a screen and a pet on your desk, and visits between Miblos. The installers ask whether you have one; without it, they finish with no error.

[Own a GeekMagic SmallTV Ultra? Install Miblo on it](https://miblo.ai/en/bring-your-own-device)

### App

The Miblo app is the no-terminal way: the same steps as the command-line installers, behind a window. It finds your AI tools (Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode and Cursor), installs Miblo, connects the ones you tick and pairs your Miblo. It never asks for an administrator password.

Download the Miblo app: https://miblo.ai/en/downloads

- macOS or Linux (Terminal): `curl -fsSL https://miblo.ai/dl/install.sh | sh`

- Windows (PowerShell): `irm https://miblo.ai/dl/install.ps1 | iex`

#### What the app keeps at hand

- Menu bar or tray: an icon with your sessions, the 5-hour and weekly limits and today's summary.
- My Miblos: the settings page, rename, blink, remove and pair another Miblo.
- AI tools: one switch per tool, Claude Code included.
- And more: Phone, Updates (Miblo and the firmware, with the code on the screen) and Shortcuts (meeting, focus, timer, message, blink).

It is a convenience, never a requirement: everything the app does can be done from the command line or the plugin, and all three can live on the same computer.

#### After that

1. Pair your Miblo (if you have one): at the end of the install the app asks whether there is a Miblo on your desk, Pair now or Later. To pair later, open My Miblos › Add a Miblo.
2. Phone app (optional): your sessions, alerts and limits on your phone, end-to-end encrypted. It needs a Miblo account; see Phone app, further down.
3. Miblo+ (optional): a subscription that adds conversations, replies, approvals and tasks from your phone. Miblo is complete without it.

[Phone app](https://miblo.ai/en/docs#phone)

[About Miblo+](https://miblo.ai/en/plus)

### Command line

One line in a terminal installs Miblo, with or without Claude Code, connects your other AI tools and pairs your Miblo. It works on macOS, Linux and Windows, WSL included (run the Linux line inside it).

macOS or Linux (Terminal):

```
curl -fsSL https://miblo.ai/dl/install.sh | sh
```

Windows (PowerShell):

```
irm https://miblo.ai/dl/install.ps1 | iex
```

On a Mac, without typing anything: download Install-Miblo-macOS.zip, unzip it and double-click Install Miblo.command. If macOS says it can't be opened, go to System Settings › Privacy & Security and click Open Anyway.

[Download Install-Miblo-macOS.zip](https://miblo.ai/dl/Install-Miblo-macOS.zip)

#### What the installer does

- Installs Miblo, with or without Claude Code. Without it, it downloads Miblo from miblo.ai and checks the signed release before anything downloaded runs; Miblo then keeps itself up to date.
- With Claude Code: finds Claude Code, adds the Miblo marketplace, installs the plugin and turns on its auto-update. The plugin and the miblo command share the same pairings.
- Other AI tools: if it finds Codex, Copilot CLI, Gemini CLI, OpenCode or Cursor, it asks one by one whether to show their sessions on Miblo.
- Pairing (optional): asks whether you have a Miblo on your desk (Return pairs it now, l leaves it for later). If you do, it gets Node.js ready (downloading it once if needed) and opens the wizard, with the list of Miblos on your network; if none answers, it says the gadget is optional and finishes.
- Limits: with Claude Code, asks whether to link the status line to show your usage limits. Your status line stays the same.
- Speaks Portuguese when your system does, English otherwise (MIBLO_LANG=pt or MIBLO_LANG=en picks one), never asks for an administrator password and can run again any time: it updates what is already there.

#### Where it goes

| System | Miblo's folder and the miblo command |
| --- | --- |
| macOS | ~/.miblo; the command is ~/.local/bin/miblo |
| Linux | ~/.local/share/miblo ($XDG_DATA_HOME/miblo); the command is ~/.local/bin/miblo |
| Windows | %LOCALAPPDATA%\Miblo; its bin folder (with miblo.cmd) is added to your user Path |

A new terminal says miblo is not found? On macOS and Linux, ~/.local/bin is not on your PATH yet: the installer prints the line to add to your shell's profile (export PATH="$HOME/.local/bin:$PATH"). On Windows, open a new terminal: windows already open keep the old Path.

#### Install without pairing now

macOS or Linux:

```
curl -fsSL https://miblo.ai/dl/install.sh | sh -s -- --no-pair
```

Windows (PowerShell): run it before the install line:

```
$env:MIBLO_NO_PAIR = '1'
```

Then pair with miblo pair --wizard in a terminal (or /miblo:pair in Claude Code).

#### Main commands

- `miblo pair --wizard`: Lists the Miblos on your network, asks the one you pick to show its code and pairs. It also offers a name and the settings page.
- `miblo pair <ip> <code>`: Pairs straight with the Miblo at that IP, using the 4-digit code on its screen.
- `miblo status`: The bridge, the status line, each paired Miblo, the active sessions, the limits and today's summary.
- `miblo setup [codex | copilot | gemini | opencode | cursor] [--remove]`: Connects another AI tool. On its own, lists what is found and connected.
- `miblo update [id] | rollback`: Updates Miblo, then the paired Miblos' firmware (with the code on the screen), or goes back to the previous version.
- `miblo phone on | off | list | pending | approve <id> | deny <id> | revoke <id>`: The optional phone app. Needs this computer linked to your account (miblo account link).
- `miblo plus status | link | approvals on | replies on | …`: Miblo+ on this computer, if you subscribe.
- `miblo server set <https://your-server> | reset`: Uses your own phone server, or goes back to miblo.ai.
- `miblo uninstall [--purge]`: Removes Miblo from this computer, keeping your pairings; --purge deletes Miblo's data too.
- `miblo help`: Lists every command. The same as in Commands, with miblo in place of /miblo:.

#### After that

1. Pair your Miblo (if you have one): the installer asks and opens the wizard. Left it for later? Run miblo pair --wizard.
2. Phone app (optional): your sessions, alerts and limits on your phone, end-to-end encrypted. It needs a Miblo account; see Phone app, further down.
3. Miblo+ (optional): a subscription that adds conversations, replies, approvals and tasks from your phone. Miblo is complete without it.

[Phone app](https://miblo.ai/en/docs#phone)

[About Miblo+](https://miblo.ai/en/plus)

### Plugin

Miblo joins each AI tool its own way: in Claude Code as a plugin; in the others through hooks Miblo writes into their settings (miblo setup), leaving the rest alone. Pick yours:

#### Claude Code

Needs Claude Code 2.1.224 or newer. It covers the terminal (claude), the Claude desktop app's Code tab and the VS Code, Cursor and JetBrains extensions: they all share the same plugins.

1. In Claude Code, add the Miblo marketplace and install the plugin (the three commands below).
2. Run /miblo:pair. It finds Miblo on the network, asks for the 4-digit code on its screen and pairs; then it asks for Miblo's name.
3. To see the 5-hour and weekly limits, agree to link the status line (or run /miblo:link-statusline). Your status line stays exactly the same.

In Claude Code:

```
/plugin marketplace add https://miblo.ai/dl/marketplace.json
```

```
/plugin install miblo@miblo
```

```
/reload-plugins
```

Or in a terminal:

```
claude plugin marketplace add https://miblo.ai/dl/marketplace.json
```

```
claude plugin install miblo@miblo
```

- In the Claude desktop app: Code tab, + › Plugins; add the marketplace above and install miblo.
- Updates: /miblo:update updates the plugin, then each Miblo's firmware.
- The plugin alone doesn't put the miblo command in your terminal. Want both? Use the Command line tab: the installer finds Claude Code and shares the same plugin and pairings.
- Before uninstalling the plugin, run /miblo:unlink-statusline.

#### Codex

1. Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
2. Connect Codex: run miblo setup codex in a terminal (or /miblo:setup codex in Claude Code).
3. Open Codex, run /hooks and trust the Miblo hooks. Codex only runs a new hook after that.
4. Sessions show on Miblo from your next activity.

```
miblo setup codex
```

- What changes: Miblo's hooks go into ~/.codex/hooks.json (or $CODEX_HOME), next to yours; the original is saved once as hooks.json.miblo-backup.
- No trusting again: the hooks run a fixed copy of Miblo's launcher in ~/.codex/miblo/, so updates never change them.
- What shows: working, needs you (approvals) and finished.
- Limits: the 5-hour and weekly ones come from Codex's own session files (~/.codex/sessions), after its first response, when you're signed in with a ChatGPT plan. An API key has no such limits.
- Undo: miblo setup codex --remove takes out only Miblo's hooks.

#### GitHub Copilot CLI

1. Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
2. Connect Copilot CLI: run miblo setup copilot in a terminal (or /miblo:setup copilot in Claude Code).
3. 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.

#### Gemini CLI

1. Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
2. Connect Gemini CLI: run miblo setup gemini in a terminal (or /miblo:setup gemini in Claude Code).
3. 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.

#### OpenCode

1. Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
2. Connect OpenCode: run miblo setup opencode in a terminal (or /miblo:setup opencode in Claude Code).
3. 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.

#### Cursor

This is Cursor's own agent. The Claude Code extension inside Cursor uses the Claude Code plugin (Claude Code tab).

1. Have Miblo installed: from the Command line tab, the app or the Claude Code plugin.
2. Connect Cursor: run miblo setup cursor in a terminal (or /miblo:setup cursor in Claude Code).
3. 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.

#### Not supported

- Cloud sessions: claude.ai/code and the cloud sessions started from the Claude desktop or mobile app. They run away from your computer and can't reach the Miblo on your network.
- GitHub Copilot's Claude agent: it doesn't run plugin hooks.
- Any tool not in the tabs above is not supported yet.

#### With every tool

- Never in the way: every hook gives up within 3 seconds and always lets the AI carry on.
- Privacy: nothing more leaves your computer than the session's folder name, its state and the tool in use. No prompts, replies, files or diffs.
- Usage limits come only from Claude Code and Codex; the other tools don't report them.

#### After that

1. Pair your Miblo (if you have one): /miblo:pair in Claude Code, or miblo pair --wizard in a terminal.
2. Phone app (optional): your sessions, alerts and limits on your phone, end-to-end encrypted. It needs a Miblo account; see Phone app, further down.
3. Miblo+ (optional): a subscription that adds conversations, replies, approvals and tasks from your phone. Miblo is complete without it.

[Phone app](https://miblo.ai/en/docs#phone)

[About Miblo+](https://miblo.ai/en/plus)

## Getting started

Source: https://miblo.ai/en/docs#getting-started

Miblo shows the sessions of the AI coding tools on your computer: Claude Code (terminal, the desktop app's Code tab, the VS Code, Cursor and JetBrains extensions), Codex, GitHub Copilot CLI, Gemini CLI, OpenCode and Cursor's own agent. It runs on macOS, Windows and Linux, WSL included, and does not depend on Claude Code: the Miblo app finds the tools you have.

1. Plug Miblo into a 5 V / 1 A USB supply. The screen shows a QR code and the network name Miblo-Setup-XXXX.
2. Scan the QR code with your phone (or join that network). The setup page opens by itself.
3. Pick your Wi-Fi network and type the password. It must be 2.4 GHz with WPA2, and the same network as your computer.
4. Once connected, the screen shows “Wi-Fi connected”, a 4-digit code and Miblo's IP.
5. On your computer, download and open the Miblo app (below). It finds your AI tools, installs Miblo, turns on automatic updates and pairs. Rather not use the app? Use the command line or the plugin (Install section).

Download the Miblo app: https://miblo.ai/en/downloads

- macOS or Linux (Terminal): `curl -fsSL https://miblo.ai/dl/install.sh | sh`

- Windows (PowerShell): `irm https://miblo.ai/dl/install.ps1 | iex`

When the app says Miblo is paired, open your AI tool. If it was already open, restart it. Sessions start showing with your next activity.

Miblo needs Node.js 20 or newer, and you don't have to install anything: it uses the Node you already have or downloads the official release once, checked against a SHA-256.

## Pairing

Source: https://miblo.ai/en/docs#pairing

Pairing links a computer to a Miblo. The app does it for you: it shows the Miblos on your network, like a Wi-Fi list, asks the one you pick to show its code and you type the 4 digits on its screen.

- Just connected: name, IP and code
- The pairing code, when the app asks

- To pair again or pair another Miblo: in the app (My Miblos › Pair another Miblo), with miblo pair in a terminal or /miblo:pair in Claude Code. If the search doesn't find Miblo, use the IP shown on its screen, just under its name: miblo pair 192.168.0.57.
- /miblo:pair also asks what to call Miblo (up to 20 characters) and whether it may know your first name and birthday, to say good morning.
- To see your usage limits, allow the status line link (in Claude Code: run /miblo:link-statusline). Your status line stays exactly the same, and /miblo:unlink-statusline undoes it.
- One Miblo takes up to 4 computers, and one computer can pair with several Miblos.
- Five wrong codes in a row lock pairing for 60 seconds, and the wait doubles with each new run of mistakes.

The settings page opens at http://miblo.local from any phone or computer on the same network, or with /miblo:settings. Changing a setting asks for the code shown on the screen, proof that you are the one in front of it.

## Commands

Source: https://miblo.ai/en/docs#commands

Commands run in a terminal as miblo <command> (for example miblo focus) and in Claude Code as /miblo:<command>; the list below uses the Claude Code form. Many are also in the Miblo app (Shortcuts). With a single Miblo paired, the id is optional; miblo status shows the ids. The daily-life commands go to every paired Miblo; add --id <id> to send one to a single Miblo.

- `/miblo:pair [ip]`: Finds Miblo on the network, asks for the code on its screen and pairs. Then asks for a name and offers to link the status line.
- `/miblo:status`: Shows the bridge, the status line, each paired Miblo, the active sessions, the limits and today's summary.
- `/miblo:mode overview | limits | sessions`: Sets the display mode.
- `/miblo:rotate on | off`: In the Overview, switches to the Limits screen every so often.
- `/miblo:focus [focus [break [rounds]]] | stop`: Starts a focus session (Pomodoro): 25 minutes of focus and 5 of break, 4 rounds by default.
- `/miblo:meeting [minutes] | off`: Meeting mode: no project, command or tool names on the screen.
- `/miblo:say <text> | off`: A note for people passing by your desk, for 30 minutes or as long as you choose.
- `/miblo:remind <minutes | HH:MM> <text>`: Reminders and alarms every day or on weekdays.
- `/miblo:timer <minutes> | stop`: A big countdown on the screen.
- `/miblo:countdown <label> <DD/MM> | off`: Counts the days to a date, on the desk screen and the pet's sign.
- `/miblo:limits`: The 5-hour and weekly limits, when they reset and when they would run out.
- `/miblo:today`: Today's summary in the terminal: responses, time, cost and limits.
- `/miblo:blue [on | off] [HH:MM HH:MM] [strength%]`: Blue light filter, always or on a schedule, from 1% to 100%.
- `/miblo:night on | off [HH:MM HH:MM] [brightness%]`: Dims the screen between two times.
- `/miblo:find`: Makes Miblo blink and wave with its settings page QR code, to spot one among several.
- `/miblo:demo [minutes | stop]`: With two or more Miblos, puts them all in pet mode now so you can watch the visits.
- `/miblo:rename [id] [name]`: Names your Miblo (up to 20 characters).
- `/miblo:owner --name <name> --birthday <DD/MM>`: Tells Miblo your first name and birthday. Both stay on the device only.
- `/miblo:settings [id]`: Opens the settings page in your browser.
- `/miblo:update [id]`: Updates the plugin, then each Miblo's firmware, with the code on the screen.
- `/miblo:link-statusline`: Links Claude Code's status line to Miblo so your limits show up.
- `/miblo:unlink-statusline`: Restores your original status line. Run it before uninstalling the plugin.
- `/miblo:reset <id>`: Factory-resets Miblo: erases Wi-Fi, pairings and settings. Asks you to confirm.
- `/miblo:setup [codex | copilot | gemini | opencode | cursor] [--remove]`: Shows another AI tool's sessions on Miblo. With no arguments, lists the ones found and connected.
- `/miblo:phone [on | off | list]`: The optional phone app: turns it on (through your Miblo account), lists the phones, or turns it off and forgets the keys.

## Other AI tools

Source: https://miblo.ai/en/docs#other-ai-tools

Miblo (and the phone app) shows the sessions of every connected AI coding tool in one list. A small label before the detail says which AI a session comes from (“Codex · npm test”). Turn each one on or off in the Miblo app (AI tools) or with miblo setup <name>.

| Tool | How to connect and what shows |
| --- | --- |
| Codex | /miblo:setup codex; then, in Codex, run /hooks and trust the Miblo hooks. Working, needs you and finished, plus the 5-hour and weekly limits. |
| GitHub Copilot CLI | /miblo:setup copilot. Working, needs you and finished. |
| Gemini CLI | /miblo:setup gemini. Working, needs you and finished. |
| OpenCode | /miblo:setup opencode; then restart OpenCode. Working, needs you and finished. |
| Cursor (its own agent) | /miblo:setup cursor; then restart Cursor. Working and finished: Cursor doesn't report when it waits for approval. |

- The Miblo app asks, for each AI tool it finds on your computer, whether its sessions show on Miblo. Later, change it in the app (AI tools); in a terminal, miblo setup on its own lists what is found and connected.
- /miblo:setup <name> --remove takes out only Miblo's hooks; your own settings stay as they are.
- Usage limits come from Claude Code and Codex; the other tools don't report limits.
- Nothing more leaves your computer: only the session's folder name, its state and the tool in use. No prompts, replies or files.

Codex, GitHub Copilot, Gemini, OpenCode and Cursor are trademarks of their owners. Miblo is not affiliated with them.

## Status SDK

Source: https://miblo.ai/en/docs#sdk

Your own programs can show up on Miblo too: a build script, a data job, an AI tool Miblo does not connect. Each one becomes a session on the gadget and the phone (working, needs you, idle or done) and can put a short message on the screen, start a focus session or a timer.

Status only: the SDK cannot approve, reply or start tasks, and nothing in it turns them on. It needs a Miblo that has the miblo sdk command (check with miblo sdk status).

In your own terminal: turn the API on and hand its token to your program:

```
export MIBLO_TOKEN=$(miblo sdk token)
```

### Node.js

Install (@miblo/status 1.0.0, Node 20+, no dependencies):

```
npm install https://miblo.ai/dl/sdk/miblo-status-1.0.0.tgz
```

Example: a session that needs you:

```
// MIBLO_TOKEN=$(miblo sdk token) node needs-you.mjs
import { MibloStatus } from '@miblo/status';
import { createInterface } from 'node:readline/promises';

const miblo = new MibloStatus();
const job = await miblo.session({ tool: 'deploy.mjs', title: 'Deploy', detail: 'building' });
await new Promise((r) => setTimeout(r, 3000));  // ...your work...
await job.needsYou('confirm the deploy');
await createInterface({ input: process.stdin, output: process.stdout }).question('Deploy? [enter] ');
await job.done('deployed');
process.exit(0);
```

### Python

Install (miblo-status 1.0.0, Python 3.9+, standard library only):

```
pip install https://miblo.ai/dl/sdk/miblo_status-1.0.0-py3-none-any.whl
```

Example: a session that needs you:

```
# MIBLO_TOKEN=$(miblo sdk token) python3 needs_you.py
import time
from miblo_status import MibloStatus

miblo = MibloStatus()
job = miblo.session("deploy.py", title="Deploy", detail="building")
time.sleep(3)  # ...your work...
job.needs_you("confirm the deploy")
input("Deploy? [enter] ")
job.done("deployed")
```

### The contract (Status API v1)

- Its own token: miblo sdk token makes a status-only token (never the bridge key) and turns the API on; without it, everything is refused. miblo sdk token --rotate replaces it and miblo sdk off turns the API off.
- This computer only: the Miblo bridge on 127.0.0.1:47821, with an HMAC-SHA256 challenge and response on every request and every answer. Browsers and other computers are kept out.
- Sessions: tool (your program's name, up to 20 characters), title and detail (up to 64) and the state working, needs_you, idle or done. needs_you and done alert on the gadget once per change. Up to 8 sessions at a time; a session ends when its process exits.
- Gadget actions: a message of up to 40 characters (1 to 480 minutes), a focus session or a timer, like miblo say, miblo focus and miblo timer. With no Miblo paired, delivered is 0, not an error.
- Reading: a status-only snapshot (names, states and gadgets), with no commands, prompts, files, costs or anything of Miblo+.
- Limits: 10 session changes a second, 3 actions in a row and then 1 every 10 s, bodies of up to 4096 bytes. Errors have stable codes (sdk_off, not_authorised, unknown_session, rate_limited...).
- v1 never breaks: fields are only ever added. The packages follow semver and 1.x speaks v1.

### Check the download

The packages come only from miblo.ai (they are not on npm or PyPI). Each file has its Ed25519 signature next to it (the same name with .sig), made with the key of Miblo's updates, and the signed SHA256SUMS lists every version.

Download and check the hash:

```
curl -fLO https://miblo.ai/dl/sdk/miblo-status-1.0.0.tgz
curl -fsSL https://miblo.ai/dl/sdk/SHA256SUMS | shasum -a 256 -c --ignore-missing
```

[SHA256SUMS](https://miblo.ai/dl/sdk/SHA256SUMS)

## Phone app

Source: https://miblo.ai/en/docs#phone

Optional and off by default: your phone shows what Miblo's screen shows (sessions, alerts, limits and today's summary) and can notify you when a session needs you, even away from your desk. The app is a page at miblo.ai/app that you add to your home screen.

1. In the Miblo app on your computer, tap Sign in with your Miblo account and turn Phone on.
2. On your phone, open miblo.ai/app, sign in to the same account (with its second step) and create the app PIN. The computer shows a 6-digit code (in the Miblo app, a notification or miblo phone pending): type that code on the phone and confirm with its passkey. If it is not your phone, tap Deny on the computer.
3. Add the page to your home screen (on iPhone: Share, Add to Home Screen) and allow notifications.
4. The phone starts showing your sessions with the next activity of any connected AI tool.

### Your own server (optional)

The phone server and the phone app are open source (AGPL-3.0), distributed from miblo.ai and signed like Miblo's updates. Run your own and your phone and computer talk only through it, never through miblo.ai. It is free, for anyone able to host it.

- You need a host with HTTPS: Docker with Caddy, or Cloudflare Workers. The steps and commands are in the server guide.
- You need Miblo 1.22.0 or newer on the computer.

[Download and run the server](https://miblo.ai/en/docs/self-hosting)

On the computer: point it to your server and type the code shown on the Miblo:

```
miblo server set https://your-server
```

To return to miblo.ai:

```
miblo server reset
```

### From a terminal

Link the computer to the account and turn the phone on:

```
miblo account link
miblo phone on
```

[Remote control from your phone: approve, reply and check your limits](https://miblo.ai/en/remote-control)

- End-to-end encrypted (AES-256-GCM): the key is made on your computer and reaches each phone locked to that phone's own key. miblo.ai stores and relays only ciphertext.
- Notifications only say that a session needs you, never which one or what.
- The server keeps just the last encrypted frame, for 10 minutes, with no IP address.
- Every new phone of the account shows on your Miblo and in a notification on the computer. Remove one in My account, Devices, or with miblo phone revoke.
- The app asks for a PIN of your own (6 digits or more), created right after you sign in: when it opens and after a while unused (1 minute to 1 hour, or whenever you leave the app, in Settings). The PIN stays on the phone. 5 wrong PINs in a row pause the tries for 1 minute; 10 block the app on that phone, end the account's session there and send a notice to your email: to get back in, sign in to the account again and create another PIN.
- The account decides which phones may join this computer, so linking or unlinking it (miblo account link / unlink) runs only in your own terminal or the app, never through an AI agent; the site asks your second factor again and the account gets an e-mail for every computer linked or unlinked. With a Miblo paired, it also asks for the 4-digit code on its screen.
- /miblo:phone off deletes the room on miblo.ai and makes your computer forget the keys. While it's off, the plugin doesn't connect to miblo.ai.

## Troubleshooting

Source: https://miblo.ai/en/docs#troubleshooting

| What happens | What to do |
| --- | --- |
| The app or miblo pair finds no Miblo | Check that the screen shows a pairing code and that Miblo is on the same network as your computer. VPNs, WSL2 and corporate networks often block the search: type the IP shown on the screen when the installer asks, or run /miblo:pair <ip>. |
| The screen says “Wrong password” | Scan the QR code again and retype the password. |
| The screen says “Network not found” | Miblo only sees 2.4 GHz networks. Turn on the router's 2.4 GHz band or give it a separate network name, and move closer to the router. |
| The screen says “Connection refused” | Check the password. If the router uses WPA3 or WPA2/WPA3 mixed mode, switch it to WPA2. |
| No limits on the screen | Run /miblo:status to see whether the status line is linked; if not, run /miblo:link-statusline. Limits show after the next response and exist only on the Pro and Max plans. |
| Miblo says “Disconnected” | It hasn't received anything for 30 seconds. The bridge comes back with the next activity of any connected AI tool; check in the app or with miblo status. |
| A Miblo shows as unauthorized | It was reset or paired with something else. Run /miblo:pair again. |
| Nothing arrives from the desktop app or an IDE | Run /miblo:update there: it checks Node.js first and says what is missing. |
| Blank status line after uninstalling | Reinstall the plugin, run /miblo:unlink-statusline and uninstall again. Next time, unlink first. |

To factory-reset without a computer, power Miblo on 6 times in quick succession. An on-screen countdown lets you cancel.

## Orders, delivery and returns

Source: https://miblo.ai/en/docs#orders

- Your order is confirmed once the payment is approved. A Pix QR code lasts 30 minutes and a boleto is due in 3 days.
- The delivery time shows at checkout and counts business days from the payment confirmation. We email the tracking code when the order ships.
- To follow it, open My order with the order code and the email you bought with, or sign in and see My orders.
- Changed your mind? You can withdraw within 7 calendar days of receiving it, no reason needed. The return costs you nothing and the money goes back the way you paid.
- 90-day warranty against defects, from delivery: we repair, replace or refund.

[Track my order](https://miblo.ai/en/order)

Late, damaged or want to return it? Write to contato@miblo.ai with the order code.

## Your account

Source: https://miblo.ai/en/docs#account

One account, with your email, brings together your orders, Miblo+, the pets you make in Studio and your part in the community. You don't need an account to use Miblo on your desk.

- To sign in, type your email: we send a code. If it's your first time, the account is created right then.
- Under Security, turn on signing in with your fingerprint or face (passkey). It's faster and safer than the email code.

[Open my account](https://miblo.ai/en/account)

## Miblo+

Source: https://miblo.ai/en/docs#miblo-plus

Miblo+ is an optional subscription: Miblo is complete without it. See what it includes and the prices on the Miblo+ page. To see your plan, your payments or cancel, go to My account › Miblo+.

[About Miblo+](https://miblo.ai/en/plus)

## Studio: make your own pet

Source: https://miblo.ai/en/docs#studio

In Studio you make a pet of your own: start from one of the 20 pets, change its parts and colours and save it. You get a code to install it on your Miblo, and your pets stay in My account › My pets.

[Open Studio](https://miblo.ai/en/community/studio)

# Fatos (Português)

### O que é o Miblo?

Um cubinho de mesa que mostra as sessões das suas ferramentas de IA, avisa quando uma precisa de você e mantém seus limites de uso à vista.

O Miblo mostra as sessões das ferramentas de IA para programar no seu computador: Claude Code (terminal, aba Code do app desktop, extensões de VS Code, Cursor e JetBrains), Codex, GitHub Copilot CLI, Gemini CLI, OpenCode e o agente do Cursor. Funciona no macOS, no Windows e no Linux, inclusive WSL, e não depende do Claude Code: o app Miblo acha as ferramentas que você tem.

### Com quais IAs de programação o Miblo funciona?

Claude Code, Codex, GitHub Copilot CLI, Gemini CLI, OpenCode e Cursor. As sessões de todas aparecem numa lista só.

- Claude Code: trabalhando, precisa de você, terminou, limites de uso.
- Codex: trabalhando, precisa de você, terminou, limites de uso.
- GitHub Copilot CLI: trabalhando, precisa de você, terminou.
- Gemini CLI: trabalhando, precisa de você, terminou.
- OpenCode: trabalhando, precisa de você, terminou.
- Cursor: trabalhando, terminou.
- Sem suporte (Sessões na nuvem) claude.ai/code e as sessões na nuvem abertas pelo app desktop ou de celular do Claude. Elas rodam longe do seu computador e não alcançam o Miblo na sua rede.
- Sem suporte (O agente Claude do GitHub Copilot) não roda os hooks de plugin.

- [Miblo para Claude Code](https://miblo.ai/ferramentas/claude-code)
- [Miblo para Codex](https://miblo.ai/ferramentas/codex)
- [Miblo para GitHub Copilot CLI](https://miblo.ai/ferramentas/copilot-cli)
- [Miblo para Gemini CLI](https://miblo.ai/ferramentas/gemini-cli)
- [Miblo para OpenCode](https://miblo.ai/ferramentas/opencode)
- [Miblo para Cursor](https://miblo.ai/ferramentas/cursor)

### Quanto custa o Miblo?

O app, o plugin do Claude Code e a linha de comando são grátis, com ou sem o aparelho.

O aparelho Miblo custa R$ 149,90 na loja do miblo.ai, com entrega para todo o Brasil.

O Miblo+, opcional, custa R$ 9,90 por mês ou R$ 99,00 por ano. O Miblo no celular, fora de casa. Veja as últimas mensagens da IA, responda e aprove permissões de qualquer lugar, em qualquer rede.

- [Comprar o Miblo](https://miblo.ai/comprar)
- [Miblo+](https://miblo.ai/plus)

### Dá para controlar o Claude Code e o Codex pelo celular?

Instale o app Miblo no computador e entre com a sua conta Miblo. No celular, abra miblo.ai/app, entre na mesma conta e digite o código de 6 dígitos que o computador mostra. O celular passa a mostrar as sessões e os limites e avisa quando uma sessão precisa de você. Com o Miblo+, você também aprova permissões, responde à IA e pede tarefas novas.

Sim, com o Miblo+, em todas as IAs que o Miblo mostra: Claude Code, Codex, GitHub Copilot CLI, Gemini CLI, OpenCode e Cursor. Se a sessão está trabalhando, a resposta entra quando ela termina a vez; se está parada, ela acorda e responde (Claude Code, Codex e OpenCode). Cada resposta pede a passkey do celular.

Sim, e é grátis: o celular recebe uma notificação quando uma sessão precisa de você, mesmo longe da mesa. A notificação diz só que uma sessão precisa de você, nunca qual nem o quê. No Cursor não há esse aviso, porque ele não informa quando espera aprovação.

- [Controle remoto](https://miblo.ai/controle-remoto)
- [Aprovar permissões do Claude Code pelo celular](https://miblo.ai/controle-remoto/aprovar-permissoes-claude-code)
- [Responder à sua IA pelo celular](https://miblo.ai/controle-remoto/responder-ia-pelo-celular)
- [Acompanhar os limites do Claude pelo celular](https://miblo.ai/controle-remoto/limites-do-claude-no-celular)

### Preciso do aparelho para usar o Miblo?

Também não precisa do aparelho: sem um Miblo na mesa, o app, o pet e o status das suas sessões (no celular também, com uma conta Miblo grátis) já funcionam, e o Miblo+ continua sendo a parte paga. O aparelho acrescenta uma tela e um pet na sua mesa, e as visitas entre Miblos. Os instaladores perguntam se você tem um; sem ele, terminam sem erro.

### Como instalar o Miblo?

Você não precisa do app: a linha de comando e o plugin fazem tudo. São três jeitos de instalar o mesmo Miblo no computador; escolha o que combina com você.

macOS ou Linux: curl -fsSL https://miblo.ai/dl/install.sh | sh

Windows (PowerShell): irm https://miblo.ai/dl/install.ps1 | iex

- Ligue o Miblo numa fonte USB de 5 V / 1 A. A tela mostra um QR code e o nome de rede Miblo-Setup-XXXX.
- Escaneie o QR code com o celular (ou entre nessa rede). A página de configuração abre sozinha.
- Escolha a sua rede Wi-Fi e digite a senha. Ela precisa ser de 2,4 GHz, com WPA2, e a mesma do seu computador.
- Quando conectar, a tela mostra “Wi-Fi conectado”, um código de 4 dígitos e o IP do Miblo.
- No computador, baixe e abra o app Miblo (abaixo). Ele acha as suas IAs, instala o Miblo, liga as atualizações automáticas e pareia. Prefere sem o app? Use a linha de comando ou o plugin (seção Instalar).

- [Baixar o app](https://miblo.ai/downloads)
- [Documentação](https://miblo.ai/docs)

### O Miblo é seguro? O que sai do meu computador?

Nunca atrapalha: cada hook desiste em 3 segundos e sempre deixa a IA seguir.

Privacidade: nada a mais sai do computador, só o nome da pasta da sessão, o estado e a ferramenta em uso. Nada de prompts, respostas, arquivos ou diffs.

- Criptografado de ponta a ponta (AES-256-GCM): a chave nasce no seu computador e chega a cada celular trancada para a chave daquele celular. O miblo.ai guarda e repassa só dados cifrados.
- As notificações dizem apenas que uma sessão precisa de você, nunca qual nem o quê.
- O servidor guarda só o último quadro cifrado, por 10 minutos, sem endereço IP.

### Quem faz o Miblo?

O Miblo é feito pela Devyzi (Devyzi Internet Soluções LTDA), no Brasil. Contato: contato@miblo.ai.

# Documentação (Português)

## Instalar

Source: https://miblo.ai/docs#instalar

Você não precisa do app: a linha de comando e o plugin fazem tudo. São três jeitos de instalar o mesmo Miblo no computador; escolha o que combina com você.

Também não precisa do aparelho: sem um Miblo na mesa, o app, o pet e o status das suas sessões (no celular também, com uma conta Miblo grátis) já funcionam, e o Miblo+ continua sendo a parte paga. O aparelho acrescenta uma tela e um pet na sua mesa, e as visitas entre Miblos. Os instaladores perguntam se você tem um; sem ele, terminam sem erro.

[Já tem um GeekMagic SmallTV Ultra? Instale o Miblo nele](https://miblo.ai/traga-seu-aparelho)

### App

O app Miblo é o caminho sem terminal: os mesmos passos dos instaladores de linha de comando, numa janela. Ele acha as suas ferramentas de IA (Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode e Cursor), instala o Miblo, conecta as que você marcar e pareia o seu Miblo. Nunca pede senha de administrador.

Baixe o app Miblo: https://miblo.ai/downloads

- macOS ou Linux (Terminal): `curl -fsSL https://miblo.ai/dl/install.sh | sh`

- Windows (PowerShell): `irm https://miblo.ai/dl/install.ps1 | iex`

#### O que fica no app

- Barra de menus ou bandeja: um ícone com as sessões, os limites de 5 horas e da semana e o resumo do dia.
- Meus Miblos: a página de ajustes, renomear, piscar, remover e parear outro Miblo.
- Ferramentas de IA: uma chave para cada ferramenta, o Claude Code inclusive.
- E mais: Celular, Atualizações (do Miblo e do firmware, com o código da tela) e Atalhos (reunião, foco, timer, recado, piscar).

É uma comodidade, nunca uma exigência: tudo o que o app faz também se faz pela linha de comando ou pelo plugin, e os três podem conviver no mesmo computador.

#### Depois disso

1. Parear o Miblo (se você tiver um): no fim da instalação o app pergunta se há um Miblo na mesa, Parear agora ou Depois. Para parear depois, abra Meus Miblos › Adicionar um Miblo.
2. App de celular (opcional): as sessões, os avisos e os limites no celular, com criptografia de ponta a ponta. Precisa de uma conta Miblo; veja App de celular, mais abaixo.
3. Miblo+ (opcional): uma assinatura que acrescenta as conversas, as respostas, as aprovações e as tarefas pelo celular. O Miblo funciona completo sem ele.

[App de celular](https://miblo.ai/docs#celular)

[Conhecer o Miblo+](https://miblo.ai/plus)

### Linha de comando

Uma linha no terminal instala o Miblo, com ou sem Claude Code, conecta as suas outras IAs e pareia o Miblo. Funciona no macOS, no Linux e no Windows, inclusive WSL (rode a linha do Linux dentro dele).

macOS ou Linux (Terminal):

```
curl -fsSL https://miblo.ai/dl/install.sh | sh
```

Windows (PowerShell):

```
irm https://miblo.ai/dl/install.ps1 | iex
```

No Mac, sem digitar nada: baixe o Install-Miblo-macOS.zip, descompacte e dê dois cliques em Install Miblo.command. Se o macOS disser que não pode abrir, vá em Ajustes do Sistema › Privacidade e Segurança e clique em Abrir Mesmo Assim.

[Baixar Install-Miblo-macOS.zip](https://miblo.ai/dl/Install-Miblo-macOS.zip)

#### O que o instalador faz

- Instala o Miblo, com ou sem Claude Code. Sem ele, baixa o Miblo do miblo.ai e confere a assinatura da release antes de rodar qualquer coisa baixada; depois o Miblo se atualiza sozinho.
- Com o Claude Code: acha o Claude Code, adiciona o marketplace do Miblo, instala o plugin e liga a atualização automática dele. O plugin e o comando miblo usam os mesmos pareamentos.
- Outras IAs: se achar Codex, Copilot CLI, Gemini CLI, OpenCode ou Cursor, pergunta uma por uma se as sessões delas aparecem no Miblo.
- Pareamento (opcional): pergunta se você tem um Miblo na mesa (Enter pareia agora, d deixa para depois). Se tiver, prepara o Node.js (baixa uma vez, se precisar) e abre o assistente, com a lista dos Miblos da rede; se nenhum responder, diz que o aparelho é opcional e termina.
- Limites: com o Claude Code, pergunta se liga a status line para mostrar os limites de uso. A sua status line continua igual.
- Fala português quando o sistema está em português (MIBLO_LANG=pt ou MIBLO_LANG=en escolhe), nunca pede senha de administrador e pode rodar de novo quando quiser: atualiza o que já existe.

#### Onde fica

| Sistema | Pasta do Miblo e comando miblo |
| --- | --- |
| macOS | ~/.miblo; o comando fica em ~/.local/bin/miblo |
| Linux | ~/.local/share/miblo ($XDG_DATA_HOME/miblo); o comando fica em ~/.local/bin/miblo |
| Windows | %LOCALAPPDATA%\Miblo; a pasta bin dele (com miblo.cmd) entra no Path do seu usuário |

Um terminal novo diz que miblo não existe? No macOS e no Linux, ~/.local/bin ainda não está no PATH: o instalador mostra a linha para pôr no perfil do shell (export PATH="$HOME/.local/bin:$PATH"). No Windows, abra um terminal novo: os que já estavam abertos guardam o Path antigo.

#### Instalar sem parear agora

macOS ou Linux:

```
curl -fsSL https://miblo.ai/dl/install.sh | sh -s -- --no-pair
```

Windows (PowerShell): rode antes da linha de instalação:

```
$env:MIBLO_NO_PAIR = '1'
```

Depois, pareie com miblo pair --wizard num terminal (ou /miblo:pair no Claude Code).

#### Comandos principais

- `miblo pair --wizard`: Lista os Miblos da rede, pede para o escolhido mostrar o código e pareia. Também oferece dar um nome e abrir a página de ajustes.
- `miblo pair <ip> <código>`: Pareia direto com o Miblo nesse IP, com o código de 4 dígitos da tela.
- `miblo status`: O bridge, a status line, cada Miblo pareado, as sessões ativas, os limites e o resumo do dia.
- `miblo setup [codex | copilot | gemini | opencode | cursor] [--remove]`: Conecta outra IA. Sozinho, lista o que foi achado e conectado.
- `miblo update [id] | rollback`: Atualiza o Miblo e depois o firmware dos Miblos pareados (com o código da tela), ou volta para a versão anterior.
- `miblo phone on | off | list | pending | approve <id> | deny <id> | revoke <id>`: O app de celular, opcional. Precisa do computador ligado à sua conta (miblo account link).
- `miblo plus status | link | approvals on | replies on | …`: O Miblo+ neste computador, se você assinar.
- `miblo server set <https://seu-servidor> | reset`: Usa o seu próprio servidor do celular, ou volta para o miblo.ai.
- `miblo uninstall [--purge]`: Tira o Miblo do computador, mantendo os pareamentos; --purge apaga os dados do Miblo também.
- `miblo help`: Lista todos os comandos. Os mesmos da seção Comandos, com miblo no lugar de /miblo:.

#### Depois disso

1. Parear o Miblo (se você tiver um): o instalador pergunta e abre o assistente. Se deixou para depois, rode miblo pair --wizard.
2. App de celular (opcional): as sessões, os avisos e os limites no celular, com criptografia de ponta a ponta. Precisa de uma conta Miblo; veja App de celular, mais abaixo.
3. Miblo+ (opcional): uma assinatura que acrescenta as conversas, as respostas, as aprovações e as tarefas pelo celular. O Miblo funciona completo sem ele.

[App de celular](https://miblo.ai/docs#celular)

[Conhecer o Miblo+](https://miblo.ai/plus)

### Plugin

O Miblo entra em cada ferramenta de IA do jeito dela: no Claude Code, como plugin; nas outras, com hooks que o Miblo escreve na configuração delas (miblo setup), sem mexer no resto. Escolha a sua:

#### Claude Code

Precisa do Claude Code 2.1.224 ou mais novo. Vale para o terminal (claude), a aba Code do app desktop do Claude e as extensões de VS Code, Cursor e JetBrains: todos usam os mesmos plugins.

1. No Claude Code, adicione o marketplace do Miblo e instale o plugin (os três comandos abaixo).
2. Rode /miblo:pair. Ele acha o Miblo na rede, pede o código de 4 dígitos da tela e pareia; depois pergunta o nome do Miblo.
3. Para ver os limites de 5 horas e da semana, aceite ligar a status line (ou rode /miblo:link-statusline). A sua status line continua exatamente igual.

No Claude Code:

```
/plugin marketplace add https://miblo.ai/dl/marketplace.json
```

```
/plugin install miblo@miblo
```

```
/reload-plugins
```

Ou num terminal:

```
claude plugin marketplace add https://miblo.ai/dl/marketplace.json
```

```
claude plugin install miblo@miblo
```

- No app desktop do Claude: aba Code, + › Plugins; adicione o marketplace acima e instale miblo.
- Atualizar: /miblo:update atualiza o plugin e depois o firmware de cada Miblo.
- Só o plugin não põe o comando miblo no terminal. Quer os dois? Use a aba Linha de comando: o instalador acha o Claude Code e usa o mesmo plugin e os mesmos pareamentos.
- Antes de desinstalar o plugin, rode /miblo:unlink-statusline.

#### Codex

1. Tenha o Miblo instalado: pela aba Linha de comando, pelo app ou pelo plugin do Claude Code.
2. Conecte o Codex: rode miblo setup codex num terminal (ou /miblo:setup codex no Claude Code).
3. Abra o Codex, rode /hooks e confie nos hooks do Miblo. O Codex só roda um hook novo depois disso.
4. As sessões aparecem no Miblo a partir da próxima atividade.

```
miblo setup codex
```

- O que muda: os hooks do Miblo entram em ~/.codex/hooks.json (ou $CODEX_HOME), junto dos seus; o original é salvo uma vez como hooks.json.miblo-backup.
- Sem pedir confiança de novo: os hooks rodam uma cópia fixa do Miblo em ~/.codex/miblo/, então as atualizações não mudam nada.
- O que aparece: trabalhando, precisa de você (aprovações) e terminou.
- Limites: os de 5 horas e da semana vêm dos arquivos de sessão do próprio Codex (~/.codex/sessions), depois da primeira resposta, entrando com um plano do ChatGPT. Com chave de API não há esses limites.
- Desfazer: miblo setup codex --remove tira só os hooks do Miblo.

#### GitHub Copilot CLI

1. Tenha o Miblo instalado: pela aba Linha de comando, pelo app ou pelo plugin do Claude Code.
2. Conecte o Copilot CLI: rode miblo setup copilot num terminal (ou /miblo:setup copilot no Claude Code).
3. As sessões aparecem no Miblo a partir da próxima atividade.

```
miblo setup copilot
```

- O que muda: um arquivo de hooks só do Miblo, ~/.copilot/hooks/miblo.json (ou $COPILOT_HOME/hooks/), que o Copilot carrega junto dos seus.
- Não instale também o plugin do Claude Code no Copilot: cada sessão apareceria duas vezes.
- O que aparece: trabalhando, precisa de você (permissões e perguntas) e terminou. O Copilot não informa limites de uso.
- No Windows, os hooks rodam pelo sh do Git for Windows.
- Desfazer: miblo setup copilot --remove.

#### Gemini CLI

1. Tenha o Miblo instalado: pela aba Linha de comando, pelo app ou pelo plugin do Claude Code.
2. Conecte o Gemini CLI: rode miblo setup gemini num terminal (ou /miblo:setup gemini no Claude Code).
3. As sessões aparecem no Miblo a partir da próxima atividade.

```
miblo setup gemini
```

- O que muda: os hooks do Miblo entram em hooks no ~/.gemini/settings.json (ou $GEMINI_CLI_HOME/.gemini/), mantendo todo o resto, comentários inclusive. Antes de cada mudança o arquivo é copiado para settings.json.miblo-backup-<hora> (ficam as 3 mais novas).
- Comentários dentro de hooks fazem o setup parar e dizer o que fazer.
- Com a confiança de pastas do Gemini ligada, os hooks só rodam em pastas confiáveis.
- O que aparece: trabalhando, precisa de você (confirmações) e terminou. O Gemini não informa limites de uso.
- Desfazer: miblo setup gemini --remove.

#### OpenCode

1. Tenha o Miblo instalado: pela aba Linha de comando, pelo app ou pelo plugin do Claude Code.
2. Conecte o OpenCode: rode miblo setup opencode num terminal (ou /miblo:setup opencode no Claude Code).
3. Reinicie o OpenCode, que carrega os plugins ao abrir.

```
miblo setup opencode
```

- O que muda: um arquivo pequeno, ~/.config/opencode/plugins/miblo.js (em $XDG_CONFIG_HOME, quando definido). O opencode.json não é tocado; um miblo.js diferente que já estivesse lá é salvo antes em ~/.config/opencode/miblo-backup/.
- Ele só observa os eventos do OpenCode, nunca bloqueia nem muda nada.
- O que aparece: trabalhando, precisa de você (permissões e perguntas) e terminou; os tokens e o custo de cada sessão aparecem no miblo status. Sem limites de uso.
- Desfazer: miblo setup opencode --remove.

#### Cursor

Aqui é o agente do próprio Cursor. A extensão do Claude Code dentro do Cursor usa o plugin do Claude Code (aba Claude Code).

1. Tenha o Miblo instalado: pela aba Linha de comando, pelo app ou pelo plugin do Claude Code.
2. Conecte o Cursor: rode miblo setup cursor num terminal (ou /miblo:setup cursor no Claude Code).
3. Reinicie o Cursor.

```
miblo setup cursor
```

- O que muda: os hooks do Miblo entram em ~/.cursor/hooks.json, junto dos seus (o original é salvo uma vez como hooks.json.miblo-backup). São só hooks que não bloqueiam nada: as suas regras de aprovação continuam iguais.
- O que aparece: trabalhando e terminou. O Cursor não tem um aviso de “esperando aprovação” que não possa também bloquear comandos, por isso o Miblo nunca mostra “precisa de você” para o Cursor.
- No Cursor agent CLI (cursor-agent), a sessão aparece trabalhando enquanto as ferramentas rodam e terminada quando a execução acaba, ou cerca de 90 s depois da última atividade.
- Desfazer: miblo setup cursor --remove.

#### Sem suporte

- Sessões na nuvem: claude.ai/code e as sessões na nuvem abertas pelo app desktop ou de celular do Claude. Elas rodam longe do seu computador e não alcançam o Miblo na sua rede.
- O agente Claude do GitHub Copilot: não roda os hooks de plugin.
- Qualquer ferramenta fora das abas acima ainda não é suportada.

#### Em todas as ferramentas

- Nunca atrapalha: cada hook desiste em 3 segundos e sempre deixa a IA seguir.
- Privacidade: nada a mais sai do computador, só o nome da pasta da sessão, o estado e a ferramenta em uso. Nada de prompts, respostas, arquivos ou diffs.
- Os limites de uso vêm só do Claude Code e do Codex; as outras ferramentas não informam limites.

#### Depois disso

1. Parear o Miblo (se você tiver um): /miblo:pair no Claude Code, ou miblo pair --wizard num terminal.
2. App de celular (opcional): as sessões, os avisos e os limites no celular, com criptografia de ponta a ponta. Precisa de uma conta Miblo; veja App de celular, mais abaixo.
3. Miblo+ (opcional): uma assinatura que acrescenta as conversas, as respostas, as aprovações e as tarefas pelo celular. O Miblo funciona completo sem ele.

[App de celular](https://miblo.ai/docs#celular)

[Conhecer o Miblo+](https://miblo.ai/plus)

## Começando

Source: https://miblo.ai/docs#comecando

O Miblo mostra as sessões das ferramentas de IA para programar no seu computador: Claude Code (terminal, aba Code do app desktop, extensões de VS Code, Cursor e JetBrains), Codex, GitHub Copilot CLI, Gemini CLI, OpenCode e o agente do Cursor. Funciona no macOS, no Windows e no Linux, inclusive WSL, e não depende do Claude Code: o app Miblo acha as ferramentas que você tem.

1. Ligue o Miblo numa fonte USB de 5 V / 1 A. A tela mostra um QR code e o nome de rede Miblo-Setup-XXXX.
2. Escaneie o QR code com o celular (ou entre nessa rede). A página de configuração abre sozinha.
3. Escolha a sua rede Wi-Fi e digite a senha. Ela precisa ser de 2,4 GHz, com WPA2, e a mesma do seu computador.
4. Quando conectar, a tela mostra “Wi-Fi conectado”, um código de 4 dígitos e o IP do Miblo.
5. No computador, baixe e abra o app Miblo (abaixo). Ele acha as suas IAs, instala o Miblo, liga as atualizações automáticas e pareia. Prefere sem o app? Use a linha de comando ou o plugin (seção Instalar).

Baixe o app Miblo: https://miblo.ai/downloads

- macOS ou Linux (Terminal): `curl -fsSL https://miblo.ai/dl/install.sh | sh`

- Windows (PowerShell): `irm https://miblo.ai/dl/install.ps1 | iex`

Quando o app disser que o Miblo foi pareado, abra a sua ferramenta de IA. Se ela já estava aberta, reinicie. As sessões começam a aparecer na próxima atividade.

O Miblo precisa do Node.js 20 ou mais novo, e você não precisa instalar nada: ele usa o Node que você já tem ou baixa a versão oficial uma vez, conferida por SHA-256.

## Pareamento

Source: https://miblo.ai/docs#pareamento

Parear liga um computador a um Miblo. O app já faz isso: ele mostra os Miblos da rede, como uma lista de Wi-Fi, pede para o escolhido mostrar o código e você digita os 4 dígitos da tela.

- Recém-conectado: nome, IP e código
- O código de pareamento, quando o app pede

- Para parear de novo ou outro Miblo: no app (Meus Miblos › Parear outro Miblo), com miblo pair no terminal ou /miblo:pair no Claude Code. Se a busca não achar o Miblo, use o IP que aparece na tela, logo abaixo do nome: miblo pair 192.168.0.57.
- O /miblo:pair também pergunta como chamar o Miblo (até 20 caracteres) e se ele pode saber seu primeiro nome e seu aniversário, para dar bom-dia.
- Para ver os limites de uso, permita a ligação com a status line (no Claude Code: rode /miblo:link-statusline). A sua status line continua exatamente igual, e /miblo:unlink-statusline desfaz.
- Um Miblo aceita até 4 computadores, e um computador pode parear com vários Miblos.
- Cinco códigos errados seguidos travam o pareamento por 60 segundos, e o tempo dobra a cada nova série de erros.

A página de ajustes abre em http://miblo.local, de qualquer celular ou computador na mesma rede, ou com /miblo:settings. Mudar um ajuste pede o código mostrado na tela, a prova de que é você quem está na frente dele.

## Comandos

Source: https://miblo.ai/docs#comandos

Os comandos rodam no terminal como miblo <comando> (por exemplo miblo focus) e, no Claude Code, como /miblo:<comando>; a lista abaixo usa a forma do Claude Code. Muitos também estão no app Miblo (Atalhos). Com um só Miblo pareado, o id é opcional; miblo status mostra os ids. Os comandos do dia a dia vão para todos os Miblos pareados; use --id <id> para mandar a um só.

- `/miblo:pair [ip]`: Acha o Miblo na rede, pede o código da tela e pareia. Depois pergunta o nome e oferece ligar a status line.
- `/miblo:status`: Mostra o bridge, a status line, cada Miblo pareado, as sessões ativas, os limites e o resumo do dia.
- `/miblo:mode overview | limits | sessions`: Escolhe o modo de tela.
- `/miblo:rotate on | off`: Na visão geral, alterna para a tela de limites de tempos em tempos.
- `/miblo:focus [foco [pausa [rodadas]]] | stop`: Começa um foco (Pomodoro): 25 minutos de foco e 5 de pausa, 4 rodadas por padrão.
- `/miblo:meeting [minutos] | off`: Modo reunião: nenhum nome de projeto, comando ou ferramenta na tela.
- `/miblo:say <texto> | off`: Um recado para quem passa pela sua mesa, por 30 minutos ou o tempo que você quiser.
- `/miblo:remind <minutos | HH:MM> <texto>`: Lembretes e alarmes diários ou de dias úteis.
- `/miblo:timer <minutos> | stop`: Uma contagem regressiva grande na tela.
- `/miblo:countdown <rótulo> <DD/MM> | off`: Contagem de dias até uma data, na mesa e na plaquinha do pet.
- `/miblo:limits`: Os limites de 5 horas e da semana, quando zeram e a previsão de quando acabam.
- `/miblo:today`: O resumo do dia no terminal: respostas, tempo, custo e limites.
- `/miblo:blue [on | off] [HH:MM HH:MM] [força%]`: Filtro de luz azul, sempre ou num horário, de 1% a 100%.
- `/miblo:night on | off [HH:MM HH:MM] [brilho%]`: Diminui o brilho entre duas horas.
- `/miblo:find`: Faz o Miblo piscar e acenar com o QR code da página de ajustes, para achar um entre vários.
- `/miblo:demo [minutos | stop]`: Com dois ou mais Miblos, põe todos no modo pet agora para ver as visitas.
- `/miblo:rename [id] [nome]`: Dá um nome ao Miblo (até 20 caracteres).
- `/miblo:owner --name <nome> --birthday <DD/MM>`: Conta ao Miblo seu primeiro nome e seu aniversário. Os dois ficam só no aparelho.
- `/miblo:settings [id]`: Abre a página de ajustes no navegador.
- `/miblo:update [id]`: Atualiza o plugin e depois o firmware de cada Miblo, com o código da tela.
- `/miblo:link-statusline`: Liga a status line do Claude Code ao Miblo, para os limites aparecerem.
- `/miblo:unlink-statusline`: Devolve a sua status line original. Rode antes de desinstalar o plugin.
- `/miblo:reset <id>`: Restaura o Miblo de fábrica: apaga Wi-Fi, pareamentos e ajustes. Pede confirmação.
- `/miblo:setup [codex | copilot | gemini | opencode | cursor] [--remove]`: Mostra no Miblo as sessões de outra IA. Sem argumentos, lista as que foram achadas e conectadas.
- `/miblo:phone [on | off | list]`: O app de celular, opcional: liga (pela sua conta Miblo), lista os celulares ou desliga e esquece as chaves.

## Outras IAs

Source: https://miblo.ai/docs#outras-ias

O Miblo (e o app de celular) mostra as sessões de todas as IAs de programação conectadas na mesma lista. Uma etiqueta pequena antes do detalhe diz de qual IA é a sessão (“Codex · npm test”). Ligue ou desligue cada uma no app Miblo (Ferramentas de IA) ou com miblo setup <nome>.

| IA | Como conectar e o que aparece |
| --- | --- |
| Codex | /miblo:setup codex; depois, no Codex, rode /hooks e confie nos hooks do Miblo. Trabalhando, precisa de você e terminou, mais os limites de 5 horas e da semana. |
| GitHub Copilot CLI | /miblo:setup copilot. Trabalhando, precisa de você e terminou. |
| Gemini CLI | /miblo:setup gemini. Trabalhando, precisa de você e terminou. |
| OpenCode | /miblo:setup opencode; depois reinicie o OpenCode. Trabalhando, precisa de você e terminou. |
| Cursor (o agente dele) | /miblo:setup cursor; depois reinicie o Cursor. Trabalhando e terminou: o Cursor não avisa quando espera aprovação. |

- O app Miblo pergunta, para cada IA que achar no computador, se as sessões dela aparecem no Miblo. Depois, mude no app (Ferramentas de IA); no terminal, miblo setup sozinho lista o que foi achado e conectado.
- /miblo:setup <nome> --remove tira só os hooks do Miblo; as suas configurações ficam como estão.
- Os limites de uso vêm do Claude Code e do Codex; as outras IAs não informam limites.
- Nada a mais sai do computador: só o nome da pasta da sessão, o estado e a ferramenta em uso. Nada de prompts, respostas ou arquivos.

Codex, GitHub Copilot, Gemini, OpenCode e Cursor são marcas dos seus donos. O Miblo não é afiliado a eles.

## SDK de status

Source: https://miblo.ai/docs#sdk

Seus próprios programas também aparecem no Miblo: um script de build, um job de dados, uma IA que o Miblo não conecta. Cada um vira uma sessão no aparelho e no celular (trabalhando, precisa de você, ociosa ou terminada) e pode mostrar uma mensagem curta na tela, iniciar um foco ou um timer.

Só status: o SDK não aprova, não responde e não inicia tarefas, e nada nele liga essas funções. Precisa de um Miblo com o comando miblo sdk (confira com miblo sdk status).

No seu terminal: liga a API e entrega o token ao seu programa:

```
export MIBLO_TOKEN=$(miblo sdk token)
```

### Node.js

Instalar (@miblo/status 1.0.0, Node 20+, sem dependências):

```
npm install https://miblo.ai/dl/sdk/miblo-status-1.0.0.tgz
```

Exemplo: uma sessão que precisa de você:

```
// MIBLO_TOKEN=$(miblo sdk token) node needs-you.mjs
import { MibloStatus } from '@miblo/status';
import { createInterface } from 'node:readline/promises';

const miblo = new MibloStatus();
const job = await miblo.session({ tool: 'deploy.mjs', title: 'Deploy', detail: 'building' });
await new Promise((r) => setTimeout(r, 3000));  // ...your work...
await job.needsYou('confirm the deploy');
await createInterface({ input: process.stdin, output: process.stdout }).question('Deploy? [enter] ');
await job.done('deployed');
process.exit(0);
```

### Python

Instalar (miblo-status 1.0.0, Python 3.9+, só a biblioteca padrão):

```
pip install https://miblo.ai/dl/sdk/miblo_status-1.0.0-py3-none-any.whl
```

Exemplo: uma sessão que precisa de você:

```
# MIBLO_TOKEN=$(miblo sdk token) python3 needs_you.py
import time
from miblo_status import MibloStatus

miblo = MibloStatus()
job = miblo.session("deploy.py", title="Deploy", detail="building")
time.sleep(3)  # ...your work...
job.needs_you("confirm the deploy")
input("Deploy? [enter] ")
job.done("deployed")
```

### O contrato (Status API v1)

- Token próprio: miblo sdk token cria um token só de status (nunca a chave do bridge) e liga a API; sem ele, tudo é recusado. miblo sdk token --rotate troca o token e miblo sdk off desliga a API.
- Só no computador: o bridge do Miblo em 127.0.0.1:47821, com desafio e resposta HMAC-SHA256 em cada pedido e em cada resposta. Navegadores e outros computadores ficam de fora.
- Sessões: tool (o nome do programa, até 20 caracteres), title e detail (até 64) e o estado working, needs_you, idle ou done. needs_you e done avisam no aparelho uma vez por mudança. Até 8 sessões ao mesmo tempo; a sessão acaba quando o processo termina.
- Ações no aparelho: uma mensagem de até 40 caracteres (1 a 480 minutos), um foco ou um timer, como miblo say, miblo focus e miblo timer. Sem Miblo pareado, delivered é 0, sem erro.
- Leitura: um retrato só de status (nomes, estados e aparelhos), sem comandos, prompts, arquivos, custos ou nada do Miblo+.
- Limites: 10 mudanças de sessão por segundo, 3 ações seguidas e depois 1 a cada 10 s, corpo de até 4096 bytes. Os erros têm códigos estáveis (sdk_off, not_authorised, unknown_session, rate_limited...).
- A v1 nunca quebra: campos só são acrescentados. Os pacotes seguem semver e a versão 1.x fala a v1.

### Conferir o download

Os pacotes saem só do miblo.ai (não estão no npm nem no PyPI). Cada arquivo tem a sua assinatura Ed25519 ao lado (o mesmo nome com .sig), feita com a chave das atualizações do Miblo, e o SHA256SUMS assinado lista todas as versões.

Baixar e conferir o hash:

```
curl -fLO https://miblo.ai/dl/sdk/miblo-status-1.0.0.tgz
curl -fsSL https://miblo.ai/dl/sdk/SHA256SUMS | shasum -a 256 -c --ignore-missing
```

[SHA256SUMS](https://miblo.ai/dl/sdk/SHA256SUMS)

## App de celular

Source: https://miblo.ai/docs#celular

Opcional e desligado de fábrica: o celular mostra o mesmo que a tela do Miblo (sessões, avisos, limites e o resumo do dia) e pode notificar quando uma sessão precisa de você, mesmo longe da mesa. O app é uma página em miblo.ai/app que você adiciona à tela de início.

1. No app Miblo do computador, toque em Entrar com sua conta Miblo e ligue o Celular.
2. No celular, abra miblo.ai/app, entre na mesma conta (com a segunda etapa) e crie o PIN do app. O computador mostra um código de 6 dígitos (no app Miblo, numa notificação ou em miblo phone pending): digite esse código no celular e confirme com a passkey dele. Se não for o seu celular, toque em Recusar no computador.
3. Adicione a página à tela de início (no iPhone: Compartilhar, Adicionar à Tela de Início) e permita as notificações.
4. O celular começa a mostrar as sessões na próxima atividade de qualquer IA conectada.

### Servidor próprio (opcional)

O servidor do celular e o app do celular são de código aberto (AGPL-3.0), distribuídos pelo miblo.ai e assinados como as atualizações do Miblo. Subindo o seu, o celular e o computador conversam só por ele, nunca pelo miblo.ai. É de graça, para quem sabe hospedar.

- Precisa de um host com HTTPS: Docker com Caddy, ou Cloudflare Workers. Os passos e comandos estão no guia do servidor.
- Precisa do Miblo 1.22.0 ou mais novo no computador.

[Baixar e subir o servidor](https://miblo.ai/docs/servidor-proprio)

No computador: aponte para o seu servidor e digite o código mostrado no Miblo:

```
miblo server set https://seu-servidor
```

Para voltar ao miblo.ai:

```
miblo server reset
```

### Pelo terminal

Ligar o computador à conta e o celular:

```
miblo account link
miblo phone on
```

[Controle remoto pelo celular: aprovar, responder e ver os limites](https://miblo.ai/controle-remoto)

- Criptografado de ponta a ponta (AES-256-GCM): a chave nasce no seu computador e chega a cada celular trancada para a chave daquele celular. O miblo.ai guarda e repassa só dados cifrados.
- As notificações dizem apenas que uma sessão precisa de você, nunca qual nem o quê.
- O servidor guarda só o último quadro cifrado, por 10 minutos, sem endereço IP.
- Cada celular novo da conta aparece no seu Miblo e numa notificação do computador. Remova um em Minha conta, Dispositivos, ou com miblo phone revoke.
- O app pede um PIN seu (6 dígitos ou mais), criado logo depois de entrar na conta: ao abrir e depois de um tempo sem uso (1 minuto a 1 hora, ou sempre que sair do app, em Ajustes). O PIN fica só no celular. 5 PINs errados seguidos pausam as tentativas por 1 minuto; 10 bloqueiam o app naquele celular, encerram a sessão da conta nele e mandam um aviso para o seu e-mail: para voltar, entre na conta de novo e crie outro PIN.
- A conta decide quais celulares entram no computador, então vincular ou desvincular a conta (miblo account link / unlink) só roda no seu terminal ou no app, nunca por um agente de IA; o site pede o segundo fator na hora e a conta recebe um e-mail a cada computador vinculado ou desvinculado. Com um Miblo pareado, também pede o código de 4 dígitos da tela dele.
- /miblo:phone off apaga a sala no miblo.ai e faz o computador esquecer as chaves. Desligado, o plugin não se conecta ao miblo.ai.

## Solução de problemas

Source: https://miblo.ai/docs#problemas

| O que acontece | O que fazer |
| --- | --- |
| O app ou o miblo pair não acha o Miblo | Confira se a tela mostra um código de pareamento e se o Miblo está na mesma rede do computador. VPNs, WSL2 e redes corporativas costumam bloquear a busca: digite o IP que aparece na tela quando o instalador pedir, ou rode /miblo:pair <ip>. |
| A tela diz “Senha errada” | Escaneie o QR code de novo e digite a senha outra vez. |
| A tela diz “Rede não encontrada” | O Miblo só enxerga redes de 2,4 GHz. Ligue a banda de 2,4 GHz no roteador ou crie uma rede só para ela, e chegue mais perto do roteador. |
| A tela diz “Conexão recusada” | Confira a senha. Se o roteador estiver em WPA3 ou no modo misto WPA2/WPA3, mude para WPA2. |
| Não aparecem limites | Rode /miblo:status para ver se a status line está ligada; se não estiver, rode /miblo:link-statusline. Os limites aparecem depois da próxima resposta e só existem nos planos Pro e Max. |
| O Miblo diz “Desconectado” | Ele não recebe nada há 30 segundos. A ponte volta na próxima atividade de qualquer IA conectada; confira no app ou com miblo status. |
| Um Miblo aparece como não autorizado | Ele foi restaurado ou pareado com outra coisa. Rode /miblo:pair de novo. |
| Nada chega pelo app desktop ou pela IDE | Rode /miblo:update ali: ele confere o Node.js primeiro e diz o que falta. |
| Status line em branco depois de desinstalar | Reinstale o plugin, rode /miblo:unlink-statusline e desinstale de novo. Da próxima vez, rode o unlink antes. |

Para restaurar de fábrica sem computador, ligue o Miblo 6 vezes seguidas, rapidamente. Uma contagem na tela deixa você cancelar.

## Pedidos, entrega e trocas

Source: https://miblo.ai/docs#pedidos

- O pedido é confirmado quando o pagamento é aprovado. O QR code do Pix vale por 30 minutos e o boleto vence em 3 dias.
- O prazo de entrega aparece na compra e conta em dias úteis a partir da confirmação do pagamento. Mandamos o código de rastreio por e-mail quando o pedido sai.
- Para acompanhar, abra Meu pedido com o código do pedido e o e-mail da compra, ou entre na sua conta e veja Meus pedidos.
- Mudou de ideia? Você pode desistir em até 7 dias corridos depois de receber, sem explicar o motivo. A devolução não custa nada e o valor volta pelo mesmo meio de pagamento.
- Garantia de 90 dias contra defeitos, contada do recebimento: consertamos, trocamos ou devolvemos o valor.

[Acompanhar meu pedido](https://miblo.ai/pedido)

Atrasou, chegou avariado ou quer desistir? Escreva para contato@miblo.ai com o código do pedido.

## Sua conta

Source: https://miblo.ai/docs#conta

Uma conta só, entrando com o seu e-mail, junta os seus pedidos, o Miblo+, os pets que você cria no Studio e a sua participação na comunidade. Para usar o Miblo na mesa, você não precisa de conta.

- Para entrar, digite o seu e-mail: mandamos um código. Se for a primeira vez, a conta é criada nessa hora.
- Em Segurança, ative a entrada com digital ou rosto (passkey). É mais rápido e mais seguro que o código por e-mail.

[Abrir minha conta](https://miblo.ai/conta)

## Miblo+

Source: https://miblo.ai/docs#miblo-plus

O Miblo+ é uma assinatura opcional: o Miblo funciona completo sem ele. Veja o que inclui e os preços na página do Miblo+. Para ver o seu plano, os pagamentos ou cancelar, entre em Minha conta › Miblo+.

[Conhecer o Miblo+](https://miblo.ai/plus)

## Studio: crie o seu pet

Source: https://miblo.ai/docs#studio

No Studio você cria um pet só seu: comece de um dos 20 bichinhos, mude as partes e as cores e salve. Você recebe um código para instalar no seu Miblo, e os seus pets ficam guardados em Minha conta › Meus pets.

[Abrir o Studio](https://miblo.ai/comunidade/studio)

# Latest release notes

## Miblo 1.24.0 (2026-10-08)

## Sem o aparelho

- **The Miblo gadget is optional.** Miblo installs and runs without one: the Miblo app, the pet and your sessions' status (on your phone too, with a free Miblo account) work on their own, and Miblo+ stays the paid plan. What a gadget adds is a screen on your desk, the pet at your desk, and visits between Miblos. A computer can be linked to your Miblo account with no gadget at all.
- **Pairing is a step you can skip.** The installers (`install.sh`, `install.ps1`, "Install Miblo.command") ask "Have a Miblo on your desk?": Return pairs it now, `l` (or `d` in Portuguese) leaves it for later. The Miblo app asks the same at the end of the install (**Pair now** / **Later**). `--no-pair` still skips the question.
- **No Miblo answering is never an error.** When nothing answers on your network, the pairing wizard says the gadget is optional and finishes (Esc in the picker, Return in the plain questions; `r` searches again), and the installers end normally with how to pair one later. `/miblo:pair` and `miblo pair --wizard` work as before.
- **Empty states instead of errors.** With no Miblo paired, the app's **My Miblos** says "No Miblo paired" with **Add a Miblo**, `miblo status` and `/miblo:status` say the same in one line, and the app's **Now** tab, the status line and the hooks work as usual. The Claude Code start-of-session note about pairing is shown once, and says the gadget is optional (it used to come back every day).

## Linking the account (audit 2026-10-08)

- **An AI agent can no longer link this computer to a Miblo account or unlink it.** The account decides which phones may join this computer, so `miblo account link` and `miblo account unlink` (and so switching accounts) are refused under an AI agent; `/miblo:plus` now tells you the command to run in your own terminal (or **Sign in with your Miblo account** in the Miblo app) instead of running it.
- **With a Miblo paired, a change of account needs the code on its screen**, as `miblo server set` already does. Linking asks for it once you confirmed the link code on miblo.ai, names the account about to be linked, and writes nothing before it (a refused link gives its token back to the site). Unlinking asks for it too. In the Miblo app you type the code on the Phone screen; from elsewhere, `miblo account confirm <code>` finishes it. No longer have that Miblo? Forget it in **My Miblos** and link again.
- **With no Miblo paired**, linking still needs your own terminal or the Miblo app, the site asks your second factor again when you confirm the code, and your account gets a security e-mail for every computer linked or unlinked, with its name ("computer linked" / "computer unlinked", within the account's hourly notice budget). Unlinking still takes the account's phones off this computer.

## A tela do Miblo no app

- **The Miblo's screen, live, in the Miblo app.** The **Now** tab shows the Miblo's screen as it is right now: your sessions, the limit rings, "needs you", the quiet Desk, pet mode and the greetings. It is the gadget's own screen code (built from the firmware as WebAssembly), so it behaves exactly like the gadget. It wears the look of your first paired Miblo, My pet included, or the factory look when you have no Miblo. It follows the app's language and your computer's time zone.
- **No gadget needed.** The screen in the app works the same with or without a Miblo on your desk. With a Miblo paired, the app reads its look from it every few minutes, only while the app asks.
- **Light on the computer.** The screen draws 10 frames a second only while the Now tab is on screen, and stops while the window is hidden or another tab is open.
- What the app's screen does not show: Wi-Fi and pairing screens, updates, visits between Miblos, and what reaches the gadget through its own commands (focus, timer, `/miblo:say`, reminders, meeting mode). See [docs/screen-in-app.md](../screen-in-app.md).
- For tools: `miblo status --screen` adds the snapshot the gadgets get and the first Miblo's look (plain `miblo status` is unchanged). Firmware developers: `make screenweb` builds the module (emcc 6.0.10) and tests it.

## Responder pelo celular em todas as IAs

"Você responde pelo celular. Se a sessão está trabalhando, a resposta entra quando ela termina a vez; se está parada, ela acorda e responde." No channel to accept, no new window, no system dialog.

- **Every AI tool Miblo shows takes replies from the phone (Miblo+).** A reply typed while a session works goes in when it finishes its turn, through each tool's own end-of-turn hook: Claude Code, Codex, GitHub Copilot CLI, Gemini CLI and Cursor. The phone says "Entra quando a sessão terminar a vez", then "Entregue".
- **An idle session wakes up and answers.** Claude Code (a background hook that wakes the session), Codex (`codex queue`) and OpenCode (Miblo's OpenCode plugin) through their official ways. Copilot CLI, Gemini CLI and Cursor have none: when the session runs in tmux or GNU screen, Miblo types the reply into its own terminal after checking that the session is the one in front; otherwise it goes in at the next turn end.
- **Approvals from the phone for Codex and OpenCode**, as for Claude Code: only the prompts the tool itself shows, never anything it would not have asked. Copilot CLI, Gemini CLI and Cursor keep their own flow (status and replies).
- **Remote tasks continue from the phone.** Answer a Claude Code task and it goes on, still in the background, with the same safe mode, time limit and Stop; `miblo plus tasks open <id>` (and the app's **Abrir**) opens it in your terminal where it stopped.
- **Fixed:** remote Claude Code tasks inherited a marker of the session that started Miblo's bridge and could run without saving their transcript.
- Every reply is shown on the computer (the gadget and a notification naming the phone) and kept in `miblo plus audit`. After updating, run `miblo setup codex` again (or let the bridge add it) and trust Miblo's two new hooks in Codex's `/hooks`; restart OpenCode, Copilot CLI, Gemini CLI and Cursor sessions to pick up the new hooks. Claude Code sessions started before the update keep the old reply channel.

## Pareamento protegido na rede local

- **The pairing code never goes on the network any more (audit 2026-10-08, M1).** Pairing a Miblo now runs a password-authenticated key exchange with the 4-digit code on its screen: your computer and the Miblo prove to each other that they know the code without ever sending it, and the pairing token is worked out on both sides, never sent either. Someone else on the same Wi-Fi who intercepts the pairing gets one guess at the code per attempt, counted by the Miblo's wrong-code lockout, and nothing they can study afterwards. The token signs every request from the first one (no rotation needed).
- **Firmware 1.24.0 only pairs this way.** An older Miblo app or plugin can no longer pair it: update Miblo on that computer first. Pairings you already have keep working as they are.
- **A Miblo on an older firmware is updated first, in the same step.** Miblo never falls back to sending the code in clear. When you pair a Miblo still on 1.23 or older (`/miblo:pair`, `miblo pair`, the installers' pairing step), Miblo says "This Miblo is on 1.23: updating it first", pairs it the old way only to run the update at once (the signed release, the update code on its screen), then asks for the new pairing code and pairs it the protected way, in the place of that temporary pairing. If the update cannot run (no internet, no firmware for that board, you stop), the temporary pairing is dropped and nothing stays paired on the computer (the Miblo's settings page may still list it until you remove it there). A Miblo once seen pairing the protected way is never paired the old way again from that computer.
- For tools: on that path `miblo pair <ip> <code>` ends with exit code 5 (type the update code: `miblo pair <ip> --update <code>`, which ends with 6 once updated), and `miblo pair <ip> --update-cancel` gives up; `/api/info` and the mDNS TXT advertise `pair: 2` / `pv=2`. Details in [docs/lan-pairing-pake.md](../lan-pairing-pake.md).

## Fixes/Segurança

- **Security audit 2026-10-08, the computer-side Lows:** `plus.json`'s signature now also covers the history, the approval timeout and the task time limit (a `plus.json` from 1.21-1.23 keeps its switches; `miblo plus status` names the three to confirm again, once, with one `miblo plus set …` on your phone); the bridge reads at most one body per challenge and refuses an oversized one before reading it; "Parar" also stops what a remote task started outside its process group (`setsid`), and on Windows stops the whole tree from the first step; `approvals.log` is signed and chained, checked by the new `miblo plus audit verify`; `miblo update rollback` is refused under an AI agent; redaction also hides long random tokens, a hex key after a secret word, `password X` in a command and the values a tool gives under secret-named keys.

## Miblo 1.23.2 (2026-10-08)

- **Fix: replies from the phone never registered their channel.** The command that registers the reply channel in Claude Code (`claude mcp add`) was given the server's name after the `-e` option, which takes several values, so Claude Code read the name as an environment entry and refused it — on every computer, since replies exist. The name now comes first. With replies on, the next start of the Miblo bridge registers the channel (nothing to redo), and the Miblo app's "turn replies off and on again" warning goes away. Sessions still need to be started with the command the app shows (Claude Code's channels preview).

## Miblo 1.23.1 (2026-10-08)

- **Fixes:**
  - **A new phone no longer waits for ever.** After you typed the computer's code on the phone, the phone app threw away the computer's proof that the code was right, so it kept showing "Waiting for your computer" and never showed the sessions. The phone app (miblo.ai/app and a self-hosted relay) now keeps that proof and connects within seconds; a phone that reads it late still connects. The exact step is now covered by a test on both sides.
  - **Replies from the phone now work when turned on with the phone's confirmation.** Turning replies on (in the Miblo app, in a terminal or through the plugin) confirmed on your phone left them on without the reply channel in Claude Code, so the app said "turn them off and on again" for ever. The computer now registers the channel when the change is applied and whenever it starts with replies on. Nothing to redo: update, and the next start of the Miblo bridge registers it.
  - The code field of the computer's confirmation on the phone is visible in dark mode (border, background and a placeholder).

## Miblo 1.23.0 (2026-10-07)

- **Confirm on your phone, with the code your computer shows (Miblo+):** turning on approvals, replies, history or new tasks, adding a task folder, or a longer wait or task limit no longer asks for the code on your Miblo's screen. Your computer (the terminal or the Miblo app) shows a 6-digit code; open the Miblo app on a phone you already use, check what it turns on, type the code and confirm with the phone's passkey (Face ID, Touch ID, fingerprint or PIN). Nothing changes before that. Three wrong codes cancel the request, and at most 6 can be asked in an hour. `miblo plus confirm status` shows the waiting one and `miblo plus confirm cancel` withdraws it. Turning things off still applies at once.
- **A new phone types the code, not your computer:** when a phone signs in to your Miblo account, your computer shows a 6-digit code (in `miblo phone pending`, the Miblo app and the notification) and you type it on the new phone. The code never travels: phone and computer run a password-authenticated key exchange over it, so not even the relay or our servers can learn it or answer in the phone's place. Three wrong answers turn the phone away. On Miblo+, if this computer already has a phone with a passkey, you also confirm the new one there. `miblo phone approve --code` is gone; `miblo phone deny <id>` still turns a phone away.
- **One passkey per phone:** a phone that already has a Miblo passkey reuses it (after asking once) instead of making a new one each time it joins a computer.
- **Approvals can wait up to an hour:** a permission prompt now waits for your phone from 15 seconds up to 1 hour (`miblo plus timeout <15-3600>`, or the choices in the Miblo app), and the card on the phone counts down in minutes and hours.
- **Miblo app 1.5.0:** shows the confirmation code on screen while your phone confirms a change, shows the new phone's code to type on it, and says which account this computer is signed in to ("Connected as <email>") with **Sign out** right there.
- **Security notices by e-mail:** every use of a recovery (emergency) code, wrong or locked-out attempts at one (at most one e-mail an hour), every new passkey added to your account and every phone added with a new passkey send a security notice e-mail (a self-hosted relay sends no e-mails), so you know at once if someone else tries.
- **Fixes:**
  - The approval card on the phone follows the wait set on the computer instead of stopping at 2 minutes.
  - Long waits no longer cut a permission prompt off after 5 minutes.

## Security audit

- The Miblo+ confirmation screen on the phone now shows exactly what will be switched on: the computer builds that text from the settings it will apply, and the settings are checked again when applied, so another program on the computer cannot show one thing and change another.
- Computer folder names and phone names are refused when they carry hidden or direction-changing characters.

## Miblo 1.22.0 (2026-10-07)

- **Up to four Wi-Fi networks, no more factory resets (firmware 1.22.0):** take your Miblo from home to the office and back and it joins whichever saved network is around, the strongest one (the one it used last wins a near tie). If none of them shows up for two minutes it opens its setup network as before, but now nothing is erased: pairings, name, pet and settings all stay, and it keeps looking for its networks in the background. A network you join through the setup network is added to the list. Your current network is kept on the update.
- **Change or add Wi-Fi from the settings page:** the new **Wi-Fi** card (after the on-screen code) lists the saved networks and has **Change / add Wi-Fi**: search for networks (with signal bars), type the password and press **Test and save**. Miblo tries the new network while keeping the current one, checks that it reaches the internet, comes back and tells you how it went: saved (with its address on that network), or why not (wrong password, network not found, no internet), with nothing changed. Tick **Make it the main network** to have Miblo move there right away. **Forget** removes a saved network; the one in use is forgotten only after Miblo moved to another saved network that works. The password travels encrypted from the page to your Miblo.
- **From the terminal:** `miblo wifi list`, `miblo wifi add <name>` (the password at a hidden prompt, or piped on stdin, never on the command line; plus the code on your Miblo's screen) and `miblo wifi forget <name>`. `miblo settings --wifi` opens the settings page at the Wi-Fi card.
- **Your computer follows your Miblo:** after a move to another network the pairing stays, and your computer finds your Miblo again at its new address by itself.
- **A simpler settings page:** the top now shows your pet, its name, its address, the firmware version and the Wi-Fi it is on. What people change most is right there (name, pet and look, Wi-Fi, firmware update); everything else sits in sections that open with a tap (screen and schedule, alerts and well-being, about you, looks and community, my pet, paired computers, advanced) and stay the way you left them.
- **Run your own relay server:** `miblo server set https://…` — open source (download and README at miblo.ai/docs/servidor-proprio; code at github.com/marcus-campos/miblo-relay); the phone and account then never touch miblo.ai.
- **Fixes:**
  - In the Miblo app's window, **Code on the screen** on the settings page did nothing: the page asked for the code in a browser dialog the app never shows. The code field, the confirmations (forget a network, remove a computer) and the factory-reset code are now part of the page itself.
  - A Miblo no longer turns "unauthorized" (needing to be paired again) when a Claude Code window not reloaded since the update still runs the previous Miblo next to the new one. The new pairing token is never stored where that older copy would send it in clear, and with firmware 1.22.0 the older copy keeps working for a week after the switch to the new token.
  - Once an older Miblo is seen running in another window, the current one stays in charge instead of handing your Miblo back to it after a quiet half hour.
  - `/miblo:status` says when the bridge answering belongs to an older Miblo (reload the other Claude Code windows), and says plainly when a Miblo really needs to be paired again; `/miblo:pair` then shows the code on the gadget's screen.