oko model-service set

Invocation#

oko model-service set --origin URL --model MODEL < api-key | oko model-service set --none

Inputs and options#

• --origin, HTTPS or loopback HTTP with no user, query or fragment; --model; the API key on standard input, kept owner-only beside the choice and never printed.
• --none: no model. `oko tasks verify` then judges each due task from the attestation its report names (`oko tasks evidence TASK --by SESSION --report FILE`): every claim Oko declares confirmed and explained in at least the operator's stated number of words, and `next_steps` and `harsh_senior_review_findings` present and empty. A task whose report names no attestation, an unreadable one, or one that falls short is judged not done with each reason under `missing`; the verdict's `by` is `the task's attestation (no model declared)`, and no judge is probed. Every other model call (`brama complete`, `oko gateway send --prompt`, the reading) is refused with `no model is declared on this machine (<path>); oko model-service clear returns Oko to Brama`.

Output and state effect#

• Writes the declaration and prints the choice that stands. Desktop's Save provider and No model use the same operations over the resident API (`set`, `set_none`) after confirmation. Probe a declared service separately with `oko tasks judge --probe`.

Refusals and safe exits#

• `oko model-service set requires --origin <text>`, `… requires --model <text>`, `--origin must be HTTPS, or HTTP on loopback, with no user, query or fragment: <origin>`, `the service's API key is empty; the CLI reads it from standard input` (exit 2). `tests/no-model/model_service.rs` drives set --none, show, a refused model call and clear through the built binary.

CLI reference#

• View the complete oko command tree