Setup Wizard
On a fresh RBAC-enabled install, Fleet Command opens the Welcome Wizard: a guided 7-step checklist for bringing ClawNex online. The wizard reappears until each required item is completed or explicitly skipped and you click Get Started.
The 7-Step Checklist
Install ClawNex
Automatic. This step turns green as soon as the dashboard is running and responding.
Add an AI model provider
Click Open Configuration. The Model Providers card opens in the Configuration hub.
The installer quick-start choices are OpenRouter, Anthropic, OpenAI, NVIDIA NIM, or Skip. The dashboard provider catalog also supports local and OpenAI-compatible endpoints such as LM Studio and Ollama.
OpenClaw being connected is not enough by itself. Add at least one non-OpenClaw model provider, or intentionally skip this step if you are validating the dashboard before adding keys.
Enable Host Security
Click Verify Now to confirm that the bundled Host Security scanner is available. The scanner is bundled with ClawNex; this is not a separate download or package install.
If verification fails, click Open Updates panel and review the scanner status there.
Sync CVE database
Click Sync Now to pull the current CVE and GitHub advisory feeds from jgamblin/OpenClawCVEs. The count is dynamic because the feed changes over time.
This enables Security Posture correlation between shield detections, affected packages, and known advisories.
Sync model pricing
Click Sync Now to import LiteLLM model-pricing metadata for the pinned LiteLLM version. This powers dollar estimates in Token & Cost Intel and model-cost views.
Configure OpenClaw routing
Click Wire LiteLLM or Open Configuration. ClawNex writes a managed LiteLLM provider entry into OpenClaw routing and restarts the OpenClaw gateway when the local supervisor can do so.
Each provider shows a routing status:
- ROUTED — traffic flows through the LiteLLM proxy for scanning and telemetry
- DIRECT — traffic bypasses ClawNex
If openclaw.json has no routable local providers, the wizard explains what is missing. OAuth-only or cloud-only fleets can skip this step until routing is available.
Run first shield test
Click Open Shield Tests and run the validation suite. This confirms prompt-shield detections are firing before real agent traffic depends on the proxy.
Setup Complete
When every step is complete or intentionally skipped, the wizard header switches to a You’re all set state with a Get Started button. Clicking it dismisses the wizard and lands the operator in Mission Control.
Dismissal is persisted in config_defaults.wizard_dismissed, so Fleet Command stops opening the wizard on later visits.
Optional Next Steps
- Configuration > UI Preferences > Display Name — override the default hostname with a friendly label
- Configuration > Data Retention — set retention periods for your compliance requirements
- Keep shield mode in OBSERVE briefly if you want to inspect traffic before switching to enforced blocking