Monitor and answer Claude Code from your screen edge

Review the request in context

A tool request shows the command or change and Claude’s reason. You can allow or deny it, or return to the terminal. Questions appear as numbered choices. Plan review lets you approve a plan or send feedback so Claude keeps planning.

After a turn, the card can show its last message and a field for your next instruction. Every answer waits two seconds before sending; Esc or Undo takes it back. Perch never chooses the answer.

Connect deliberately

1. Review the proposed Claude Code hook changes in Perch’s setup or agent settings.
2. Connect the integration. Perch backs up the settings before adding its entries.
3. Start a new Claude Code session and confirm its activity appears.
4. Leave answering off to monitor, or enable it when you want supported requests in Perch.

The agent’s own app remains available

Perch steps aside when you are already in the session’s app. Switching back and staying also returns the request to the agent. A handoff wait between 2 and 30 minutes controls how long Perch holds a request.

Ordinary Claude chats are not supported. Claude desktop Code sessions can open their conversation; terminal sessions bring the terminal host forward.

Requests stay in memory

Pending requests travel over a private local socket and are discarded once answered. Saved session status is separate and does not include commands, diffs or transcripts.

Common questions