# Activity and stats

> See how often Synkro checks actions, which Rules match, and where your agents are working.

Source: https://docs.synkro.sh/guides/stats

Use `synkro stats` for a summary of your recorded Synkro activity. It shows tool
attempts, sessions, decisions, matched Rules, projects, agents and approval
statuses. Use [Events](/guides/events) to inspect the individual actions behind
those numbers.

## See your activity

```sh
synkro stats
```

The default window is the past seven days. A human's signed-in CLI sees the
organization's activity. When your connected agent runs the command, it sees
activity from its own connection and installation.

The report starts with total tool attempts and sessions, followed by outcomes
and per-agent activity bars. Tables stack into labeled rows in narrow terminals.
Set `NO_COLOR=1` for uncolored output, or use `--json` for structured results.

| Section | What it tells you |
| --- | --- |
| Recorded tool attempts | How many tool requests Synkro recorded in the selected period. A retry is another attempt. |
| Sessions | How many agent sessions had recorded tool attempts. |
| Outcome and semantic check | How many attempts received each decision and semantic-check status. |
| Harnesses | Which agents, such as Codex or Claude Code, produced those attempts. |
| Projects | The recorded working directories where those attempts happened. |
| Rules matched | How many distinct attempts matched each Rule. |
| Current consent status | The current approval status of requests associated with those attempts. |

One action can match several Rules. It counts once in the total, and once under
each matched Rule. Approval statuses are current, not a count of every status
change during the period.

An `allow` decision does not necessarily mean a semantic check completed. Read
the semantic-check status alongside the decision. `NULL` means a value is
unavailable, including an attempt without a recorded verdict; it does not mean
Allow or zero.

## Choose a period, project or agent

```sh
synkro stats --from 2026-10-01 --to 2026-10-21
synkro stats --project /work/payments
synkro stats --project /work/payments --harness codex
```

`--project` matches the exact recorded working directory, not a project name or
path prefix. Run the unfiltered command first to find that value. `--harness`
matches the recorded agent name, such as `codex` or `claude_code`. Without these
filters, the report includes all activity you can access.

Dates include the entire final day and use your configured `events_timezone`
(local time by default). For an exact interval, use RFC3339 timestamps with an
offset. See [time formats](/reference/cli#events).

## Use the results with your agent

```sh
synkro stats --from 2026-10-01 --to 2026-10-21 --json
```

Ask your agent to summarize the most frequently matched Rules, compare projects,
or explain the balance of allowed, flagged, approval-required and blocked
attempts. JSON includes the applied `window`, `as_of`, `scope`, `tool_attempts`,
`sessions`, and the grouped results. Ranked lists can be shortened;
`ranked_lists_truncated` tells you when that happens. Totals and outcome counts
still cover the whole selected window.

To inspect the actual decisions in the same period:

```sh
synkro events --type verdict --from 2026-10-01 --to 2026-10-21 --details
```

Follow [Events](/guides/events) to read the related prompts, tool inputs, Rule
checks and results. Stats counts recorded tool attempts, not every message or
task your agent worked on. For current enforcement health, use `synkro status`.
For charges, use [Billing and usage](/guides/billing); for a cost projection,
use [Estimate your cost](/guides/estimate).

## No activity yet?

Check the account and organization with `synkro whoami`, then run
`synkro status`. Try a wider date range and remove the project or harness filter.
To record your first governed action, follow [Verify a decision](/onboarding/verify-events).