# What to check when agent status is not updating

Canonical: https://perched.fyi/guides/agent-status-not-updating/
Updated: 2026-10-23

A missing state can mean an unconnected session, a stale hook or an event the provider does not expose. Check those separately before changing the rest of your agent settings.

## Start with the connection

1. Confirm Perch is running and monitoring has not been paused.
2. Open agent settings and check that the provider is connected.
3. If Perch offers Repair for a stale hook or moved app, review and use it.
4. Start a new agent session after connecting or repairing.
5. Run a small task and look for activity followed by a completed turn.

## Check the session you are expecting

Make sure you are looking for the correct project and that the session is not hidden. Perch can hide a session until its state changes. A local rename can also make it look different from the terminal title.

A session that existed before hooks were connected may not have picked up the integration. Testing a new session is a more useful check than repeatedly opening an old conversation.


## Distinguish a missing event from a missing answer

Cursor passive hooks do not report awaiting-permission status. Perch will not reconstruct that event from screen contents. Codex desktop coverage has not been verified, and ordinary Claude chats are outside the supported workflow.

If activity appears but an answer card does not, check whether answering is enabled and whether that action is supported for the provider. Perch also steps aside when the session’s own app is in front, and returns requests after the chosen wait.


## An opening problem may be separate

If the session is listed but opening it only brings an app forward, check the destination support. Cursor opens the app, not a particular chat. Exact-tab selection is optional for supported Terminal, iTerm2 and tmux sessions.


## Ask for help with a small reproduction

Write down your macOS version, the provider and whether it is CLI or desktop, whether a new session behaves differently, and which state you expected. Avoid including credentials or private project contents. A clear sequence is more useful than an entire transcript.


[Email Perch support](mailto:support@trillium.one)

## Related reading
- [Perch compatibility: Claude Code, Codex and Cursor](https://perched.fyi/guides/agent-compatibility/)
- [Get started with Perch on your Mac](https://perched.fyi/guides/getting-started/)
- [Approve, answer and reply from Perch](https://perched.fyi/guides/answering-agents/)