feat: openai-compatible-strict-reasoning (2/2) - #34
Closed
myk1yt wants to merge 53 commits into
Closed
Conversation
myk1yt
force-pushed
the
pr/b17-provider-cost-v2
branch
from
August 4, 2026 06:11
ca96c3c to
7f5fa9e
Compare
myk1yt
force-pushed
the
pr/b05a-strict-reasoning-v2
branch
from
August 4, 2026 11:34
658c4f2 to
4692197
Compare
myk1yt
force-pushed
the
pr/b17-provider-cost-v2
branch
from
August 4, 2026 11:40
7f5fa9e to
42df2fa
Compare
myk1yt
force-pushed
the
pr/b05a-strict-reasoning-v2
branch
3 times, most recently
from
August 4, 2026 20:40
77e7207 to
a3b22a7
Compare
myk1yt
force-pushed
the
pr/b17-provider-cost-v2
branch
5 times, most recently
from
August 6, 2026 07:28
98dd23f to
9d2c50a
Compare
# Conflicts: # src/core/tools/error-interception/StructuralValidator.ts
# Conflicts: # src/core/assistant-message/__tests__/NativeToolCallParser.spec.ts # src/core/assistant-message/__tests__/presentAssistantMessage-parser-dedup.integration.spec.ts # src/core/assistant-message/presentAssistantMessage.ts
# Conflicts: # src/core/assistant-message/__tests__/presentAssistantMessage-parser-dedup.integration.spec.ts
…ception refs from backup
MimoHandler was passing raw tool schemas to the API without the strict mode conversion that all other OpenAI-compatible providers use. This caused tool call errors due to missing required/strict fields. - Call this.convertToolsForOpenAI(tools) instead of raw assignment - Adds strict: true, required properties, additionalProperties: false
An id-less argument-continuation chunk belongs to the most recent id chunk seen at its index. When a provider reuses index 0 with a NEW id (a disguised second parallel call), the new call's id chunk was dropped but its id-less argument fragments were still kept and concatenated into the FIRST call's accumulator, corrupting its JSON. Track dropped indexes in filterToFirstToolCall state and drop subsequent id-less fragments for those indexes. Also rewrite the function docblock, which referenced a non-existent error-interception retry loop.
The parseErrors/parseFailures docblocks claimed presentAssistantMessage routes recorded failures to an INVALID_JSON_ARGUMENTS error-interception pattern. No such routing exists on this codebase; describe the actual lifecycle (consumed via the consume* APIs, cleared on new API request). Comment-only change, no behavior difference.
parseErrors/parseFailures static maps accumulated an entry per malformed tool call and were never cleared in production (the consume* APIs have no production callers), slowly leaking for the extension-host lifetime. Add NativeToolCallParser.clearParseFailures() and call it in Task.recursivelyMakeClineRequests alongside clearAllStreamingToolCalls()/ clearRawChunkState(), where other per-stream state is reset. The consume* APIs keep working for tests.
MiMo sends tools through convertToolsForOpenAI(), which attaches a strict flag to every function tool. An OpenAI-compatible endpoint that doesn't support structured outputs rejects the request with a 400 and the turn fails outright. Mirror the existing parallel_tool_calls fallback: detect schema-rejection errors narrowly (400 status plus a mention of strict/additionalProperties in a tools context, so unrelated 400s like MiMo's missing-reasoning_content rejection are not retried) and retry once with the original schemas and no strict flag.
Co-authored-by: Roomote <roomote@roomote.dev>
…1190) Co-authored-by: Roomote <roomote@roomote.dev>
…1132) CI failure: E2E Tests (Mocked) failed with '404 No fixture matched' because provider-cost.test.ts calls startNewTask with probe tag 'provider-cost-e2e' but no fixture existed.
…stubs and custom endpoints
…ames (Zoo-Code-Org#1073) * fix(telemetry): record tool usage once centrally, sanitize raw tool names * fix(telemetry): defer native MCP usage recording until validation passes * fix(telemetry): narrow UseMcpToolTool callback, harden test mocks, close coverage gaps * test(telemetry): complete native MCP mock so validateToolExists runs the real path
Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Roomote <roomote@roomote.dev>
…sages load (Zoo-Code-Org#1181) * fix(task): skip saveClineMessages when history task aborts before messages load * test: strengthen resume-eviction-race assertions and type mock provider * test: add fallback mock for second getSavedClineMessages read in resume-eviction spec * fix(task): prevent saving unhydrated history messages during abort --------- Co-authored-by: Naved Merchant <naved.merchant@gmail.com>
…-Code-Org#1198) Co-authored-by: Roomote <roomote@roomote.dev>
…rg#1141) * refactor(webview): complete provider identifier migration * test(webview): type selected model hook mocks * test(webview): keep selected model spec out of provider migration * test(webview): harden provider identifier migration tests --------- Co-authored-by: Elliott de Launay <edelauna@gmail.com>
…de-Org#1193) * chore(deps): update dependency mermaid to v11.16.1 [security] * fix(webview): harden mermaid securityLevel and tighten dev-mode CSP --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Elliott de Launay <edelauna@gmail.com>
…-Org#1161) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…#1199) Co-authored-by: Roomote <roomote@roomote.dev>
…o-Code-Org#1200) Co-authored-by: Roomote <roomote@roomote.dev>
…rg#1146) * refactor(webview): canonicalize ApiOptions provider identifiers * test(webview): strengthen ApiOptions interaction coverage * fix(webview): use providerIdentifiers.openrouter in ApiOptions option sort --------- Co-authored-by: Elliott de Launay <edelauna@gmail.com>
…-Code-Org#1203) Co-authored-by: Roomote <roomote@roomote.dev>
…o-Code-Org#1204) Co-authored-by: Roomote <roomote@roomote.dev>
…-Code-Org#1201) Co-authored-by: Roomote <roomote@roomote.dev>
Owner
Author
|
Closing to recreate with main as target base branch. This PR had stale base branch references after fork sync. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stack Position
feat/openai-compatible-strict-reasoningDescription
Full Feature Description
feat/openai-compatible-strict-reasoningprovider-settings.ts,base-openai-compatible-provider.ts,base-provider.ts,OpenAICompatible.tsx,openai.ts,openai-compatible.ts,anthropic-vertex.ts,qwen-code.ts.cachedStatebefore saving. Cost calculation treats missing fields as unknown or zero per provider contract and does not produce negative tokens. Cached input/output tokens and provider-specific price units are not double-counted. B17 does not change request payload or tool-call policy.Why Split Into 17 PRs
Instead of submitting this feature as a single unified PR, it was split into individual PRs because as code size grows, safely reviewing a PR becomes very difficult. The feature was broken into mutually exclusive individual PRs so that each can be reviewed independently.
What This PR Specifically Changes
Normalizes OpenAI/OpenAI-compatible/Anthropic Vertex/Qwen usage fields and cached tokens, and calculates cost according to provider price lookup. Does not change request payload, strict UI, or MiMo tool policy.
Included Files
src/api/providers/openai.tssrc/api/providers/openai-compatible.tssrc/api/providers/anthropic-vertex.tssrc/api/providers/qwen-code.tsExclusion Scope