Compare
Perch or checking your terminal tabs?
Updated · 1 min read
Your agent’s own terminal is the right place for its full output. Perch adds a nearby view of supported session states so you can decide when that terminal needs attention.
Two ways to find the next handoff
| Need | Checking terminal tabs | Perch |
|---|---|---|
| Read full agent output | Open the session and read it | Open the agent; Perch does not retain transcripts |
| Check several session states | Visit the relevant tabs | See supported sessions together in the shelf |
| Answer a request | Use the agent’s own interface | Use supported opt-in actions or return to the agent |
| See a completed turn | Check the session | See its supported completion event |
| Coordinate overlapping edits | Your project workflow | Still your project workflow |
When the terminal is enough
If you work inside one session most of the time, the original interface may already give you the context you need. You can read output, answer requests and inspect the project without adding a monitor.
A terminal also remains important for detailed review. Perch’s recent steps describe activity and timing, not every command’s output.
When a shelf adds something useful
A local state view becomes useful when the recurring problem is finding which of several sessions needs you. Perch groups supported activity into Needs you, Working and Recent and makes the state visible at the screen edge.
It works alongside your terminal rather than moving sessions elsewhere. Answering is optional and varies by provider. Cursor’s passive hooks do not expose awaiting-permission status, so checking its own interface remains necessary for that case.
Keep both in the review loop
Use Perch to notice the handoff and the terminal or editor to inspect details. Neither a visible status nor a completed turn replaces reviewing the resulting changes.
Your agents, one glance away.
Perch is launching soon. Join the launch list to hear when it is ready.
macOS 14+ · Apple silicon · Native SwiftUI + AppKit