Troubleshooting
No pull requests
Section titled “No pull requests”Run gh auth login, then check Settings → Connections.
The reply box is greyed out
Section titled “The reply box is greyed out”That session’s terminal isn’t one perch can type into. Install the editor extension, or start sessions from perch.
A permission prompt says “answer in its terminal”
Section titled “A permission prompt says “answer in its terminal””Turn on Settings → Decisions → Answer permission prompts here. The next prompt comes to perch.
Fork or Reopen opened in perch, not my editor
Section titled “Fork or Reopen opened in perch, not my editor”That’s the default. To use your editor, pick it in Settings → Reopen sessions in (it needs the perch extension; Settings → Setup installs it). If it says the extension is too old, install the new one there and reload the editor’s windows.
A Codex session doesn’t show
Section titled “A Codex session doesn’t show”perch finds Codex sessions through Codex’s own background service, so the session’s Codex window needs to be open. Check Settings → Setup lists a codex account.
Agents aren’t adding tasks
Section titled “Agents aren’t adding tasks”Turn on Settings → How agents work → Agents add tasks for you, then restart the session: agents read their instructions when a session starts.
The browser says to open perch from its Mac app
Section titled “The browser says to open perch from its Mac app”A browser needs the one-time link printed by npm start. Run it again for a new one.
The phone can’t reach my Mac
Section titled “The phone can’t reach my Mac”Check the Mac is awake with perch running. Away from your Wi-Fi you need a relay.