Caricamento in corso...
Caricamento in corso...
Last synced: Today, 22:00
Technical reference for the OpenClaw framework. Real-time synchronization with the official documentation engine.
Use this file to discover all available pages before exploring further.
qa-channeldm:<user>channel:<room>group:<room>thread:<room>/<thread>channel:group:.artifacts/qa-e2e/json{ "channels": { "qa-channel": { "baseUrl": "http://127.0.0.1:43123", "botUserId": "openclaw", "botDisplayName": "OpenClaw QA", "allowFrom": ["*"], "pollTimeoutMs": 1000 } } }
Account keys:
enablednamebaseUrlbotUserIdbotDisplayNamepollTimeoutMsallowFrom"*"defaultToactions.messagesactions.reactionsactions.searchactions.threadsMulti-account keys at the top level:
accountsdefaultAccountHost-side self-check (writes a Markdown report under
.artifacts/qa-e2e/bashpnpm qa:e2e
This routes through
qa-labqa-channelFull repo-backed scenario suite:
bashpnpm openclaw qa suite
Runs scenarios in parallel against the QA gateway lane. See QA overview for scenarios, profiles, and provider modes.
Docker-backed QA site (gateway + QA Lab debugger UI in one stack):
bashpnpm qa:lab:up
Builds the QA site, starts the Docker-backed gateway + QA Lab stack, and prints the QA Lab URL. From there you can pick scenarios, choose the model lane, launch individual runs, and watch results live. The QA Lab debugger is separate from the shipped Control UI bundle.
© 2024 TaskFlow Mirror
Powered by TaskFlow Sync Engine