AgentPerchA little help,
when you need it.
Connection questions, session states and the boundaries of the current beta.
AgentPerch is currently in private beta. A paid Mac App Store release is planned; no public download, price or launch date is available yet.
Which tools work with AgentPerch?
Codex CLI, Codex desktop, Claude Code CLI and Claude Code desktop have basic real-event evidence. That baseline does not establish complete failure, approval or permission coverage. CLI support and desktop support are evaluated separately. This evidence comes from the private-beta integration; the forthcoming Mac App Store transport still needs its own compatibility and release acceptance.
- Codex CLI: basic live lifecycle and per-request token observations. Clarification questions are not currently tracked; a question may need your attention without appearing in Needs you. The full failure and approval matrix remains under acceptance.
- Codex desktop: live tool and permission events observed. A session link can be dispatched, but the exact destination has not been established by GUI read-back.
- Claude Code CLI: basic live lifecycle observed; full failure and approval acceptance remains.
- Claude Code desktop: basic live lifecycle and matching session resume observed.
- Cursor: experimental; live CLI start/end transport observed, with fuller lifecycle and desktop verification incomplete.
- Gemini CLI and Copilot CLI: experimental adapters tested with fixtures; real installed-host delivery is not established.
- OpenCode: experimental partial bridge; current lifecycle and permission coverage remains unresolved.
Regular Claude Chat and Cowork are not supported. AgentPerch does not automatically monitor arbitrary apps.
Common questions
How do I connect a session?
In welcome setup, choose Codex or Claude Code and follow the connection steps. Start a new coding session and submit a prompt. The live checklist needs an event arriving during setup. You can continue setup later if you are not ready to connect.
What if a connection stops updating?
Check connection health in the app, then use its repair option if offered. Repairs preserve unrelated settings and create private backups. Start a new supported session and look for a fresh event. A configured handler alone does not prove events are arriving.
Why is an old request still in Needs you?
An unresolved approval or input request stays visible even when its status becomes unconfirmed. A question mark indicates unconfirmed status. Dismiss is a local acknowledgement; it does not approve the request in your coding tool. A new attention episode can bring the session back.
Does opening a session mark it reviewed?
No. Mark reviewed is an explicit action. A successful link dispatch means macOS accepted the link; it does not prove the intended session opened or that you reviewed it. Where an exact app route is unavailable, use a copyable CLI resume command when offered.
What do the usage numbers mean?
Usage covers retained, observed Codex model requests within the shared 10,000-event window. Cached input is included in input. Earlier or unobserved requests may be missing. Claude usage, subscription allowances, reset times and monetary estimates are unavailable. Activity counts are received status events, not productivity or time worked.
Can I use it without a notch?
The menu-bar panel is available alongside the notch interface. Primary-click its icon to open the panel; secondary-click for commands. The default global shortcut is Control–Option–A and can be configured in General settings. Physical notch hover, fullscreen/Spaces and multi-display acceptance still need real hardware checks.
Are notifications enabled automatically?
No. Attention notifications need explicit enablement and macOS permission. Completion notices have a separate opt-in. Notices use generic provider/status text. Notice routing stays in memory and does not survive app relaunch. Brief states between the two-second samples can be missed.
How do I stop activity collection?
Remove the integration to stop its new events. Hiding a provider changes only the displayed sessions and counts. Installed hooks can continue writing events when AgentPerch is closed. Before removing local data or backups, check whether other configured hooks still use the shared support folder.
Mac requirements and availability
The current private beta targets Apple Silicon and declares macOS 14 or later. Current native QA evidence is from macOS 26 on the development Mac; this is not a claim of acceptance across every supported macOS version. Public distribution and clean-machine acceptance remain release gates.
Contact support
Email contact@whodevelop.com with your AgentPerch version, macOS version, coding tool, and whether you use its CLI or desktop app. Describe what you expected and what happened.
Review screenshots and logs before sharing them. Remove private project labels, paths, identifiers, prompts and credentials. Do not send raw provider conversations or activity-folder files unless you have reviewed their contents.