obi CLI connects your machine to your Obi account and carries the Skill your assistant runs. In everyday use your assistant runs these commands for you; this reference is for when you want to run or script them yourself.
Help and version
--help prints every command and its options. capabilities lists, as JSON, the commands and options this installed version supports.
Global options
JSON output
With--json, every invocation prints exactly one envelope:
obi doctor --json on a Mac with the video tools installed prints:
credentialStorage is keychain, secret-service or file once this machine is signed in, and none before.
A failure has "ok": false and an error object instead of data:
mode says where the result came from: local (this machine only), product (your account on Obi’s servers) or test (a local synthetic server). nextAction is always the CLI’s own sentence, never text relayed from a server.
After a timeout or a conflict on a write, read the current state before retrying.
Exit codes
Credentials and local state
The CLI keeps your connection in the system credential store: the macOS Keychain, or the freedesktop Secret Service throughsecret-tool on Linux. On Windows, and on any machine without one, sign in with obi login --expect-email <email> --storage file to keep it in an owner-only file instead. The CLI never prints tokens.
Local state lives in:
Version 0.1.8 moves the folder and the stored connection an earlier version kept under its former name, on its first run.
Environment variables
The Skill follows the language of your conversation, whatever these variables say.