Use cases
Keep client coding sessions in view on your Mac
Updated · 2 min read
Client work can leave you with several projects and several agents open at once. Perch gives the sessions on your Mac a shared place to show their status, so you can choose the right one before responding.
Check the project before the request
When sessions belong to different clients, the first question is which project is asking. Perch keeps status alongside project context and lets you rename sessions locally. Clear names make it easier to spot a familiar command in the wrong project.
The shelf groups attention by state. Start a review in Needs you, leave running tasks in Working, and find completed turns in Recent.
A review routine for parallel client work
- Give each session a distinct project and a bounded task. Use separate working copies when changes might overlap.
- Name sessions so the client and purpose are easy to recognize.
- Before approving, check the project, the command or change, and the agent’s reason.
- Inspect the resulting diff and use your existing client delivery checks.
Local visibility is a personal work surface
Perch makes no network requests and keeps its status and notes on your Mac. It does not create a client portal or share transcripts with coworkers. Your agents remain separate services with their own data handling.
Perch’s local behavior does not change a provider’s terms or establish a confidentiality certification. Decide which tools may handle each client’s material in your existing process.
Common questions
Can my agency share one live shelf?
Perch has no shared team dashboard. Each shelf is local to its Mac.
Does Perch resolve overlapping edits?
No. Use task boundaries and separate working copies. Perch reports activity; it does not merge code.
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