CLI command reference

The CLI command reference lists commands and flags. Check the help for the version installed on your machine before using a command.

Identify the installed contract

unlimgpt --version
unlimgpt --help

Run these locally before copying a command from another machine or a newer guide. --version identifies the executable, and root help lists available commands without signing in. In published CLI 0.1.2, --help works at the root but not for subcommands. Use the syntax documented for your installed release; if it differs, follow the installation guide rather than guessing flags.

Compare unlimgpt --version with npm view @unlimgpt/cli version and find the operation in unlimgpt --help. If your installed version does not support it, use the browser key screen. Do not substitute a similar-looking flag from another CLI.

Choose the right guide

• Use client configuration for a supported editor or AI client. It explains the plan, verification and rollback of local configuration.
• Use CLI key management to create, rotate or revoke organization API keys. A key is distinct from the CLI's OAuth authorization.
• Use CLI security to understand the operating-system credential store and secret delivery.
• Use doctor troubleshooting only when setup or verification fails; it is not a prerequisite for the first API request.

CLI commands manage access and local client configuration. The configured client calls the public API directly; the CLI is not an inference proxy. For an HTTP integration, use the first API request instead.

Use login and whoami --json to check CLI authorization and the organization ID; use models to test an already stored API key without generating output. configure changes local client setup, while doctor investigates a failed setup. A paid doctor probe exists only behind explicit --probe confirmation. The CLI can return non-zero even after a partial key or configuration change, so inspect its reported result and receipts before retrying. For machine-readable output, use a supported --json option instead of parsing human-facing text. In a doctor --json report, data.ok means no check failed; the outer ok only means a report was produced and does not confirm that the checks passed.

Report a mismatch

If the command reference and local help differ, record the version, command name and unexpected help text. Do not include an API key, token, password, environment dump or credential-store value. Check installation, then report the mismatch with those safe details.