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

# Review autonomous usage

> See what Cogno's autonomous turns spent — tokens per day, per project, and per member — from Settings → Usage.

**Settings → Usage** shows what Cogno spent working on its own: the tokens its
autonomous turns used, day by day, and which projects and people they ran for.
Open it when you want to know where the work went, or before deciding whether a
project is worth leaving to run unattended.

## What is counted

Only **autonomous turns** — the ones Cogno starts from the queue on its own.

A turn you typed into the Composer is you working, not Cogno working unattended,
so it is left out. That keeps the number answering one question instead of two.

A turn whose executor reported nothing is not counted as zero; it is simply
absent. Claude Code and Codex both report token counts, so this is rare.

## Read the page

<Steps>
  <Step title="Open Settings → Usage">
    The page opens on **You** and **Last 7 days**.
  </Step>

  <Step title="Choose whose usage to see">
    **You** is your own machines. **Workspace** is everyone's, and only the
    workspace owner can open it.
  </Step>

  <Step title="Choose a period">
    **Last 7 days**, **Last 30 days** or **Last 90 days**. The bars widen with
    the span — a day each for a week or a month, a week each for ninety days —
    so the chart stays readable. The label under the chart says which.
  </Step>
</Steps>

The headline is the total tokens, followed by the number of turns behind it and
the split between input, cache read, cache write and output. The split matters:
a cached read costs a fraction of a fresh one, so two workspaces with the same
total can be spending very differently.

Below the chart, **By project** and **By member** rank where the work went. Long
lists are folded: the top eight are named and the rest arrive as a single row
saying how many are behind it.

## Cost

Claude Code reports a cost with each turn and the page shows it, described as a
**list price**. It is not an amount anyone was billed — a subscription plan
charges none of it.

Codex reports no price at all. A Codex-only period therefore shows tokens and no
cost, which is different from a cost of zero.

## Where the numbers come from

Each finished autonomous turn reports what it spent to Cogno as it ends, and the
figures are the executor's own — the same ones `claude` and `codex` count for
themselves. Nothing is estimated here.

Usage is kept indefinitely. The period control limits what one view asks for,
not how long the record lasts.

## Related

* [Machines](/docs/machines) — the computers that run autonomous turns
* [Agents](/docs/agents) — what Cogno does unattended
* [Billing](/docs/billing) — the plan and what it actually costs