Installing a coding agent does not always make its command available in every terminal window. A CLI may be missing from the current process environment, installed somewhere else, or available but not signed in. These failures can look similar when you are trying to start an AI coding task.

This guide was drafted with AI assistance and checked against Orke’s public setup documentation. BOMTOBE makes Orke. The sequence below is a troubleshooting reference, not a report of a measured support case or an Orke screen capture.

First, identify the failure. A command-not-found message points toward installation or PATH. A provider sign-in prompt means the CLI started, so investigate authentication instead.

Record the operating system, the exact error text, and the terminal or environment where it appeared. Note whether the terminal was open before installation and whether the command fails everywhere or only in one place.

Second, open a fresh terminal after installation. Processes that were already open may keep an old PATH, so an existing terminal may not see a change made by an installer.

Follow the provider’s current installation instructions for your operating system. Test whether the command starts in that fresh terminal before changing other settings. Orke’s AI setup guide recommends this same first check.

Third, confirm installation if a fresh terminal still cannot find the command. Check the provider’s current instructions for your operating system and user, and avoid copying commands from outdated posts.

An authentication prompt is different: it means the program started. Complete that CLI provider’s current sign-in instructions; do not treat missing credentials as a failed installation.

Orke’s setup guide describes account sign-in for Codex CLI and Claude Code, API key and model selection for NVIDIA, and authentication managed by OpenCode, Hermes, and Antigravity through their CLIs. These details can change, so check the provider’s own current instructions.

In Orke Settings, review AI accounts and choose the intended current account. Select the AI in a new session and make a small request. Orke documents that new AI tasks use the current account; ordinary terminal commands that do not call an AI service do not need one.

Fourth, compare the environment where the command works with the one where it fails. My PC, a container, and a remote machine can each have their own installed programs and sign-in state.

Orke documents that installing and signing in on My PC does not configure an isolated container. Install the CLI and sign in from the isolated terminal if that is where the AI task will run.

Fifth, restart Orke only if the PATH change happened while Orke was already open and its new terminal still cannot see the command. Save your work, restart the app, open a fresh terminal, and try again.

If the problem continues, record the operating system, CLI provider, exact error, when the terminal was opened, and the environment where you tried it. Remove private tokens or credentials before sharing the note.

Never paste an API key, password, or session token into a public article or support request. A useful troubleshooting record describes what you observed without exposing the secret that grants access.

Quick order: command missing in an old terminal — open a fresh one; still missing — verify the provider’s install steps; CLI asks to sign in — follow that provider’s authentication flow; works on My PC but not in a container — set it up in that container; PATH changed while Orke was open — save work, restart, and check again.

Read Orke’s current AI setup and accounts guide at https://orke.bomtobe.com/en/docs/orke/accounts/ and the isolated environments guide at https://orke.bomtobe.com/en/docs/orke/isolation/. Provider installation and sign-in requirements can change, so follow their current official instructions.