Repository navigation
Description
Summary
Reasoning control is broken for Local AI (the llama-server the app launches and registers as the llamacpp provider):
- Effort Off /
/think offdoes not stop thinking. The model keeps reasoning; the gateway only hides the output, so Off still costs the full thinking time. - Newer gateways can fail outright. Gateway 2026.10.5 beta sends
reasoning_effortto local OpenAI-compatible providers by default. With the app's current provider entry,/think minimalon Qwen3.8 returns HTTP 500 from llama-server.
Root cause
LlamaServerRouterConfiguration.cs:295writesreasoning = oninto the llama-server preset. With--reasoning on, llama.cpp ignoresreasoning_effort: "none", so the per-request off switch has no effect. This is an upstream llama.cpp bug (still on master); under the default--reasoning auto,"none"turns thinking off for every template in the Local AI catalog.LocalAiGatewayProviderDefinition.BuildProviderJsondeclaresreasoning = truebut nocompat.supportsReasoningEffort/supportedReasoningEfforts. The gateway therefore either sends nothing the server honors (older gateways) or sends levels the model template does not support, such asminimal(2026.10.5 beta).GatewayActionTransport.cs:122sendsthinking: "low"with every canvas (A2UI) action. The gateway persists that level on the chat session, so one canvas action silently switches the user's Effort to Low and turns Off back into thinking.
Proposed fix (standard reasoning_effort, not model-specific)
Use OpenAI's reasoning_effort field, which llama-server implements and the gateway already supports per model, with Off sent as "none":
- Drop
reasoning = onfrom the llama-server preset (fall back to the defaultauto). - Declare per-model effort support in the provider entry, sourced from the model catalog for every entry:
- Qwen3.8:
supportedReasoningEfforts: [none, low, medium, high], hide Minimal (its template has low / medium / xhigh, and accepts high as xhigh). - Qwen3.6 and Qwen3.5:
[none, medium], hide Minimal and High (on/off only). "none"must be listed, or the gateway drops Off.- Do not hide Low: the gateway rejects an explicitly requested hidden level rather than clamping it, and paired phones request Low.
- Qwen3.8:
- Stop canvas actions from sending
thinking: "low".
Resulting pickers: Off / Low / Medium / High / Ultra for Qwen3.8, Off / Low / Medium / Ultra for Qwen3.6 (Ultra is a gateway mode and cannot be hidden).
Both app config write paths (config set --batch-file and config.patch) preserve the hidden-level settings and pass the exact readback check. Existing installs need a provider-entry migration so an upgrade does not hit the "changed outside the companion" repair state.
Trade-offs to decide
- Default effort drops for Qwen3.8 from xhigh to medium (the gateway default). In return, switching between Medium and Off reuses the prompt cache instead of re-prefilling the agent prompt (about 21 s on an RTX Spark), because the Qwen3.8 template writes the effort level at the top of the system prompt.
- Gateway floor rises to v2026.6.5, since older gateways reject the level-hiding setting. Only native-gateway installs are affected; WSL setup installs the latest gateway.
- Phones can still switch Effort to Low through voice transcripts and the iOS share extension. That needs an upstream gateway change.
Validation so far
Proven end to end through real gateways 2026.9.8, 2026.10.2 and 2026.10.5 beta on Linux with an RTX 4090, using a small stand-in model loaded with the real Qwen chat templates.
Not yet tested: the real catalog models, Windows, the app's own Effort UI and canvas path, and llama-server router mode under auto.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
Projects
- StatusShow more project fieldsBacklog
Activity
clawsweeper commentedon Nov 2, 2026
Codex review: this still needs some work.
Summary
Keep this issue open: current main retains the reported configuration defects, the partial fix remains unmerged, and this collaborator-authored report requires explicit maintainer judgment.
Reproducibility: Current source establishes forced reasoning, absent effort metadata and the canvas Low override; the report and linked candidate supply runtime observations, but this read-only review ran no tests or live reproduction.
Root-cause cluster
Relationship:
canonicalCanonical: #1976
Summary: This issue retains the broader Local AI effort-control problem; the existing candidate implements a qualified-Qwen and canvas subset.
Members:
fixed_by_candidate: fix: honor Effort Off for qualified Qwen local AI models #2012 - The candidate addresses the named router, provider and canvas paths but explicitly defers non-Qwen effort metadata.Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.
Maintainer decision needed
Next step
Review #2012 (fix: honor Effort Off for qualified Qwen local AI models) for the remaining migration and pinned-runtime proof, then confirm its default-effort policy and deferred model scope.
Review details
Best possible solution:
Honor validated per-model effort capabilities while preserving session choices, credentials, external edits and recoverable managed upgrades.
Do we have a high-confidence way to reproduce the issue?
Current source establishes forced reasoning, absent effort metadata and the canvas Low override; the report and linked candidate supply runtime observations, but this read-only review ran no tests or live reproduction.
Is this the best way to solve the issue?
Catalog-backed capabilities and session inheritance fit the existing owners, but the original fixed Gateway floor should not be assumed necessary because the candidate now proposes guarded degradation on older versions.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning medium; reviewed against 212fac114f6f.
Label changes
Label changes:
No label changes.
Label justifications:
P2: Optional Local AI effort control and selected inference requests are affected, without an established core-runtime outage or blocked onboarding flow.impact:auth-provider: Generated provider capabilities do not constrain reasoning requests to the local model's supported vocabulary.impact:session-state: Canvas requests explicitly override effort with Low, and the contributor reports that value replacing the session's selected Off state.Evidence reviewed
What I checked:
src/OpenClaw.Connection/LocalAi/LlamaServerRouterConfiguration.cs:297, 212fac114f6f)src/OpenClaw.Connection/LocalAi/LocalAiGatewayProviderDefinition.cs:124, 212fac114f6f)src/OpenClaw.Tray.WinUI/A2UI/Actions/GatewayActionTransport.cs:122, 212fac114f6f)src/OpenClaw.Tray.WinUI/Services/LocalAiGatewayProviderCoordinator.cs:70, 212fac114f6f)Likely related people:
src/OpenClaw.Tray.WinUI/A2UI/Actions/GatewayActionTransport.cs)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.Reviewed November 17, 2026, 10:25 PM ET / November 18, 2026, 03:25 UTC.
fix: honor Effort Off for qualified Qwen local AI models (openclaw#1976)
fix: honor Effort Off for qualified Qwen local AI models (openclaw#1976)
github-actions commentedon Nov 17, 2026
This issue has been automatically marked as stale due to inactivity.
Please add updated OpenClaw Windows details or it will be closed.