Run Doctor first#
Open Settings then Doctor and press Run checks. It checks each enabled agent's supported tracking requirements, sign-in state, and usage source, then offers the exact repair action where one exists. On launch, AgentPeek checks managed integrations and repairs only its own hook entries. Read-only integrations stay untouched.
Common issues#
- A session doesn't appear: check Doctor shows that agent as Ready, then start a new session and produce supported activity. Hook-based integrations may need a session started after setup. A banner under the session header with Open Doctor appears when AgentPeek already knows something needs you.
- Jump back raises the wrong window: window-level jump back needs macOS Accessibility access; the host matrix lists each terminal's exact precision.
- A usage number shows
--: the value is unavailable or stale; press Refresh usage, and remember AgentPeek never invents a quota an agent doesn't report. - Codex sessions aren't tracked: depending on your Codex version, hooks may need to be enabled in its config first, which AgentPeek sets up for you when you connect it.
Update and reach support#
Update AgentPeek from the About tab (Sparkle checks for updates) and try again; the version log shows what each release fixed. If the problem remains, message me on X @brenhubr.