From 655cfb477af48e62e7f60e7bccdb70a3d67073c4 Mon Sep 17 00:00:00 2001
From: Shakker <shakkerdroid@gmail.com>
Date: Thu, 9 Apr 2026 00:34:20 +0100
Subject: [PATCH] docs: clarify multipass live auth support

---
 docs/concepts/qa-e2e-automation.md | 11 +++++++----
 docs/help/testing.md               |  7 ++++++-
 2 files changed, 13 insertions(+), 5 deletions(-)

diff --git a/docs/concepts/qa-e2e-automation.md b/docs/concepts/qa-e2e-automation.md
index f36ae7c8ee6..04a1bac9311 100644
--- a/docs/concepts/qa-e2e-automation.md
+++ b/docs/concepts/qa-e2e-automation.md
@@ -59,10 +59,13 @@ pnpm openclaw qa suite --runner multipass --scenario channel-chat-baseline
 ```
 
 This boots a fresh Multipass guest, installs dependencies, builds OpenClaw
-inside the guest, runs `qa suite` on the mock-openai lane, then copies the
-normal QA report and summary back into `.artifacts/qa-e2e/...` on the host.
-It reuses the same scenario-selection behavior as `qa suite` on the host and
-only changes where that suite runs.
+inside the guest, runs `qa suite`, then copies the normal QA report and
+summary back into `.artifacts/qa-e2e/...` on the host.
+It reuses the same scenario-selection behavior as `qa suite` on the host.
+Live runs forward the supported QA auth inputs that are practical for the
+guest: env-based provider keys, the QA live provider config path, and
+`CODEX_HOME` when present. Keep `--output-dir` under the repo root so the guest
+can write back through the mounted workspace.
 
 ## Repo-backed seeds
 
diff --git a/docs/help/testing.md b/docs/help/testing.md
index f09606f509a..3e2a5dd2658 100644
--- a/docs/help/testing.md
+++ b/docs/help/testing.md
@@ -51,7 +51,12 @@ These commands sit beside the main test suites when you need QA-lab realism:
 - `pnpm openclaw qa suite --runner multipass`
   - Runs the same QA suite inside a disposable Multipass Linux VM.
   - Keeps the same scenario-selection behavior as `qa suite` on the host.
-  - Reuses the same provider/model selection flags as `qa suite`; the runner only changes where the suite executes.
+  - Reuses the same provider/model selection flags as `qa suite`.
+  - Live runs forward the supported QA auth inputs that are practical for the guest:
+    env-based provider keys, the QA live provider config path, and `CODEX_HOME`
+    when present.
+  - Output dirs must stay under the repo root so the guest can write back through
+    the mounted workspace.
   - Writes the normal QA report + summary plus Multipass logs under
     `.artifacts/qa-e2e/...`.
 - `pnpm qa:lab:up`