You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/concepts/qa-e2e-automation.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -787,9 +787,10 @@ the source of truth for one test run and should define:
787
787
- docs and code refs
788
788
- optional plugin requirements
789
789
- optional gateway config patch
790
-
- the executable `qa-flow`
790
+
- an executable `qa-flow` block for flow scenarios, or `execution.kind`/`execution.path`
791
+
for Vitest and Playwright scenarios
791
792
792
-
The reusable runtime surface that backs `qa-flow` is allowed to stay generic
793
+
The reusable runtime surface that backs `qa-flow`blocks is allowed to stay generic
793
794
and cross-cutting. For example, markdown scenarios can combine transport-side
794
795
helpers with browser-side helpers that drive the embedded Control UI through the
795
796
Gateway `browser.request` seam without adding a special-case runner.
@@ -915,6 +916,7 @@ The report should answer:
915
916
For the inventory of available scenarios - useful when sizing follow-up work or wiring a new transport - run `pnpm openclaw qa coverage` (add `--json` for machine-readable output).
916
917
When choosing focused proof for a touched behavior or file path, run `pnpm openclaw qa coverage --match <query>`.
917
918
The match report searches scenario metadata, docs refs, code refs, coverage IDs, plugins, and provider requirements, then prints matching `qa suite --scenario ...` targets.
919
+
Every `qa suite` scenario execution writes a `qa-evidence.json` artifact. Flow scenarios also write `qa-suite-summary.json` for existing suite/report tooling; scenarios that declare `execution.kind: vitest` or `execution.kind: playwright` run the matching test path and write `qa-vitest-report.md` or `qa-playwright-report.md` plus per-scenario logs.
918
920
Treat it as a discovery aid, not a gate replacement; the selected scenario still needs the right provider mode, live transport, Multipass, Testbox, or release lane for the behavior under test.
919
921
920
922
For character and style checks, run the same scenario across multiple live model
Copy file name to clipboardExpand all lines: docs/gateway/health.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,21 @@ health commands above for live connectivity checks.
42
42
-`channels.<provider>.accounts.<accountId>.healthMonitor.enabled`: multi-account override that wins over the channel-level setting.
43
43
- These per-channel overrides apply to the built-in channel monitors that expose them today: Discord, Google Chat, iMessage, Microsoft Teams, Signal, Slack, Telegram, and WhatsApp.
44
44
45
+
## Uptime monitoring
46
+
47
+
External uptime monitoring services should use the dedicated `/health` endpoint, not `/v1/chat/completions`.
48
+
49
+
-**DO use:**`GET /health` — instant response, no session created, no LLM call, returns `{"ok":true,"status":"live"}`
50
+
-**DON'T use:**`/v1/chat/completions` for health checks — each request creates a full agent session with skill snapshot, context assembly, and LLM calls
51
+
52
+
When no `x-openclaw-session-key` header or `user` field is provided, `/v1/chat/completions` generates a new random session for each request. Monitoring services that ping every 15 minutes create ~96 sessions/day, each consuming 4–22KB. Over time this causes session store bloat and can lead to context window overflow.
53
+
54
+
### Monitoring service setup examples
55
+
56
+
-**BetterStack:** Set health check URL to `https://<your-gateway-host>:<port>/health`
57
+
-**UptimeRobot:** Add a new HTTP monitor with URL `https://<your-gateway-host>:<port>/health`
58
+
-**Generic:** Any HTTP GET to `/health` returns 200 with `{"ok":true}` when the gateway is healthy
59
+
45
60
## When something fails
46
61
47
62
-`logged out` or status 409–515 → relink with `openclaw channels logout` then `openclaw channels login`.
Copy file name to clipboardExpand all lines: docs/platforms/windows.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,13 @@ most Linux-compatible Gateway runtime.
18
18
Windows Hub is the native WinUI companion app for Windows 10 20H2+ and Windows 11. It installs without administrator privileges and is published with signed
19
19
x64 and ARM64 installers on OpenClaw releases.
20
20
21
-
Download the latest stable installer:
21
+
Download the latest stable installer from the [OpenClaw releases page](https://github.com/openclaw/openclaw/releases):
If a download link above returns a 404, visit the [releases page](https://github.com/openclaw/openclaw/releases) and look for the `OpenClawCompanion-Setup-*` assets on the latest release.
26
28
27
29
After install, launch **OpenClaw Companion** from the Start menu or the system
28
30
tray. The installer also adds shortcuts for Gateway Setup, Chat, Settings,
0 commit comments