-
-
Notifications
You must be signed in to change notification settings - Fork 69.3k
[Bug] LCM throws "No API key for provider: bailian" and falls back to truncation, despite main config having bailian API key #40902
Description
Bug type
Regression (worked before, now fails)
Summary
After installing lossless-claw plugin, the LCM module repeatedly logs errors about missing API key for bailian provider, even though the main OpenClaw configuration (openclaw.json) has a valid bailian API key configured under models.providers.bailian.
The plugin attempts to generate summaries but fails, falling back to truncation. This also seems to trigger service instability (webchat disconnected, service restart).
Steps to reproduce
Install lossless-claw plugin: openclaw plugins install @martian-engineering/lossless-claw
Keep lossless-claw enabled in plugins.entries
Have bailian provider configured in models.providers with valid API key
Restart gateway and monitor logs
Observe LCM errors
Expected behavior
LCM should inherit or respect the main OpenClaw configuration's API key for bailian, or provide a documented way to configure it separately.
Actual behavior
LCM logs the following errors repeatedly:[lcm] completeSimple error: No API key for provider: bailian
[lcm] empty normalized summary on first attempt; provider=bailian; model=MiniMax-M2.5; ... retrying with conservative settings
[lcm] completeSimple error: No API key for provider: bailian
[lcm] retry also returned empty summary; ... falling back to truncation
[lcm] all extraction attempts exhausted; provider=bailian; model=MiniMax-M2.5; source=fallb
OpenClaw version
OpenClaw version: 2026.3.8
Operating system
OS: macOS (M4 Mac mini)
Install method
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response