openclaw - 💡(How to fix) Fix 2026.5.12-beta.1: isRuntimeManagedAuthProvider missing from plugin SDK (LCM falls back to legacy auth)

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…

Root Cause

LCM 0.9.4 calls \params.deps.isRuntimeManagedAuthProvider?.(provider, providerApi)\ during plugin init to check if runtime.modelAuth is available.

I grepped the entire OpenClaw 2026.5.12-beta.1 dist/ directory:

  • \isRuntimeManagedAuthProvider\ → 0 matches
  • \4790e40\ (PR #41090 merge commit) → 0 matches

  • untimeManagedAuth\ → 0 matches

The function is never injected into plugin deps, so LCM always falls back to legacy auth-profiles (API key mode). This blocks ADC/OAuth2 paths for plugins.

RAW_BUFFERClick to expand / collapse

Environment

  • OpenClaw: 2026.5.12-beta.1 (1824464)
  • LCM: @martian-engineering/lossless-claw 0.9.4
  • OS: Windows 11

Symptom

LCM startup logs: \
[lcm] OpenClaw runtime.modelAuth is unavailable; using legacy auth-profiles fallback. Stock lossless-claw 0.2.7 expects OpenClaw plugin runtime support from PR #41090. OpenClaw 2026.3.8 and 2026.3.8-beta.1 do not include merge commit 4790e40. the first OpenClaw release after 2026.3.8 is required... \\

Root Cause

LCM 0.9.4 calls \params.deps.isRuntimeManagedAuthProvider?.(provider, providerApi)\ during plugin init to check if runtime.modelAuth is available.

I grepped the entire OpenClaw 2026.5.12-beta.1 dist/ directory:

  • \isRuntimeManagedAuthProvider\ → 0 matches
  • \4790e40\ (PR #41090 merge commit) → 0 matches

  • untimeManagedAuth\ → 0 matches

The function is never injected into plugin deps, so LCM always falls back to legacy auth-profiles (API key mode). This blocks ADC/OAuth2 paths for plugins.

Questions

  1. Is PR #41090 planned for a future release, or was it merged but not included in this build?
  2. What's the correct way for plugins to detect runtime.modelAuth availability in current releases?

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

openclaw - 💡(How to fix) Fix 2026.5.12-beta.1: isRuntimeManagedAuthProvider missing from plugin SDK (LCM falls back to legacy auth)