Continue 1.1.45-1.1.47: Gemini agent mode fails with 400 INVALID_ARGUMENT 'alwaysApply'
In Continue 1.1.45 through 1.1.47 on VS Code (Windows 11), agent mode with Gemini models (gemini-2.0-flash, gemini-2.5-flash-05-20, gemini-2.5-pro-preview) fails with HTTP 400 INVALID_ARGUMENT: "Unable to submit request because required fields ['alwaysApply'] are not defined in the schema properties." The same models work in chat and edit modes. Which version fixes this and is there a workaround?
Originally asked on GitHub: https://github.com/continuedev/continue/issues/6121
6 answers
Fixed. The bug was reproduced on Continue v1.1.47, and the issue is resolved in v1.1.57 (a pre-release) and confirmed working in v1.1.62. Upgrade Continue to v1.1.57 or later.
A contributor reproduced the error on v1.1.47 and posted the exact response:
Unable to submit request because required fields ['alwaysApply'] are not defined in the schema properties.This indicates agent mode sends a field the Gemini tool schema rejects, but the thread does not explain the root cause further. The contributor then suggested testing v1.1.57, and users confirmed agent mode with Gemini worked there and in v1.1.62.The reporter's version bisect showed agent mode with Gemini models worked through v1.1.45 and broke by v1.1.47, so that is the regression window if you need to identify the change.
As a temporary workaround, a contributor noted that edit mode still worked with all Gemini models even while agent mode failed. If you cannot upgrade right away, use edit mode with Gemini or use a non-Gemini model for agent mode (general advice, not stated in the thread).
Did this work for you?What @fred-maussion tried on GitHub (Worked)
A user tried Continue v1.1.57 on VS Code after the contributor's suggestion and reported agent mode with Gemini worked.
Source: https://github.com/continuedev/continue/issues/6121#issuecomment-3047618401 (opens external site)
Did this work for you?What @justindonnaruma tried on GitHub (Worked)
A user tested v1.1.62 and reported the issue looked fixed; a contributor then confirmed it was fixed.
Source: https://github.com/continuedev/continue/issues/6121#issuecomment-3069280155 (opens external site)
Did this work for you?What @Patrick-Erichsen tried on GitHub (Didn't work)
A contributor reproduced the 400 error on v1.1.47 and captured the response mentioning the missing 'alwaysApply' field, then suggested trying v1.1.57.
Source: https://github.com/continuedev/continue/issues/6121#issuecomment-3046945481 (opens external site)
Did this work for you?What @ShamanicArts tried on GitHub (Partly worked)
The reporter reverted Continue versions one by one and found agent mode with Gemini worked through 1.1.45, stopped working in 1.1.47, and had also worked in 1.1.41 earlier.
Source: https://github.com/continuedev/continue/issues/6121#issuecomment-2978544924 (opens external site)
Did this work for you?What @ShamanicArts tried on GitHub (Didn't work)
The reporter tested gemini-2.0-flash, gemini-2.5-flash-05-20, and gemini-2.5-pro-preview in agent mode on Continue 1.1.45-1.1.47 using both Gemini and OpenRouter providers; all failed with HTTP 400 INVALID_ARGUMENT while edit mode still worked.
Source: https://github.com/continuedev/continue/issues/6121 (opens external site)
Did this work for you?
Related questions
- Continue error with Llama via LiteLLM: Cannot set properties of undefined (setting 'parsedArgs')
- How to enable Agent mode (tool use) for LM Studio models in Continue?
- How to make Continue's @folder/@codebase send full file contents?
- MCP tool call times out at 60s even with connectionTimeout set in Continue
- Continue error 'Unexpected non-whitespace character after JSON' with Gemini 2.5 Pro or Ollama