# Custom Gemini Model Not Supported

**URL:** <https://forum.cursor.com/t/custom-gemini-model-not-supported/168676>\
**Category:** Help\
**Tags:** gemini, byok\
**Created:** [August 17, 2026, 7:49pm UTC](https://forum.cursor.com/t/custom-gemini-model-not-supported/168676 "2026-08-17T19:49:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Devansh\_Singh](https://avatars.discourse-cdn.com/v4/letter/d/eb9ed0/32.png) [@Devansh\_Singh](https://forum.cursor.com/u/Devansh_Singh)\
**Post date:** [August 17, 2026, 7:49pm UTC](https://forum.cursor.com/t/custom-gemini-model-not-supported/168676/1 "2026-08-17T19:49:58Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Adding gemini-3.5-flash-lite as a custom model will fail apparently because the though\_signature parameter is not supported via OpenAI routing.

### Steps to Reproduce

Add gemini-3.5-flash-lite as a custom model and run a query which uses a tool call.

### Expected Behavior

Custom gemini model should run normally.

### Screenshots / Screen Recordings

 ![Screenshot 2026-08-18 at 1.18.26 AM.png](https://us1.discourse-cdn.com/cursor1/original/3X/b/e/be5880ba52632a9d440fce6d5d7e9af8e96c9231.png)

### Operating System

MacOS

### Version Information

Cursor IDE: 3.16.17

### For AI issues: which model did you use?

gemini-3.5-flash-lite

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [August 20, 2026, 7:18am UTC](https://forum.cursor.com/t/custom-gemini-model-not-supported/168676/6 "2026-08-20T07:18:42Z")

</div>

Hey, thanks for the report, and for the screenshot with the error and the Request ID, that helped me track it down.

What’s happening: `gemini-3.5-flash-lite` isn’t one of the officially supported models in Cursor’s model picker. When you add it as a custom model via the OpenAI-compatible routing, the first turn works, but on later turns with tool calls Google returns `400 Function call is missing a thought_signature`. The reason is that for flash-lite slugs Cursor currently doesn’t include the required thought signatures when it resends the conversation history that contains tool calls.

This is a known issue, the same thing was reported before for `gemini-3.1-flash-lite-preview`. We’ve passed it to the team. I can’t share an ETA yet, but I’ll reply here when there’s an update.

For now, the workaround is to use `gemini-3.5-flash` (supported natively, no custom key needed) or any other non flash-lite Gemini model with your own key. Tool calls work fine there.
