Oko
Oko/Docs

Command reference

oko agent harnesses

Lists every coding-agent harness Oko knows — the catalogue `oko agent run`, `oko sessions adopt` and the activity counts read — and reads each against this machine: whether its program is installed, whether Brama can route it and why not, whether `oko agent run` can start it, and which of its transcript directories exist. Transcript Lake reads the sessions of the same harnesses under the same ids. Catalogue-based Codex resumption uses `codex resume <session>` without bypassing hook trust; the harness keeps its own trust requirements.

Invocation#

Command
oko agent harnesses [--plain]

Inputs and options#

  • No input. The answer is JSON, one object per harness: id, display, executable, path (the installed program, or null), routable, refusal (the sentence `oko agent run` answers, or null), runnable, transcripts (each directory as path and present) and source (the documentation the entry was read from); --plain prints the same document for a person.

Output and state effect#

  • Reads the catalogue compiled into this build and looks for each program in ~/.local/bin, ~/.kimi-code/bin, /opt/homebrew/bin and /usr/local/bin; writes nothing.
  • Devin transcript locations follow its native directory selection: a nonempty XDG_DATA_HOME selects $XDG_DATA_HOME/devin/cli; an unset or empty value selects ~/.local/share/devin/cli. Both path and present describe that selected directory. A missing selected directory is reported absent; it does not select another store or make the harness routable.
  • Desktop's Model access → Coding harnesses section shows the same answer, read over the resident API's agent request {"action":"harnesses"}: each harness's program, the sentence saying why Brama cannot route it or the `oko agent run --harness ID` that runs it, and how many of its transcript directories exist.

Refusals and safe exits#

  • `oko agent harnesses does not take <flag>; it takes no flags` and `oko agent harnesses takes only flags; it was given <word>, which it would not read` (exit 2); `HOME is not set, so no harness can be looked for`.

CLI reference#