Command reference
oko telemetry work
How a member worked, day by day, from the transcripts written in the window: Transcript Lake's Oko export, or the trees each --root names. Sessions Oko's own automations opened are left out of the working hours. With --by provider, each member's prompts counted by the harness that took them, under its display name in Oko's harness catalogue (the name `oko agent harnesses` and `oko stats` show), or its runtime id when the catalogue does not know it.
Invocation#
oko telemetry work --days N [--limit N] [--root DIR ...] | oko telemetry work --by provider (--from DAY | --all) [--to DAY] [--json] [--limit N] [--member 'NAME|TIMEZONE|ROOT' ...]Inputs and options#
- --days, required: the window; --limit, a backstop on files read; --root, repeatable.
- --by provider takes --from (yyyy-MM-dd) or --all; --to defaults to today; --member repeats; --json prints the counts as `{members: [{member, zone, from, to, counts}]}`.
Output and state effect#
- Reads only; prints `{files, days}`, or with --by provider one `label<TAB>count` line per harness the member's transcripts were written by, most prompts first.
Refusals and safe exits#
- `oko telemetry work requires --days <whole number>`, and a --days that is not a positive whole number; a non-numeric --limit (exit 2); `oko telemetry work --by takes provider; got <value>`; `oko telemetry work --by provider takes --from YYYY-MM-DD, or --all`; `invalid --from: <text>; days are yyyy-MM-dd` and the same for --to; `invalid --timezone: <zone>`.