AgentPeek
Download
OverviewInstallationPill, panel & menu barSessionsPermissions & questionsFollow-up promptsHost matrixSupported agentsToken usageLocal serversQuick RoutesFast ActionsViewsWidgetsAgent BoardNotificationsSettingsLicensing & pricingPrivacyTroubleshooting & support

Reference

Privacy

Local-first by design: your sessions are your business, and the network surface is small enough to list in full.

What stays on your Mac#

  • Session transcripts, diffs, prompts, token usage, project paths, and your local server list stay on your Mac.
  • No accounts, no analytics, no telemetry.
  • Supported local usage is read from data those tools already keep on your Mac. A remote Hermes dashboard is contacted only when you connect one.
  • Cursor usage is read from your Cursor account, using the Cursor sign-in already on your Mac, only when Cursor usage is shown.

Every network call#

The only regular network activity is license checks, Sparkle update checks, those Cursor usage reads, and reads from a remote Hermes dashboard if you point AgentPeek at one in Settings. License activation and deactivation send your license key, machine ID, and app version; deactivation also sends the signed activation instance ID. Starting a trial sends just your machine ID and app version.

How agent data is read#

Monitoring reads the hooks, logs, and local stores each agent already keeps, documented per agent under Supported agents and in Quick Routes. AgentPeek never enables an agent's analytics, never adds credentials, and answers a prompt only when you choose an action, so nothing is ever sent to an agent on your behalf.