TELEMETRY & PRIVACY

What we collect, and what we never touch

agent-hop is a local-first tool: your sessions, searches, and files never leave your machine. To understand how the tool is actually used and where it breaks, it sends a small amount of anonymous, aggregate usage data. It is on by default, fully disclosed, and takes one command to turn off.

What is collected

  • Which command ran and how it was entered (picker,resume, or a direct agent launch), plus which supported harnesses are on your PATH (names only: Claude, Codex, OpenCode, Pi, Grok).
  • Hops — which harness you left and which you landed on, and whether the live session was converted or started fresh. Not the chat itself.
  • Resume / search — whether you used Ctrl+R or ah resume, source and target harness, whether it was same-agent or cross-agent, and whether a query was present (never the query text).
  • Environment basics — operating system, CPU architecture, and the agent-hop version.
  • An anonymous install id — a random UUID generated on your machine, used only to count distinct installs. It is not derived from your hardware, name, or account.
  • Coarse country — inferred at our server from the request and stored; the raw IP address is never logged or stored.

What is never collected

  • Your search queries.
  • File paths, project names, or directory contents.
  • Any chat content — messages, prompts, tool calls, or attachments.
  • Session ids from your agents, or anything that could identify a specific chat.
  • Your IP address (used transiently for coarse geo, then discarded — never stored).

In short: the events describe how the tool is used, never what you used it on.

How to turn it off

Any one of these disables telemetry completely:

  • Run ah telemetry off (persists across runs; ah telemetry on re-enables, ah telemetry status shows the current state).
  • Set AH_TELEMETRY=0 in your environment.
  • Set the cross-tool DO_NOT_TRACK=1 standard, which agent-hop honors.

Where the data goes

Events are sent to telemetry.agent-hop.com, an endpoint we run ourselves on Cloudflare — no third-party analytics service is involved. Sending is best-effort and bounded: if you are offline or the request is slow, agent-hop drops it silently rather than blocking or slowing anything down. The collection code is open source and auditable in the repository.