Skip to content

yachiyo provider

Manages provider definitions from ~/.yachiyo/config.toml. API keys and Vertex private keys are stored in the encrypted, device-local provider credential vault. API keys are redacted as *** in all output.

Terminal window
yachiyo provider list

Every configured provider, keys redacted.

Terminal window
yachiyo provider show <id-or-name>

One provider in full, addressed by UUID or display name.

Terminal window
yachiyo provider update <id-or-name> [--payload '<json>']

Merges a JSON patch into an existing provider. Only the fields you supply change.

Terminal window
yachiyo provider update my-openai --payload '{"apiKey":"sk-..."}'
yachiyo provider update my-openai --payload '{"baseUrl":"https://proxy.internal/v1"}'

Supplying an apiKey or Vertex private key writes it to this device’s encrypted vault. Provider credentials are not synced, so configure them separately on each device.

Terminal window
yachiyo provider set-default <id-or-name> [--model <model>]

Promotes the provider to default and sets the model new chats start with — updating both provider ordering and the defaultModel setting in one step. Without --model, it picks that provider’s first enabled model.

Terminal window
yachiyo provider set-default anthropic --model <model-name>
Terminal window
yachiyo provider models # locally enabled models
yachiyo provider models <id-or-name> # everything the provider's API offers

Without an argument you get a flat array of { provider, model } for every model you have enabled — the valid values for modelOverride fields in schedule payloads and essential presets.

With a provider argument it calls the provider’s API and lists what is actually available, which is how you discover model names worth enabling.