github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #15785] gemini-3-flash-preview:cloud - Function Calling returns 400 #56570

New Issue
Open
opened 2026-04-29 11:03:08 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-29 11:03:08 -05:00
Owner
Copy Link

Originally created by @fangcx616 on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/15785

What is the issue?

Google's Gemini 3 API enforces a thought_signature mechanism: every function call response includes a signature that must be sent back alongside the tool result; omitting it causes 400 errors.
Multiple SDKs integrating Gemini 3 have had to add explicit support for thought_signature to make tool calling work.
Ollama Cloud currently does not propagate or manage thought_signature for Gemini 3, causing tool integrations that work with other models to fail specifically for gemini-3-flash-preview:cloud.
Questions:

Is support for Gemini 3 thought_signature in tool/function calling already planned?
Is there a recommended workaround in the meantime (e.g. disable tools for Gemini 3, or use a different Gemini model)?

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @fangcx616 on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/15785 ### What is the issue? Google's Gemini 3 API enforces a thought_signature mechanism: every function call response includes a signature that must be sent back alongside the tool result; omitting it causes 400 errors. Multiple SDKs integrating Gemini 3 have had to add explicit support for thought_signature to make tool calling work. Ollama Cloud currently does not propagate or manage thought_signature for Gemini 3, causing tool integrations that work with other models to fail specifically for gemini-3-flash-preview:cloud. Questions: Is support for Gemini 3 thought_signature in tool/function calling already planned? Is there a recommended workaround in the meantime (e.g. disable tools for Gemini 3, or use a different Gemini model)? ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-29 11:03:08 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#56570
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?