Skip to main content
Every error the CLI prints carries a code and the next action to take. With --json, they are in error.code and error.nextAction; the exit code tells you the family. Still stuck? Write to support@hireobi.com with the command you ran and the error code. Never send a token or a credential file.

​
Installing

The CLI needs Node.js 22 or later. Check with node --version, upgrade Node.js, then install again.
obi skill install found a file or link at ~/.agents/skills/obi or ~/.claude/skills/obi that it did not create. It never replaces one. Move or remove that entry yourself, then run the command again.
Skills load when a chat starts. Run obi skill install, then open a new chat. obi skill path shows where the bundled Skill is.

​
Signing in

Run obi login --expect-email <your email>.
The connection waits for your approval in the browser. Open the address the CLI printed, check that the page shows the same code, approve, then run the same obi login command again: it resumes the same connection.
The CLI opens a browser only on macOS or Linux, in a terminal on a machine with a display; never on Windows, over SSH or in CI. Open the printed address yourself, on any device, and compare the code before you approve.
The connection was approved by another account than the one you expected, or denied in the browser. Nothing was stored. Run obi login again and approve it with your own account.
Verify your email from the message Obi sent, or finish the account setup in the browser, then run obi status.
The macOS Keychain or the Linux Secret Service is missing, locked or refused the operation, or you are on Windows, where the CLI uses none. Unlock it, or sign in with obi login --expect-email <your email> --storage file to keep the connection in a file only your user can read.
The local state directory or one of its files can be read by other users, is a link, or belongs to another user. Restrict the directory to your user (mode 700) and its files (mode 600). The state directory depends on your system.
Run obi logout, then obi login --expect-email <your email>.

​
Working with Obi

Only the account owner can do this, for example start the reading of your website or a purchase. Ask the owner.
A timeout does not prove the change failed. Read the current state first (obi status, obi business show, obi questions show or obi harness purchase status), then retry only if the change is not there. Obi does this for you in the chat.
The command asked Obi’s servers to read your website or prepare your questions, and on your account your assistant does that work. Ask Obi in your assistant: the Skill reads the work with obi harness show --stage business or --stage questions and saves the result with obi harness submit.
The review or the scan changed after the result was prepared. Obi reads the current work and prepares the result again.
The scan you asked for is not fully authorized for your plan’s coverage. Editing a question does not fix it. Ask Obi to show your coverage with obi harness coverage.

​
Network and updates

Check your network connection and try again later. A rate limit tells you how long to wait when the server says so.
The server refused the request with a reason this CLI version does not know. Retrying will not help: update the CLI with npm install --global @hireobi/cli, then try again.
The server answered in a form this CLI version does not know. Update the CLI with npm install --global @hireobi/cli, then try again.
A development variable is set: the error names it. OBI_ORIGIN exists for Obi development and only accepts a local address; a variable an older version read is refused. Unset it to reach your account.