Skip to content

[Bug]: [reopen #82344] Regression after upgrading from 2026.5.7 → 2026.5.18: embedded runtime detected as third-party harness while direct Claude CLI still works #84222

@FreeWind6

Description

@FreeWind6

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

I've already started the task #82344 and it is marked as completed. But in fact, after upgrading from version 2026.5.7 to version 2026.5.18, the error was repeated.

After upgrading OpenClaw from 2026.5.7 to 2026.5.18, Telegram and Dashboard/UI integrations started failing, while direct CLI usage (openclaw from terminal) continued to work normally with the same Claude CLI auth/session.

Downgrading back to 2026.5.7 restores functionality.

This suggests the issue is not with Anthropic account/auth itself, but with how newer OpenClaw versions handle Claude CLI integration in gateway/UI/Telegram runtime paths.

The failure appears specifically in gateway-mediated interactions, not in direct terminal execution.

Steps to reproduce

  1. Install and configure OpenClaw 2026.5.7

  2. Configure Claude CLI provider according to docs:

    • anthropic:claude-cli
    • OAuth login completed
  3. Verify:

    • Telegram works
    • Dashboard/UI works
    • Direct CLI works
  4. Upgrade OpenClaw to 2026.5.18

  5. Restart gateway/service

  6. Try:

    • sending Telegram message
    • using Dashboard/UI chat
  7. Observe failures/timeouts/errors

  8. Direct CLI usage still works:

    openclaw
  9. Downgrade back to 2026.5.7

  10. Restore previous config/backup

  11. Telegram and Dashboard start working again

Expected behavior

After upgrading from 2026.5.7 to 2026.5.18:

  • Existing Claude CLI auth should continue working
  • Telegram integration should continue responding
  • Dashboard/UI chat should continue responding
  • Gateway should start normally without requiring downgrade flags
  • Behavior should remain consistent with direct CLI execution

Actual behavior

After upgrade to 2026.5.18:

Telegram stops responding
Dashboard/UI becomes unusable
Gateway/runtime exhibits failures
Direct CLI execution still works normally with the same auth/session
Error in Telegram: ⚠️ API provider returned a billing error — your API key has run out of credits or has an insufficient balance. Check your provider's billing dashboard and top up or switch to a different API key.
Error in Logs: LLM request rejected:
Third-party apps now draw from your extra usage, not your plan limits.
Add more at claude.ai/settings/usage and keep going.

OpenClaw version

2026.5.18

Operating system

Ubuntu 26.04 LTS

Install method

npm

Model

anthropic/opus-4.7

Provider / routing chain

openclaw cli

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Metadata

Metadata

Assignees

Labels

P1High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingclawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.impact:auth-providerAuth, provider routing, model choice, or SecretRef resolution may break.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.regressionBehavior that previously worked and now fails

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions