Unable to remove "stop" parameter from autocomplete request for gpt-5-nano

[sbaechler]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macOS
- Continue version: 1.3.16
- IDE version: VSCode recent
- Model: gpt-5-nano
- config:
  
- name: GPT 5 nano
      model: gpt-5-nano
      <<: *azure
      roles:
          - autocomplete
          - apply
      defaultCompletionOptions:
          contextLength: 272000
          temperature: 1
          stop: []

Description

GPT-5-nano does not support the stop parameter at all. It returns a 400 response. It looks like the parameter is sent even if I set it to an empty array.

I am using the Azure API with API version '2025-04-01-preview'.

To reproduce

1. Configure gpt-5-nano as autocomplete model.
2. Select it in the config
3. Start coding.

Log output

`{ "error": { "message": "Unsupported parameter: 'stop' is not supported with this model.", "type": "invalid_request_error", "param": "stop", "code": "unsupported_parameter" } }`

[github-actions]

This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.

[sbaechler]

The bug still occurs in version 1.3.24

[kku39]

I’m facing the same issue on Windows 11.

I found a workaround by overriding the stop parameter to null using requestOptions.extraBodyProperties like this:

  - name: Azure GPT 5 nano
    provider: azure
    model: gpt-5-nano
    requestOptions:
      extraBodyProperties:
        stop: null

[favro-zz]

I have a similar bug using grok-code-fast-1. Setting the stop parameter doesn't override the internal stop parameters, it merely adds to them and causes Grok to return a "too many stops" error.