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.
  • The desktop app has no AgentPeek account, product analytics, or 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.

Network activity#

Regular app network activity consists of license checks, Sparkle update checks, Cursor usage reads when shown, and reads from a remote Hermes dashboard if you connect one. 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 your machine ID and app version. Direct Chat uses the selected agent's transport, so that agent can make its normal network calls.

The public website uses Cloudflare Web Analytics. That measurement runs on agentpeek.app, not inside the desktop app, and does not inspect agent activity.

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 or adds credentials. It sends an answer to an agent only after you choose an action.