Optional campaign measurement
Help us learn whether a small advertising test leads to actual use. This is optional: ordinary installation and every product feature work without it.
A click is not an installation
The website records command-copy and package-page interest separately. The CLI can observe its own execution and a successful agent result; the website cannot infer either from a click.
- Copy or PyPI click
- Interest in trying the tool. It does not establish a download, installation or task.
- Executable activation
- The installed CLI ran the explicit measurement command. This is a local executable signal, not a verified package-manager installation count.
- First completed task
- A newly enrolled configuration reached a confirmed successful headless agent result. Queued tasks, failed turns and terminal launches do not qualify.
Choose before guided setup
Choose the Google campaign recipe only if you arrived through that Google test. Otherwise, continue ordinary setup. This is a source label you choose, not proof that an ad click was billed.
The optional command uses the fixed label google / atgent-search-v1. Running it is the choice to attach that label to the CLI's coarse usage counts. It does not copy a browser identifier, click ID or arbitrary URL into your config.
For a new-configuration result, enrollment must happen before atgent init, other configuration commands or a first task. A configuration that already exists is labeled returning; reenrollment does not turn old activity into a new acquisition. There is no backfill.
What leaves your computer
With this choice enabled, the CLI adds the fixed source and campaign, plus new_configuration or existing_configuration, to its existing anonymous counts in PostHog. It reuses the CLI's existing random analytics ID. No email address, prompt, task text, output, file path, repository, credential or browser identifier is added.
Coarse labels
- One fixed source and campaign.
- New or existing configuration.
- Executable and task-result milestones.
Stays out of campaign events
- Email, task text and agent output.
- File paths, repositories and credentials.
- Browser identities and Google click IDs.
The website and CLI keep separate analytics identities. These counts do not establish a unique person, a verified Google ad click or an exact click-to-install conversion rate. An executable can self-report: this is useful operational measurement, not tamper-proof installation attestation.
Control and limits
atgent measurement status shows the local preference and atgent measurement disable stops future campaign labeling. Disabling does not remove counts already received. Setting ATGENT_TELEMETRY=off or DO_NOT_TRACK=1 stops all CLI analytics, including these events; CI is excluded.
Offline use, opt-out and unsuccessful delivery can leave counts missing. No result is invented from a missing event. A completed task means a confirmed agent result; it does not prove that code was deployed, reviewed or correct.
Continue with Getting started. Read Privacy for the existing CLI, website and optional dashboard data practices.