Command reference
oko stats snapshot
The numbers Oko Desktop's activity screen shows: tokens used (input, output and cache writes; cache reads are left out), operator prompts and frustrated prompts over the last day, the last week and all time, the agents and projects the frustration came from, and the conversations touched in the last day.
Invocation#
oko stats snapshot [--root DIR ...]Inputs and options#
- --root, repeatable: transcript roots to read; Transcript Lake's Oko export when none is named. Every runtime's format is read with oko's shared decoder.
Output and state effect#
- Prints the snapshot as JSON. A prompt counts as frustrated when Oko's model read it so (`oko tasks read`); prompts not read yet are counted apart; goals are not measured and the snapshot says so.
- The closure rate beside the arrival rate, over the same three windows: defectsRecorded, defectsRepaired and defectsClosed (24h, 7d, All; byMember is by product, from the register's found_at, repaired_at and fixed_at) and tasksDone (byMember is who judged: a session, the operator, or `release <product> <version>` for the release's own verdicts), plus defectsAwaitingRelease {total, byProduct}, the open defects whose repair is recorded and waits for a published release. A register or verdict read that fails is named in closureRefused and the other measures stand. Oko Desktop's Activity screen shows them under Activity.
Refusals and safe exits#
- `oko stats takes snapshot or models; got <verb>` (exit 2); a root that cannot be read is reported.