A coding-agent monitor for developers on Mac

Keep implementation and review moving

A coding session alternates between work the agent can do and decisions only you should make. Perch shows that distinction with three states: a blue ring while work is running, an amber dot when a session needs you, and a green check when a turn finishes.

The shelf groups sessions into Needs you, Working and Recent. Use it to choose which session to open. A finished turn is a cue to review the result; it does not mean the code is correct.

A practical development loop

1. Give the agent a bounded task and agree on how you will check its result.
2. Continue your own implementation or review while it works.
3. When a session needs you, read the request. Respond from Perch where supported, or open the agent’s app.
4. Inspect the completed change and run the checks appropriate to the task.

Know what each integration can answer

With answering enabled, Claude Code supports tools, questions, plans and replies. Codex supports allow, deny and replies. Cursor supports replies after a turn finishes; its passive hooks do not expose awaiting-permission status. Answering is off by default, and every answer has two seconds to undo.

Read the compatibility guide ↗

Keep the next thought nearby

Leave a review reminder or the next prompt in one of Perch’s ten local sticky notes. Copy it when you are ready. Perch does not automatically dispatch notes or turn them into a task queue.

Common questions