Jeden/Docs

CLI command

jeden asks

Read everything Jeden asked of you, in every session, and what you answered.

Exact invocation#

Shell
jeden asks [list|show <ask-id>|answer <ask-id> --text "answer"] [--json]

Inputs and options#

  • No session selection: the register covers every session of this machine. --json returns the same values the RPC methods asks/list, asks/get and asks/answer return.

Output and state effect#

The register is operator-asks.json beside the session root (~/.jeden/operator-asks.json, or beside JEDEN_SESSION_ROOT). An ask enters it when an independent review blocks a task on something only you hold, or when the agent asks you a question with ask_user. The same thing asked again — by another task, in another session, in the same words or named by the review as the same ask — is recorded as another place it was asked, not as a new ask, so the stop message shows each ask once with how many times and since when it has been asked. Every model call that continues work, and every review, reads the register: a review that blocks a task on an ask that already holds your answer is refused unless a step of the task failed after the answer, and an ask_user question you already answered in the same workspace in the same words is answered from the register without asking you. When the register is first created, the asks already recorded on tasks of this machine's sessions are adopted into it, the same words in several sessions becoming one ask. A new ask a task waits on is also put to you through the program stado capabilities resolve operator-asks --consumer jeden names (Oko on Wisent's hosts: asks ask --from jeden --subject ask-&lt;ask-id&gt;), delivered on the channels you chose with oko contact and shown in Oko Desktop and Oko iOS; the ask's oko field keeps that ask's id and its deliveries, or the declared cause it was not asked there: the jeden.alternatives refusal of a host that names no operator-asks alternative, or jeden.completion.asks.oko (program-unstartable, program-refused with the command line, directory, exit status and what it said, answer-unreadable, ask-unnamed). An answer you give there is taken into the register when the waiting session next continues, exactly as if given with jeden asks answer; an alternative that cannot be read then stops the continuation with its cause (answer-missing when it says answered and carries no answer). Jeden works without it: the ask still waits here and jeden asks answer answers it.

Refusals and boundaries#

  • The command is read whole before the register, jeden.completion.asks.command, exit 2: an unknown option (option-unknown), --text without its answer (text-missing), an unknown action (action-unknown), show or answer without an ask id (id-missing), extra words (words-extra), answer without --text (answer-textless) and --text beside list or show (text-unused).
  • An unreadable or foreign register is refused, never treated as empty, jeden.completion.asks.register: register-unreadable, register-not-json (line and column), schema-other, time-not-stamp (naming the ask or occurrence), a directory that cannot be made (directory-uncreatable), a lock that cannot be opened or taken (lock-unopenable, lock-refused), revision-exhausted; adopting the sessions' asks the first time: root-unlistable, entry-unreadable, adopted-state-unreadable, adopted-state-not-json, adopted-task-orphaned and adopted-time-not-stamp, each naming the session's completion.json.
  • A command line of the wrong form (an unknown command or option, a missing, unexpected or invalid argument, a missing confirmation) prints the error and the usage and exits 2; a refusal that retrying unchanged can help (a dependency down or not answering, a rate limit) exits 69; any other refusal or failure exits 1. A refusal a functionality declares ends with fix: … and cause: &lt;operation&gt;.&lt;cause&gt;, and jeden errors show &lt;operation&gt; lists every cause of that functionality.