Oko/Docs

CLI reference#

Browse the complete command tree, including exact invocations, inputs, state effects, and source-grounded refusals.

Product#

Overview — What Oko owns, supported platforms, source setup, interfaces, operations, and support.
Sign in — Install Oko, request and verify an email code, select an explicit autonomous method, and diagnose the actual refusal in CLI or Desktop.
Release notes — Every published Oko release and the current unreleased changes.
Organization administration — Roles, permissions, invitations, membership, and ownership for Wisent organizations.

Release qualification — Real session, wait-register and task-graph journeys required before an Oko release.
PTY relay — Authentication, operation, and Stado deployment for Oko terminal sharing.
Defect register — Where a defect found in a Wisent product is recorded, why it is not a page in that product's documentation, and the commands that record and close one.
Frustration register — Every moment the operator lost patience: his words, how many times he had already asked, what the agent did to cause it, and the revision that removed the cause.
Contributions — The work a person's prompts produced that a verdict accepted, reported to Wisent's contribution ledger as credits for its author.
Person model — Oko's model of the operator as a person: how each of his messages reads as an instruction and a decision, how his decisions fared, what frustrates and relieves him, and what he said about himself.
Strategic feedback — How a teammate's Slack reply to Oko becomes a recorded strategic decision: one event per reply, its attempts, what a decision may change and the refusals.

Transcript intelligence — Evidence-locked facts read from session transcripts: source adoption and one-off repairs.
Model service and judge — Provider choice, model readiness, task verdict contracts and real judge qualification.
Database schema — Ownership, migration, review, and deployment boundaries for Oko’s hosted Supabase schema.

iOS companion — Architecture, trust boundaries, requirements, and local setup for the Oko mobile client.
Desktop interface — The operator decisions, ownership boundaries, state rules, and packaging contract behind Oko Desktop.
Desktop task ledger — Message ownership, task relations, batch qualification and completion checks through the native desktop and CLI.