openclaw - 💡(How to fix) Fix [QA-lab] Live runtime-pair run does not stage OpenAI Codex auth into isolated QA agent [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#80412Fetched 2026-05-11 03:14:57
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
2
Timeline (top)
cross-referenced ×3commented ×1

Error Message

A minimal live runtime-pair probe launched successfully with provider mode live-frontier, but the Pi runtime cell failed with an auth error in the isolated QA agent store, and the Codex runtime cell timed out. The main OpenClaw install has an OpenAI Codex OAuth profile, but the temporary QA agent did not receive usable auth.

  • fail fast before launching paired runtime cells with an actionable auth-preflight error.

Code Example

OPENCLAW_QA_SUITE_PROGRESS=1 OPENCLAW_BUILD_PRIVATE_QA=1 OPENCLAW_ENABLE_PRIVATE_QA_CLI=1 pnpm openclaw qa suite \
  --provider-mode live-frontier \
  --runtime-pair pi,codex \
  --model openai-codex/gpt-5.5 \
  --alt-model openai-codex/gpt-5.5 \
  --scenario channel-chat-baseline \
  --concurrency 1 \
  --allow-failures \
  --output-dir .artifacts/qa-e2e/live-runtime-pair-channel-baseline

---

No API key found for provider "openai-codex". Auth store: /tmp/openclaw/.../state/agents/qa/agent/auth-profiles.json ... Configure auth for this agent (openclaw agents add <id>) or copy only portable static auth profiles from the main agentDir.
RAW_BUFFERClick to expand / collapse

Parent: #80171 Related PR: #80323 Related live proof tracker: #80397

Priority

High for completing live-frontier proof. This blocks the live token-efficiency lane from producing useful usage data in the current local setup.

What happened

A minimal live runtime-pair probe launched successfully with provider mode live-frontier, but the Pi runtime cell failed with an auth error in the isolated QA agent store, and the Codex runtime cell timed out. The main OpenClaw install has an OpenAI Codex OAuth profile, but the temporary QA agent did not receive usable auth.

Repro

OPENCLAW_QA_SUITE_PROGRESS=1 OPENCLAW_BUILD_PRIVATE_QA=1 OPENCLAW_ENABLE_PRIVATE_QA_CLI=1 pnpm openclaw qa suite \
  --provider-mode live-frontier \
  --runtime-pair pi,codex \
  --model openai-codex/gpt-5.5 \
  --alt-model openai-codex/gpt-5.5 \
  --scenario channel-chat-baseline \
  --concurrency 1 \
  --allow-failures \
  --output-dir .artifacts/qa-e2e/live-runtime-pair-channel-baseline

Observed result

Suite completed as an artifact-producing failure:

  • Scenario: channel-chat-baseline
  • Drift: failure-mode
  • Pi cell: auth failure after ~20s, 0 tokens
  • Codex cell: timeout after ~140s, 0 tokens
  • Codex plugin state in both cells: codex.installed=false

Pi diagnostic excerpt:

No API key found for provider "openai-codex". Auth store: /tmp/openclaw/.../state/agents/qa/agent/auth-profiles.json ... Configure auth for this agent (openclaw agents add <id>) or copy only portable static auth profiles from the main agentDir.

Artifacts:

  • /Volumes/LEXAR/repos/openclaw-1/.artifacts/qa-e2e/live-runtime-pair-channel-baseline/qa-suite-report.md
  • /Volumes/LEXAR/repos/openclaw-1/.artifacts/qa-e2e/live-runtime-pair-channel-baseline/qa-suite-summary.json
  • /Volumes/LEXAR/repos/openclaw-1/.artifacts/qa-e2e/live-runtime-pair-channel-baseline/runtime-cells/channel-chat-baseline/pi/qa-suite-report.md
  • /Volumes/LEXAR/repos/openclaw-1/.artifacts/qa-e2e/live-runtime-pair-channel-baseline/runtime-cells/channel-chat-baseline/codex/qa-suite-report.md

Expected

For live runtime-pair proof, the isolated QA agent should either:

  • stage a usable OpenAI/OpenAI Codex credential/auth profile for the selected live model; or
  • fail fast before launching paired runtime cells with an actionable auth-preflight error.

The Codex runtime cell also should not spend the full scenario timeout if the required Codex runtime/plugin/auth setup is unavailable.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING