Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix 2026.3.24 breaks Mistral provider: models.json overwritten with wrong api type [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#56262•Fetched 2026-04-08 01:43:02
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
samgoos7samgoos7
Participants
HaqiverseHaqiversesamgoos7samgoos7
Timeline (top)
commented ×1

Upgrading from 2026.3.13 to 2026.3.24 breaks the Mistral provider. On gateway startup, 2026.3.24 overwrites agents/main/agent/models.json and adds a Mistral provider entry with "api": "openai-completions". This causes all Mistral API calls to return a 404:

{
  "message": "no Route matched with those values"
}

Root Cause

Upgrading from 2026.3.13 to 2026.3.24 breaks the Mistral provider. On gateway startup, 2026.3.24 overwrites agents/main/agent/models.json and adds a Mistral provider entry with "api": "openai-completions". This causes all Mistral API calls to return a 404:

{
  "message": "no Route matched with those values"
}

Fix Action

Workaround

Pin to 2026.3.13 and keep models.json without a Mistral provider entry (let the gateway use its built-in provider).

Code Example

{
  "message": "no Route matched with those values"
}
RAW_BUFFERClick to expand / collapse

Description

Upgrading from 2026.3.13 to 2026.3.24 breaks the Mistral provider. On gateway startup, 2026.3.24 overwrites agents/main/agent/models.json and adds a Mistral provider entry with "api": "openai-completions". This causes all Mistral API calls to return a 404:

{
  "message": "no Route matched with those values"
}

Steps to reproduce

  1. Start with a working setup on 2026.3.13 using mistral/mistral-medium-latest
  2. models.json has no Mistral entry (gateway uses built-in provider)
  3. npm install -g [email protected]
  4. Restart gateway
  5. models.json is overwritten with Mistral entry: "api": "openai-completions", "baseUrl": "https://api.mistral.ai/v1"
  6. All Mistral calls return 404

Expected behavior

Gateway should either:

  • Not overwrite models.json on startup, or
  • Write the correct api type for Mistral (not openai-completions)

Workaround

Pin to 2026.3.13 and keep models.json without a Mistral provider entry (let the gateway use its built-in provider).

Environment

  • macOS Darwin 24.6.0
  • Node.js 24
  • Model: mistral/mistral-medium-latest
  • Auth: api_key mode via .env

Additional context

The Mistral API works fine when called directly. The issue is specifically in how 2026.3.24 generates the provider config in models.json.

Also noted: 2026.3.24 has a path-to-regexp breaking change in the msteams extension (/api* → should be /api{*path}).

extent analysis

Fix Plan

To fix the issue, we need to update the models.json file to use the correct api type for Mistral. We can achieve this by manually updating the models.json file or by modifying the code that generates it.

Manual Update

  1. Stop the gateway.
  2. Open the models.json file and update the Mistral provider entry to use the correct api type.
{
  "api": "mistral",
  "baseUrl": "https://api.mistral.ai/v1"
}
  1. Restart the gateway.

Code Update

If you want to modify the code that generates the models.json file, you can update the openclaw package to use the correct api type for Mistral.

// Update the provider config generation code
const mistralProvider = {
  api: 'mistral',
  baseUrl: 'https://api.mistral.ai/v1'
};

// Use the updated provider config when generating models.json

Note: The exact code changes will depend on the implementation of the openclaw package.

Verification

To verify that the fix worked, you can check the models.json file to ensure that it has the correct api type for Mistral. You can also test the Mistral API calls to ensure that they are no longer returning 404 errors.

Extra Tips

  • Make sure to test the fix thoroughly to ensure that it does not introduce any new issues.
  • Consider reporting the issue to the openclaw package maintainers so that they can update the package to use the correct api type for Mistral.
  • Keep in mind that the path-to-regexp breaking change in the msteams extension may also need to be addressed separately.

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…

FAQ

Expected behavior

Gateway should either:

  • Not overwrite models.json on startup, or
  • Write the correct api type for Mistral (not openai-completions)
#api#installation#tensor shape#autograd error#model save/load

Still need to ship something?

×6

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

Back to top recommendations

TRENDING