Muse Code, already in the fleet.
Perch shows every open session of Meta’s muse CLI in your menu bar — working, finished, interrupted or closed — and taps you when a turn is done, with Muse’s reply. It’s early support: approvals, replies and Stop come once they’ve been measured.
How it works
What a Muse row has today
A row for every open muse terminal
Working, finished, interrupted or closed, titled with the first thing you asked. Muse holds a lock on each live session's folder, so Perch ties every row to its own process — and when you start a new conversation with /new, the row follows it.
A “finished” notification with the reply
When a turn ends, the notification carries Muse's closing reply, on the Mac and as a push to your phone.
Waiting for you to trust a folder
The first time you open Muse somewhere new, it asks “Do you trust this workspace?”. That session reads “Waiting for you to trust this folder” rather than going missing.
Only your sessions
Muse runs small helper agents on every turn, and they fire hooks of their own. Perch drops them, so each conversation is one row. Headless muse exec and muse serve runs get none.
Hooks beside your own
Perch adds its hooks to ~/.config/muse/settings.json next to anything you already have, and Remove Integration takes them out again. Muse runs them with no approval step.
On your phone and your watch
Muse sessions show in Perch Companion and the Apple Watch app under their own name, beside the rest of your fleet.
What’s not here yet
Most of what a fully supported agent gets
No “needs you”
Muse’s approval prompt hasn’t been watched yet, so a session waiting on one doesn’t turn amber or send an alert. Check the terminal when a turn seems to stall.
No approvals, replies or Stop
Withheld on purpose: Meta’s documentation says the approval notice fires only after six seconds, and a reply typed in that window could approve something nobody has seen. They arrive in a later update, once measured.
No Stats or usage bars
Muse’s session log carries per-turn tokens, and nothing in Perch reads them yet. Its 5-hour and weekly windows are only reachable by running a Muse server, which Perch doesn’t do.
No Muse mark on the row
Muse rows wear a plain tint for now, rather than Muse’s own mark.
When these land, Muse joins the eight agents the homepage counts. Each of those has a page of its own saying exactly what it does and doesn’t do.
Pay once for the fleet. Subscribe for the conversation.
One licence covers every agent Perch watches, Muse included — and includes the iPhone companion and all future updates.
Solo
- Lifetime license — pay once, keep it
- One Mac at a time; deactivate in-app to move
- iOS companion, push alerts & Live Activities included
- Notarized app with signed automatic updates
Team
- A license key for every teammate — not one shared key
- Assign and revoke seats by email from your customer portal
- Your seat is claimed on purchase; invite the rest by email
- Same lifetime license and updates on every seat
- Perch Pro is separate — each teammate who wants it subscribes in the iPhone app
Pro
Most popularor $29 a year
Launch price until 15 November, then $49 a year
- A Mac app licence included, for as long as you subscribe — nothing separate to buy
- Read your agents’ conversations from your iPhone, and reply straight back into the session
- Works with your Mac locked, from anywhere your phone can reach it*
Free to download. Pro is an in-app purchase.
* What Pro can reach depends on the agent and on where its session is running. Replying needs the session inside tmux or herdr (Droid, tmux only) — OpenCode uses its own local server instead — and it has to be switched on in Settings, because paying for Pro is not the same as consenting to remote input. Reading a conversation works wherever the session runs. Each agent’s own page says exactly what it supports, and what it doesn’t.
Prices in USD, tax included.
Questions