Oko
Oko/Docs

Command reference

oko sessions attention

Which live agent needs its supervisor now, ranked, each with the evidence for every sign it shows and the action that sign needs, so a supervisor acts on the agents that matter instead of reading every transcript tail.

Invocation#

Command
oko sessions attention [--socket PATH] [--json]

Inputs and options#

  • Every model policy pass (`oko sessions policy run`, and the Oko service on its cron) ranks the sessions it read from what it measured itself and keeps the ranking in attention.json in the Oko directory (OKO_ATTENTION moves it); this command prints the kept ranking and the time its pass made it.
  • The signs, in the order of need attention.json declares: wait past due (an open wait standing past the due moment its wait line carries), stalled call (its running call past every completed call of its shape), looping (its last answers repeat one another, or since its last commit or claim it repeated one call more times than any session did before committing), blocker that is not one (raised or refused for more than once in the progress window of the pass), stopped with open work (its turn ended while Oko holds open work for it), prose to the operator (that turn ended on its own words rather than on a provider failure) and no commit in its norm (behind the measured repair norm of `oko work progress`).
  • Agents are ordered by their most needful sign, then by how many signs they show, then by how long they have been silent; an agent with no sign is not listed.

Output and state effect#

  • For a person: one line per agent (session, role, model, state, seconds silent), then each sign with its evidence and an `action:` line. --json prints {at, examined, agents: [{session, title, role, supervisor, model, state, silentSeconds, signs: [{sign, evidence, action}]}], unread, activitySince, activityUnread}.
  • The continuation typed to a supervisor whose turn ends with open work, or whose answers repeat, opens with this ranking, and the supervisor handover names the command first. The native API sessions domain answers it as `attention`, OkoKit reads it as `OkoSessions.Attention`, and Oko Desktop → Work → Sessions → Agent sessions shows it above Executor supervision with the evidence and action of each sign.
  • For example, an executor whose `stado` call stands past the longest `stado` wait measured on its machine, and whose turn then ended with two open items, is listed first with both signs, the due moment and measurement of the wait, and the actions to interrupt it and continue it.

Refusals and safe exits#

  • “no model policy pass has ranked the agents yet (<file> does not exist); `oko sessions policy run` runs one”; “<file> is not an attention ranking: <cause>”; “<file> cannot be read: <cause>”; “the kept attention ranking has no agents list: <ranking>”.
  • A sign the declaration does not name is not ranked and is said under unread (“attention.json declares no sign …”); a transcript the activity window could not read, or an activity window the pass could not measure, is named under activityUnread with its cause, never counted as no sign.

CLI reference#