Piepy 0.3.0: know your limits, and Wibey in every editor

The biggest update since launch. Piepy already tells you what your agents are doing; now it also tells you how much you have left, and it follows Wibey into Cursor and VS Code.

Your limits, right in the island

Code Puppy and Wibey usage at a glance. Open the island and a new section at the bottom shows a bar for each agent you've connected. Code Puppy's bar is your 6-hour token block, with large and small models in two greens. Wibey's is your week of credits, in blue. Each comes with when it resets, and hovering a bar gives the exact numbers.
Fresh when you want it. Piepy refreshes every 5 minutes (choose 1, 2, 5 or 10 in Settings → Display), and the little arrow beside each agent checks right now. It rests while your screen is locked or your Mac is asleep.
Honest when something's off. Off the VPN, or Wibey's login has run out? You see the last numbers greyed out with the reason ("Can't reach Code Puppy (VPN?)", "Open Wibey to sign in again"), instead of a bar that quietly lies.
Read-only, and yours to turn off. Piepy only reads: it asks each agent's own usage service, with the login that agent already keeps on your Mac. It sends nothing of yours and never renews a login. Show usage in Settings → Display turns it all off.

Wibey in Cursor and VS Code

The row says where the chat lives. A Wibey chat in the Cursor or VS Code extension now shows as Cursor or VS Code, never "Terminal". So does the Wibey CLI in an editor's built-in terminal.
One click to the right window. Click a row and the editor window that chat runs in comes forward, in a fraction of a second, without starting a second copy of the editor.
Answer without switching. A question from a chat in either editor can be answered right in the island.
Just what you typed. The row's prompt no longer starts with the date and system text the extension adds.
Gone when the editor is. Quit an editor and its Wibey rows go with it; the other editor's stay.

Wibey tells you more

An MCP server asks you something. The row says it's waiting and shows which server is asking and what. A click takes you to the session to answer.
A tool fails. The row shows which one and the first line of its error, until Wibey moves on. One failed tool doesn't mark the whole turn as failed.
Wibey is compacting. When Wibey compacts its context on its own, the row says Compacting…, so a quiet session doesn't look stuck.
Repair at launch. New in Settings → Integrations, on by default: when an update brings new hooks, Piepy fixes your connected agents by itself as it starts, so you don't have to look for the Repair button. It never connects an agent you haven't, and you can turn it off.

Smaller things

About's Privacy section works. Privacy policy, the new Terms of use and What Piepy stores open the real pages, also on company networks that block piepy.xyz.
A smoother opening. The island's bottom corners are round from the first moment it opens (they used to start tight and round off), and there's less empty space under the usage section.

Updating

Piepy updates itself: when 0.3.0 is ready it tells you, and you restart when it suits you. After the restart, your connected Wibey picks up the new hooks by itself.

Installing Piepy

Open Piepy.dmg and drag Piepy onto Applications. Piepy needs macOS 14 or later and an Apple silicon Mac (M1 or newer).

Piepy is free and isn't signed by Apple, so macOS asks you to confirm it once. On macOS 15 and later:

Open Piepy from Applications. macOS says "Apple could not verify 'Piepy' is free of malware...". Click Done
(not Move to Trash).
Open System Settings, then Privacy & Security, and scroll down to Security. It says "'Piepy' was
blocked...". Click Open Anyway and enter your Mac password.
Click Open in the next prompt.

Piepy opens, and from now on it opens like any other app.