Oko
Oko/Docs

Command reference

oko asks history

Reads every request put to the signed-in person, oldest first, with what came of it and what it was like, so whoever asks next reads what the person answered before, in their own words, beside the requests they answered and the ones they left.

Invocation#

Command
oko asks history [--session <id>]

Inputs and options#

  • None: every ask of the signed-in person, whatever its standing.
  • --session <id> adds the requests that session wrote in chat, read as `oko asks pleas --session <id>` reads them, under `chat`.

Output and state effect#

  • Prints `{asks, summary, entries, at}`, and `chat` (the document `oko asks pleas` prints) with --session. Each entry: id, askedBy, subject, question, createdAt, standing (waiting, undelivered, expired, answered, withdrawn), the answer verbatim with answeredOn, answeredAt and answerSeconds, reachedOn (the channels that took it) and notReached ({channel, detail} of each that did not), case (null when the detail names no grant; else {complete, parts, missing, admits}, read back under the labels `oko asks ask --grant` writes, admits the number of exact commands listed), questionChars, detailChars, earlier (the older asks of the same product about the same subject, each {id, standing, answer}) and features {carriesWholeCase, admits, repeatsAnsweredAsk, repeatsAsk, reached}.
  • summary is `{feature: {value: {standing: {count, asks}}}}`: per value of each feature, the asks of each standing and how many — for example how many asks carrying the whole case were answered against those without it, or which requests repeated one already answered. Nothing judges an answer: the counts and the verbatim answers are the evidence. Reads the asks and their deliveries only.
  • The native API's asks domain answers the same document as action history (without --session's chat), and OkoKit decodes it as OkoAskHistory through OkoOperatorAsks.history(), for Oko Desktop and Oko iOS.

Refusals and safe exits#

  • `oko asks history does not take <flags>; it takes --session` and `oko asks history takes only flags; it was given <word>, which it would not read` (exit 2); `oko asks history requires --session <text>` when --session has no value; with --session, every refusal of `oko asks pleas`.
  • The shared database refusals of `oko database check` (no signed-in session, no organization).

CLI reference#