Synopsis
Description
operator status prints a summary of the current Operator installation without starting the agent or the gateway. Use it to verify that your configuration file exists, your workspace is set up, and the correct provider keys or OAuth credentials are in place before running operator agent or operator gateway.
The output includes:
- Operator version and build information
- Config file path and whether it exists
- Workspace path and whether it exists
- Active default model name
- Each supported provider — whether an API key is configured
- OAuth/token sessions from
~/.operator/auth.json(if any)
Provider key detection
Thestatus command checks whether each provider entry has an API key or API base set in config.json. It does not make network requests or validate the key — it only checks that the field is non-empty.
Options
operator status accepts no flags.
Examples
Check status with a fully configured installation:operator onboard to create the config file.
operator version
Theoperator version command (alias: v) prints version and build information and then exits. It does not load the config file.
operator status includes this same version information at the top of its output, so you can use either command to check the installed version.
Providers checked
The following providers are checked for configured credentials:| Provider | What is checked |
|---|---|
| OpenRouter | providers.openrouter.api_key |
| Anthropic | providers.anthropic.api_key |
| OpenAI | providers.openai.api_key |
| Gemini | providers.gemini.api_key |
| Zhipu | providers.zhipu.api_key |
| Qwen | providers.qwen.api_key |
| Groq | providers.groq.api_key |
| Moonshot | providers.moonshot.api_key |
| DeepSeek | providers.deepseek.api_key |
| VolcEngine | providers.volcengine.api_key |
| Nvidia | providers.nvidia.api_key |
| vLLM / Local | providers.vllm.api_base |
| Ollama | providers.ollama.api_base |
The
model_list array is the recommended way to configure providers. The legacy providers block is still checked by operator status for backward compatibility, but new installations should use model_list exclusively.operator migrate
operator migrate migrates configuration and workspace files from a previous installation (such as OpenClaw) to Operator OS.
Source to migrate from. Currently supports
openclaw.Show what would be migrated without making any changes.
Re-sync workspace files from the source. Use this to pull in new files added after a previous migration.
Only migrate the configuration file; skip workspace files.
Only migrate workspace files; skip the configuration file.
Skip confirmation prompts.
Override the source home directory. Defaults to
~/.openclaw.Override the target home directory. Defaults to
~/.operator.Related commands
operator onboard— create the config file if it does not existoperator auth status— detailed view of OAuth/token credential state per provideroperator gateway— start the gateway once status confirms config is correctoperator agent— run the agent interactively