Permission prompts
For sessions in tmux, perch reads the prompt off the screen and answers it for you. For sessions anywhere else (Cursor included), turn on Settings → Decisions → Answer permission prompts here.
What it changes
Section titled “What it changes”- It adds one Claude Code hook to each account’s
settings.json, after saving a copy assettings.json.before-perch. Turning it off takes the hook out again. - Claude Code hands each permission prompt to perch while still showing it in the terminal. Whichever you answer first wins.
- If perch isn’t running, the prompt works exactly as before.
- Sessions already open pick it up at their next prompt. No restart needed.
Questions (“1, 2 or 3?”) come too: pick a choice, several where it allows, or type your own answer. Plans still need their terminal, or a tmux session.
Always allow
Section titled “Always allow”Always saves a rule in the project’s Claude Code settings, so that exact command isn’t asked about again. perch never offers it for a command that carries a key, token or password, because Claude Code saves the rule as written and the secret would sit in a settings file.