Global flags
These flags are available on all commands:omni config
Manage CLI profiles. These commands don’t require authentication.omni config init
Interactively create a new configuration profile. Prompts for a profile name, API endpoint, and authentication method. See CLI authentication for more details about OAuth and API token authentication.- OAuth opens a browser-based login flow. Approving the verified Omni CLI application creates a user-scoped credential for the profile.
- API token stores the token in the profile. You can also set
OMNI_API_TOKENor pass--tokento override the profile token.
omni config login
Authenticate a profile with browser-based OAuth. If you don’t provide a profile name, the CLI uses the default profile.omni config logout
Clear OAuth tokens from a profile. If you don’t provide a profile name, the CLI uses the default profile.omni config show
Display the current configuration. Tokens are redacted in the output.omni config use
Switch the default profile.omni agent-help
Print a concise usage guide formatted for AI agents.API commands
Most of the commands in this section are auto-generated from the Omni OpenAPI spec. For the Omni CLI, this means:-
API tags become command groups. For example, the
documentsAPI tag corresponds to theomni documentscommand group. -
Path parameters become positional arguments, such as
documentIdin the following example: -
Query parameters become flags, such as
userIdin the following example: -
Request bodies are passed via
--bodyor stdin.
omni <group> --help to see all commands in a group or omni <group> <command> --help for command-specific argument and flag details.

