Usage
Use ./src/bin/okso --help to see all flags. The CLI walks through planning and tool execution with approvals by default.
Task-based walkthroughs
Run with approvals
-
Start with a prompted run so the plan requires confirmation before tools execute (default):
./src/bin/okso -- "inspect project layout and search notes" -
To auto-approve tool calls, pass
--yes(or--no-confirm) for a fully automated pass:./src/bin/okso --yes -- "save reminder" -
If your config sets
APPROVE_ALL=truebut you need prompts for a sensitive query, exportAPPROVE_ALL=falsefor that run:APPROVE_ALL=false ./src/bin/okso -- "draft meeting notes" -
Increase logging with
--verboseor silence informational logs with--quietwhen running unattended scripts.
Initialize config for a custom model
-
Generate a config file without executing any plan using the
initsubcommand. Set the model specs and branches you want via environment variables before runninginit:export PLANNER_MODEL_SPEC="bartowski/Qwen_Qwen3-8B-GGUF:Qwen_Qwen3-8B-Q4_K_M.gguf" export EXECUTOR_MODEL_SPEC="bartowski/Qwen_Qwen3-4B-GGUF:Qwen_Qwen3-4B-Q4_K_M.gguf" export SEARCH_REPHRASER_MODEL_SPEC="bartowski/Qwen_Qwen3-1.7B-GGUF:Qwen_Qwen3-1.7B-Q4_K_M.gguf" export PLANNER_MODEL_BRANCH=main export EXECUTOR_MODEL_BRANCH=main export SEARCH_REPHRASER_MODEL_BRANCH=main CONFIG_FILE="${XDG_CONFIG_HOME:-$HOME/.config}/okso/config.env" ./src/bin/okso init -
At runtime, override config values by exporting the same variable names that appear in
config.env:PLANNER_MODEL_SPEC=bartowski/Qwen_Qwen3-8B-GGUF:Qwen_Qwen3-8B-Q4_K_M.gguf \ EXECUTOR_MODEL_SPEC=bartowski/Qwen_Qwen3-4B-GGUF:Qwen_Qwen3-4B-Q4_K_M.gguf \ PLANNER_MODEL_BRANCH=main \ EXECUTOR_MODEL_BRANCH=main \ LLAMA_BIN=llama-completion \ ./src/bin/okso --yes -- "classify support tickets" -
To keep the run noninteractive while still respecting a new model, pair the overrides with
--yes.
Refer to configuration for available settings and tools for handler details.
Define and invoke workflows
Workflows let you bundle a sequence of tool calls behind a pseudo-tool named workflow_<name>. Create a JSON file in workflows/ and include the required metadata and steps.