Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix doctor --fix does not auto-migrate invalid bailian compat.thinkingFormat enum values after upgrade [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#77803•Fetched 2026-05-06 06:21:10
View on GitHub
Comments
1
Participants
2
Timeline
2
Reactions
4
Author
JIRBOYJIRBOY
Participants
clawsweeper[bot]clawsweeper[bot]JIRBOYJIRBOY
Timeline (top)
commented ×1cross-referenced ×1

Error Message

After upgrading OpenClaw, all configured bailian models have an invalid compat.thinkingFormat value. openclaw doctor --fix does not automatically migrate these values to the new allowed enum, causing --fix to fail with a config validation error.

Error: Config validation failed: models.providers.bailian.models.0.compat.thinkingFormat: Invalid input ...

Root Cause

  • --fix proceeds with other fixes but ultimately fails with exit code 1:

    Error: Config validation failed: models.providers.bailian.models.0.compat.thinkingFormat: Invalid input ...

  • The invalid enum values are not corrected or reset to a default.
  • Because --fix fails, none of the other fixes persist either (see related issue about atomic failure).
RAW_BUFFERClick to expand / collapse

Bug Description

After upgrading OpenClaw, all configured bailian models have an invalid compat.thinkingFormat value. openclaw doctor --fix does not automatically migrate these values to the new allowed enum, causing --fix to fail with a config validation error.

Reproduction Steps

  1. Have a pre-upgrade config with bailian models configured (e.g. models.providers.bailian.models).
  2. Upgrade OpenClaw to a version where thinkingFormat only allows ["openai", "openrouter", "deepseek", "zai"].
  3. Run openclaw doctor — it reports:

    Invalid config: models.providers.bailian.models.0.compat.thinkingFormat: Invalid input (allowed: "openai", "openrouter", "deepseek", "zai") (and the same for models 1, 2, 6, 7, 8 — 6 models total)

  4. Run openclaw doctor --fix.

Observed Behavior

  • --fix proceeds with other fixes but ultimately fails with exit code 1:

    Error: Config validation failed: models.providers.bailian.models.0.compat.thinkingFormat: Invalid input ...

  • The invalid enum values are not corrected or reset to a default.
  • Because --fix fails, none of the other fixes persist either (see related issue about atomic failure).

Expected Behavior

doctor --fix should detect invalid enum values in compat.thinkingFormat and either:

  • Reset them to a sensible default (e.g. "openai"), or
  • Prompt the user to choose from the allowed values, or
  • At minimum, remove the invalid field so the default applies.

This is a standard config-migration scenario that --fix is designed to handle.

Environment

  • OS: Windows 10 Education 10.0.19045
  • OpenClaw: just upgraded to latest

Additional Context

This affects 6 bailian models simultaneously, suggesting the old allowed values for thinkingFormat were broader and got narrowed in a recent release. Users with existing bailian configs will hit this on every upgrade.

extent analysis

TL;DR

Manually update the compat.thinkingFormat values for the affected bailian models to one of the allowed enum values ("openai", "openrouter", "deepseek", or "zai") to resolve the config validation error.

Guidance

  • Identify the 6 bailian models with invalid compat.thinkingFormat values and update their configurations to use a valid enum value.
  • Run openclaw doctor --fix again after manually updating the configurations to ensure the other fixes are applied successfully.
  • Consider resetting the invalid enum values to a sensible default (e.g., "openai") if no specific value is preferred.
  • Verify that the updated configurations pass validation by running openclaw doctor without the --fix flag.

Example

No code snippet is provided as the issue is related to configuration updates rather than code changes.

Notes

The issue is specific to the thinkingFormat enum values in the bailian model configurations, and the solution involves updating these values to conform to the new allowed enum. This may require manual intervention until the --fix command is updated to handle this scenario automatically.

Recommendation

Apply workaround: Manually update the compat.thinkingFormat values for the affected bailian models, as the --fix command does not currently handle this scenario automatically. This will allow the other fixes to be applied successfully.

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…
#tool integration#LLM response#prompt template#agent execution#callback error

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 doctor --fix does not auto-migrate invalid bailian compat.thinkingFormat enum values after upgrade [1 comments, 2 participants]