openclaw - 💡(How to fix) Fix NVIDIA API doNVIDIA custom provider hangs with thinking=medium — no way to disable per provideresn't support it. Need a way to disable thinking per custom provider. [2 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#78627Fetched 2026-05-07 03:34:32
View on GitHub
Comments
2
Participants
2
Timeline
3
Reactions
2
Author
Timeline (top)
commented ×2labeled ×1

Custom NVIDIA provider freezes when OpenClaw auto-sets thinking=medium because NVIDIA API does not support this parameter.

Root Cause

Custom NVIDIA provider freezes when OpenClaw auto-sets thinking=medium because NVIDIA API does not support this parameter.

Fix Action

Fix / Workaround

Severity: High — blocks all responses Frequency: Always Consequence: Bot unusable with NVIDIA custom provider as primary model Workaround: Use google/gemini-2.5-flash as primary instead

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Custom NVIDIA provider freezes when OpenClaw auto-sets thinking=medium because NVIDIA API does not support this parameter.

Steps to reproduce

  1. Add custom provider: custom-integrate-api-nvidia-com/meta/llama-3.1-70b-instruct
  2. Set it as agents.defaults.model.primary
  3. Send any message via Telegram
  4. Observe bot returns cached "Standing by" instead of live response

Expected behavior

Bot responds normally. thinking parameter should not be sent to providers that don't support it.

Actual behavior

Gateway sets thinking=medium for NVIDIA model. NVIDIA API does not support this parameter and hangs. Bot returns 100% cached response.

OpenClaw version

2026.5.6

Operating system

Windows 11 + WSL2 Ubuntu

Install method

npm global

Model

custom-integrate-api-nvidia-com/meta/llama-3.1-70b-instruct

Provider / routing chain

openclaw -> NVIDIA integrate AP

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

Severity: High — blocks all responses Frequency: Always Consequence: Bot unusable with NVIDIA custom provider as primary model Workaround: Use google/gemini-2.5-flash as primary instead

Additional information

No response

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

Bot responds normally. thinking parameter should not be sent to providers that don't support it.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING