ODS V3 Pre-Release: Public testing and refinement ahead of the official V3 launch. Turn your PC, Mac, or Linux box into a private AI server.
ODS — Post-Install Checklist
Run these checks after installation to confirm everything is working.
1. Overall health
ods status
Shows container status, service health checks, and GPU metrics in one view. All enabled services should report healthy. If any show as not responding, check the logs (step 6 below).
2. LLM response test
ods chat "Hello, are you working?"
You should receive a text response within a few seconds. If you see an error, check ods logs llm.
3. Web interface
Open your browser and navigate to the address shown at the end of installation (default: http://localhost:3000). The Open WebUI chat interface should load and let you send a message.
If the installer selected Portal, confirm the default model is portal/default,
send a real message, then open http://localhost:3001/pixel and send another
message through the dedicated Dashboard app. Ask Portal to check ODS status and
confirm it uses pixel_ods_status without exposing credentials or internal
paths. Also check the private path:
systemctl is-active openclaw-gateway.service pixel-ingress.service
sudo -u "$USER" curl --unix-socket /run/ods-pixel/pixel-ingress.sock \
http://localhost/health
docker inspect --format '{{.State.Health.Status}}' ods-pixel-edge
Expected results are two active lines, {"status":"ok"}, and healthy.
See PIXEL.md for rollback and the full qualification gate.
4. GPU verification
NVIDIA — GPU utilisation, VRAM, and temperature appear automatically in ods status.
AMD:
ods gpu status
Apple Silicon — GPU is used automatically; no separate check needed.
5. Check enabled services
ods list
Core services (llama-server, open-webui, dashboard) should be shown as running. Optional services selected during install should also appear.
6. Diagnose a failing service
ods logs <service> # e.g. ods logs llm
Replace <service> with the name from ods list. Common aliases: llm for llama-server, stt for Whisper, tts for Kokoro.
If a service fails its health check after reviewing logs, see TROUBLESHOOTING.md.