You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(vertex): preserve tool continuations across system updates #43478
Vertex tool continuations fail when a chronological system update is admitted after a local tool result and before the next model call.
Gemini 3.7 Flash rejects the merged function-response turn with HTTP 400, while Claude Opus 4.8 on Vertex returns HTTP 404 for a terminal native system turn.
Environment
opencode version: 0.0.0-dev-17667
OS: Linux 7.1.8-200.fc44.x86_64
Terminal: TERM=alacritty, COLORTERM=truecolor
Shell: /bin/zsh
Install/channel: dev
Active plugins: opencode-chatgpt-websearch
Reproduction
Configure a local tool such as websearch or webfetch.
Start a tool-using prompt with google-vertex/gemini-3.7-flash#medium or google-vertex/claude-opus-4-8@default.
Admit a chronological system update while the tool is running, before the continuation request is assembled.
Allow the local tool to complete.
Expected Behavior
The tool result and chronological update should be lowered into a provider-valid continuation request and the model should complete normally.
Actual Behavior
Gemini 3.7 Flash returns HTTP 400: Requests ending with a model turn are not supported.
Claude Opus 4.8 on Vertex returns HTTP 404 after a successful local tool call.
Additional Context
Gemini previously merged the system update into the Gemini function-response turn.
Anthropic Messages previously emitted a terminal native system message after the local tool_result turn.
Both failures reproduced with standalone source-build sessions and are covered by provider-lowering regression tests.
This issue might be a duplicate of existing issues. Please check:
core: Vertex Gemini rejects system updates after conversation starts #43431: Same author, same environment, and very similar root cause — Vertex Gemini rejecting system updates after conversation history starts. That issue covers the general case; this one focuses specifically on the tool-continuation path (system update admitted after a local tool result and before the continuation request). If these share the same underlying fix, consider consolidating or cross-referencing them.
Activity
github-actions commentedon Aug 19, 2026
This issue might be a duplicate of existing issues. Please check: