> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reticle.sh/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Reticle is a dev-only, localhost-only verification layer for AI coding agents. It reads program truth (network, state, console, routing, animations, framework state) from inside a running web app and returns a deterministic verdict with evidence. It is not a screenshot tool and not a browser automation library.
> Only `reticle_act_and_wait` and `reticle_assert` produce a verdict. Every other tool moves or reads the app and proves nothing. A drive that ends without one of those two has no result, however many tools it used.
> A verdict of `verified: "unknown"` is not a pass. It means Reticle drove the app and could not tell what happened. Report it as unknown; never weaken a check to make it pass.
> Package names are scoped `@reticlehq/*` and the CLI is `reticle`. Install with `npx reticle init`. The complete tool surface is on the `/usage` page; `/agent-cheatsheet` is the one-screen version.

# reticle telemetry

> Show, enable, or disable Reticle's anonymous usage metrics on this machine.

`reticle telemetry` is the user-facing control for anonymous usage metrics.

```bash theme={"dark"}
npx reticle telemetry [status|enable|disable]
```

## Sub-actions

| Action    | Default                    | What it does                                                                       |
| --------- | -------------------------- | ---------------------------------------------------------------------------------- |
| `status`  | yes, when nothing is given | Report the current state, why it is that state, and where the policy lives         |
| `enable`  |                            | Turn metrics on for this machine                                                   |
| `disable` |                            | Persist a machine-wide opt-out. Unlike `RETICLE_TELEMETRY=0`, this survives shells |

Any other word is a usage error: `unknown telemetry action: <word>`, exit `1`.

## What it prints

Human-readable lines on stdout, like [`doctor`](/cli/doctor). Real capture inside a Reticle source checkout:

```
telemetry    disabled  (this is a Reticle source checkout; developing it is not using it)
policy       https://github.com/reticlehq/reticle/blob/main/docs/telemetry.md
```

When it is enabled, a third line names every way to turn it off:

```
opt out      reticle telemetry disable  (or RETICLE_TELEMETRY=0 / DO_NOT_TRACK=1)
```

## Exit codes

| Code | Meaning                              |
| ---- | ------------------------------------ |
| `0`  | Status shown, or the setting changed |
| `1`  | Unknown sub-action                   |

## Worked example

```bash theme={"dark"}
npx reticle telemetry status
npx reticle telemetry disable
```

<Card title="Exactly what is collected" icon="shield-check" href="/telemetry">
  The complete list, in plain language, and every way to switch it off.
</Card>

<Card title="Every event, in schema detail" icon="database" href="/telemetry-events">
  The contributor reference: payload blocks, field types, and what each event exists to answer.
</Card>