> ## 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 version

> Print the version of the Reticle server that is actually executing.

`reticle version` prints the running package version. It is the diagnostic to reach for when you need to know which build `npx` actually resolved, which is not always the one you expected.

```bash theme={"dark"}
npx reticle version
npx reticle --version
npx reticle -v
```

All three are the same command. No flags.

## What it prints

One `reticle_version` line. Real capture:

```json theme={"dark"}
{ "t": "2026-08-14T19:38:37.595Z", "event": "reticle_version", "version": "2.8.0" }
```

## Exit codes

Always `0`.

## Worked example

```bash theme={"dark"}
npx reticle version | jq -r .version
```

<Note>
  The version here is the CLI's. A daemon that was already running keeps serving its own build until
  it exits, so [`reticle doctor`](/cli/doctor) is the command that compares the two and names a
  skew.
</Note>