# Perch compatibility: Claude Code, Codex and Cursor

Canonical: https://perched.fyi/guides/agent-compatibility/
Updated: 2026-10-23

Perch brings supported agents into one shelf, but the available actions are different for each integration. Use this table to check the workflow you actually need.

## Supported actions at a glance


Current Perch integration capabilities

| Capability | Claude Code | Codex CLI | Cursor local Agent |
| --- | --- | --- | --- |
| Activity monitoring | Yes | Yes | Yes |
| Awaiting-permission status | Supported | Supported | Not exposed by passive hooks |
| Allow or deny tools | Yes, opt-in | Yes, opt-in | Use Cursor |
| Numbered questions | Yes, opt-in | Not documented | Use Cursor |
| Plan review | Yes, opt-in | Not documented | Use Cursor |
| Reply after a turn | Yes, opt-in | Yes, opt-in | Yes, opt-in |
| Current live verification | CLI activity and answers | CLI answering | Local Agent activity |

## A Code session is different from an ordinary chat

The Claude integration is for Claude Code. Ordinary Claude conversations and OpenCode are not supported. The current product record includes live checks for Claude Code CLI, Cursor local Agent activity and Codex CLI answering.

Codex desktop app coverage has not been verified. Do not assume a desktop app is covered just because the provider’s CLI is listed.


## What opening a session does

Claude desktop Code sessions can open their conversation. Terminal sessions bring the terminal host forward. Optional exact-tab jumping covers Terminal, iTerm2 and tmux. Cursor opens the app rather than a specific chat.

Perch selects and focuses supported destinations. It does not type into a terminal or read its screen. Exact-tab jumping is optional and separate from basic monitoring.


## Answering is always your choice

All answering is off by default and requires opting in. Every response has a two-second undo. Perch steps aside when you return to the session’s app and hands a held request back after your selected wait.

Compatibility depends on events from the connected hooks. If an agent changes its integration behavior, check the connection with a new session before relying on it for a busy workflow.


[Troubleshoot missing activity](https://perched.fyi/guides/agent-status-not-updating/)

## Common questions

### Does every provider have the same actions?

No. Claude Code supports the broadest set. Codex has approvals and replies; Cursor has replies after a turn.

### Does Perch include access to these agents?

No. Agent subscriptions and API usage are separate.

## Related reading
- [Monitor and answer Claude Code from your screen edge](https://perched.fyi/use-cases/claude-code/)
- [Keep Codex CLI activity and requests in view on Mac](https://perched.fyi/use-cases/codex/)
- [See Cursor Agent activity from the edge of your Mac](https://perched.fyi/use-cases/cursor/)