Codex and the Claude app
Codex (beta)
Section titled “Codex (beta)”perch finds Codex sessions started in any terminal, live, by asking Codex’s own background service which are open and what each is doing: working, your turn, or needs you (waiting on an approval or a question). Your ~/.codex shows up as an account on its own.
- Conversations, context used, and your plan’s usage come from Codex’s session files.
- Replies go through Codex itself (
codex queue), so they reach a session open in any terminal. - New session, Reopen and Fork run Codex in perch’s terminals.
- Approvals are answered in Codex for now; perch shows that one is waiting.
It’s marked beta because it’s new; if something looks off, say so.
The Claude app
Section titled “The Claude app”Sessions started in the Claude desktop app’s Code tab run Claude Code too, and show up like any other, marked “in the Claude app”. perch shows their status and conversation, and permission prompts can come to perch. The app holds their input, though, so you reply in the app, and close them there. Fork works: it carries the conversation into a perch terminal you can reply to from anywhere.
Gemini CLI is next. Want another agent? See Adding an agent.