ae9f779e5f
Replaced 84 typography characters (curly quotes, apostrophes, em/en dashes, non-breaking hyphens) with ASCII equivalents per docs/CLAUDE.md heading and content hygiene rules. - docs/gateway/tools-invoke-http-api.md: 14 chars; removed the duplicate '# Tools Invoke (HTTP)' H1 (Mintlify renders title from frontmatter; the in-body H1 with parens produced a brittle anchor). - docs/tools/browser-control.md: 14 chars - docs/security/formal-verification.md: 14 chars - docs/gateway/configuration-reference.md: 14 chars - docs/concepts/agent.md: 14 chars - docs/channels/qa-channel.md: 14 chars
3.2 KiB
summary, title, read_when
| summary | title | read_when | |||
|---|---|---|---|---|---|
| Synthetic Slack-class channel plugin for deterministic OpenClaw QA scenarios | QA channel |
|
qa-channel is a bundled synthetic message transport for automated OpenClaw QA. It is not a production channel - it exists to exercise the same channel plugin boundary used by real transports while keeping state deterministic and fully inspectable.
What it does
- Slack-class target grammar:
dm:<user>channel:<room>group:<room>thread:<room>/<thread>
- Shared
channel:andgroup:conversations are surfaced to agents as group/channel room turns, so they exercise the same visible-reply and message-tool routing policy used by Discord, Slack, Telegram, and similar transports. - HTTP-backed synthetic bus for inbound message injection, outbound transcript capture, thread creation, reactions, edits, deletes, and search/read actions.
- Host-side self-check runner that writes a Markdown report to
.artifacts/qa-e2e/.
Config
{
"channels": {
"qa-channel": {
"baseUrl": "http://127.0.0.1:43123",
"botUserId": "openclaw",
"botDisplayName": "OpenClaw QA",
"allowFrom": ["*"],
"pollTimeoutMs": 1000
}
}
}
Account keys:
enabled- master toggle for this account.name- optional display label.baseUrl- synthetic bus URL.botUserId- Matrix-style bot user id used in target grammar.botDisplayName- display name for outbound messages.pollTimeoutMs- long-poll wait window. Integer between 100 and 30000.allowFrom- sender allowlist (user ids or"*").defaultTo- fallback target when none is supplied.actions.messages/actions.reactions/actions.search/actions.threads- per-action tool gating.
Multi-account keys at the top level:
accounts- record of named per-account overrides keyed by account id.defaultAccount- preferred account id when multiple are configured.
Runners
Host-side self-check (writes a Markdown report under .artifacts/qa-e2e/):
pnpm qa:e2e
This routes through qa-lab, starts the in-repo QA bus, boots the bundled qa-channel runtime slice, and runs a deterministic self-check.
Full repo-backed scenario suite:
pnpm 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):
pnpm 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.
Related
- QA overview - overall stack, transport adapters, scenario authoring
- Matrix QA - example live-transport runner that drives a real channel
- Pairing
- Groups
- Channels overview