Command reference
oko frustration scan
Reads one session's operator turns for the moments he lost patience and records each: a turn Oko's model read as frustrated, or a demand already made earlier in the session. Reading a session twice duplicates nothing; `oko index sync` does the same for every session it rewrites.
Invocation#
oko frustration scan --session ID | --transcript PATH [--session ID] [--json]Inputs and options#
- --session names a session whose live transcript is on this machine; --transcript names a transcript file, with --session naming it when the file does not.
Output and state effect#
- Records the new moments and prints how many operator turns were read, how many moments were found and how many are still unanswered, the worst repetition, and the unexplained moments. A turn Oko's model has not read is measured by nobody, so after printing what it recorded the scan refuses until every turn has a reading.
Refusals and safe exits#
- `oko frustration scan requires --session <id> or --transcript <path>`; `frustration: session <id> has no live transcript on this machine`; `frustration: <session> has no operator turns to read`; `frustration: <n> of <total> operator turn(s) of <session> have no model reading, so whether they were frustrated is unknown: #<ordinal>, …` naming `oko tasks read`, which reads them, after the moments it did record are kept and printed; the shared database refusals of `oko database check`, because the model's readings are read from it.