OpenClaw网关

Quickstart

For a real local gateway from source:

export MODEL_PROVIDER_KEY="sk-..."
dotnet run --project src/OpenClaw.Cli -c Release -- start

When the gateway finishes startup it now prints explicit phase markers, a final OpenClaw gateway ready. block, the localhost URLs, Ctrl-C to stop, and any non-fatal startup notices under Started with notices:. Then open:

The root URL redirects to /chat. For the full first-run walkthrough (including the "First 10 Minutes" runbook and debugging flow), see docs/QUICKSTART.md. For the project shape and repository map before changing code, see docs/GETTING_STARTED.md.

If you want a direct gateway fallback instead of the full CLI onboarding flow, run:

dotnet run --project src/OpenClaw.Gateway -c Release -- --quickstart

--quickstart is interactive-only. It applies a minimal loopback-local profile for the current process, prompts for missing provider inputs, retries on the common first-run failures, and after a successful start can save the working setup to ~/.openclaw/config/openclaw.settings.json.

If the CLI is already on your PATH, the same guided entrypoints are:

openclaw start
openclaw setup
openclaw setup launch --config ~/.openclaw/config/openclaw.settings.json
openclaw setup service --config ~/.openclaw/config/openclaw.settings.json --platform all
openclaw setup status --config ~/.openclaw/config/openclaw.settings.json
openclaw upgrade check --config ~/.openclaw/config/openclaw.settings.json
openclaw upgrade rollback --config ~/.openclaw/config/openclaw.settings.json --offline

Useful follow-up commands and surfaces:

openclaw models presets
openclaw models packages
openclaw models install gemma-4-e4b --accept-license --path ~/Downloads/gemma-4-E4B-it-Q4_K_M.gguf --mmproj-path ~/Downloads/mmproj-gemma-4-E4B-it-Q8_0.gguf
openclaw models doctor
openclaw maintenance scan --config ~/.openclaw/config/openclaw.settings.json
openclaw maintenance fix --config ~/.openclaw/config/openclaw.settings.json --dry-run
openclaw skills inspect ./skills/my-skill
openclaw compatibility catalog
openclaw insights
openclaw admin trajectory export --anonymize --output ./trajectory.jsonl
openclaw upgrade check --config ~/.openclaw/config/openclaw.settings.json --offline
openclaw upgrade rollback --config ~/.openclaw/config/openclaw.settings.json --offline
openclaw migrate upstream --source ./upstream-agent --target-config ~/.openclaw/config/openclaw.settings.json

• Skill inventory: /admin/skills
• Maintenance report: /admin/maintenance
• Observability summary: /admin/observability/summary
• Operator insights: /admin/insights
• Audit export: /admin/audit/export
• Trajectory export: /admin/trajectory/export
• Compatibility matrix: docs/COMPATIBILITY.md

For local Ollama setups, prefer the native root endpoint and an explicit preset:

openclaw setup --non-interactive --profile local --workspace ./workspace --provider ollama --model llama3.2 --model-preset ollama-general

OpenClaw.NET now treats Ollama as a first-class native provider at http://127.0.0.1:11434. Older /v1 endpoints still work for one compatibility cycle, but openclaw models doctor will flag them so you can migrate cleanly.

For OpenClaw-managed local inference, use provider embedded with an installable package. Gemma 4 is now the main embedded local model path:

openclaw models packages
openclaw models install gemma-4-e4b \
  --accept-license \
  --path ~/Downloads/gemma-4-E4B-it-Q4_K_M.gguf \
  --mmproj-path ~/Downloads/mmproj-gemma-4-E4B-it-Q8_0.gguf
openclaw setup --provider embedded --model-preset embedded-gemma-4-e4b --model gemma-4-e4b
openclaw models status gemma-4-e4b

The package catalog includes Gemma 4 E2B, E4B, 31B, and 26B-A4B GGUF entries, plus the experimental Gemma 4 E2B LiteRT-LM package for adapter work. The older gemma-local-small-q4 Gemma 3 package remains available for smaller machines.

Embedded video support is frame-based: OpenClaw samples local video/* inputs into ordered image frames before calling the local sidecar, and Gemma 4 GGUF packages include the multimodal projector file needed for image-frame inputs. LiteRT-LM packages are experimental and require an OpenClaw-compatible adapter binary; see docs/LOCAL_MODELS.md.

Breaking change: browser admin usage is account/session-first. Use named operator accounts for /admin, and use operator account tokens for Companion, CLI, API, and websocket clients.