Use cases
Keep Codex CLI activity and requests in view on Mac
Updated · 2 min read
Keep Codex CLI in its terminal while its state stays visible at your screen edge. Perch supports Codex activity, allow and deny actions, and replies, with a two-second undo for the answers you choose.
Codex beside your other sessions
A Codex session can appear beside Claude Code and Cursor. Check which project is running and which supported request needs attention without moving code or starting sessions inside Perch.
Codex CLI answering has been checked live in the current product record. The Codex desktop app has not been verified. CLI support and desktop support are separate questions when evaluating your setup.
Review before sending
Turn on answering if you want to allow or deny supported requests or reply after a turn ends. Check the request and its project context before choosing. Each answer has a two-second undo window.
Claude Code’s numbered question forms and plan-review actions are not listed as Codex features. The compatibility guide makes the supported boundary explicit.
Start with one session
- Review and connect the Codex hooks in Perch.
- Start a new Codex CLI session after connecting.
- Confirm that activity and the end of a turn appear.
- Enable answering only if you want supported requests in Perch. Keep the terminal for everything else.
Provider access stays separate
Perch does not supply Codex access or pay for provider usage. Its local monitoring does not change what your coding agent sends to its own service.
Common questions
Is the Codex desktop app supported?
It has not been verified in the current product record. The live answering check is for Codex CLI.
Does Codex have Claude Code’s plan controls?
The documented Codex actions are allow, deny and replies.
Your agents, one glance away.
Perch is launching soon. Join the launch list to hear when it is ready.
macOS 14+ · Apple silicon · Native SwiftUI + AppKit