Replying

Type in the reply box and perch types it into the session’s terminal, exactly as if you had. To do that it needs a way in:

• Sessions started from perch (⌘N) run in tmux, so they always work. You can watch their live terminal in the window too.
• Sessions in Cursor or VS Code need the small perch extension. It only listens on this Mac and only answers perch.
• Codex sessions take replies wherever they run, through Codex itself (codex queue).
• Sessions in the Claude app take replies in the app, which holds their input.
• Other terminals show their conversation, but replies go in the terminal itself.

The editor extension

The Mac app installs it for you: Settings → Setup, then Install next to your editor. Windows already open pick it up after a reload (⌘⇧P → Developer: Reload Window).

Running from source, build it with cd cursor-extension && npm run package and install perch-bridge.vsix from the editor’s Extensions menu.

In the reply box

• / opens the same slash commands Claude Code has, including your own commands, skills and plugins.
• Paste or drop a screenshot and its path goes into your reply; Claude Code reads it as an image. Screenshots are kept for 30 days.
• A half-written reply stays with its session as a draft.