Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

o1-mini unusable : use 'max_completion_tokens' instead #193

Open
2 tasks done
TsiAizen opened this issue Nov 22, 2024 · 3 comments
Open
2 tasks done

o1-mini unusable : use 'max_completion_tokens' instead #193

TsiAizen opened this issue Nov 22, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@TsiAizen
Copy link

Verify it's not a duplicate bug report

Describe the Bug

OpenAI error 400: {
"error": {
"message": "Unsupported parameter: 'max_tokens' is not supported with this model. Use 'max_completion_tokens' instead.",
"type": "invalid_request_error",
"param": "max_tokens",
"code": "unsupported_parameter"
}
}

Please tell us if you have customized any of the extension settings or whether you are using the defaults.

model : o1-mini

Additional context

No response

@TsiAizen TsiAizen added the bug Something isn't working label Nov 22, 2024
@TsiAizen TsiAizen changed the title o1-mini: use 'max_completion_tokens' instead o1-mini unusable : use 'max_completion_tokens' instead Nov 22, 2024
@nrbrt
Copy link

nrbrt commented Dec 1, 2024

I can confirm this bug. None of the o1-preview models work.

@dnnspaul
Copy link

Confirming for o1 as well:

image

@ryanwyler
Copy link

Using o1-mini and o1 require additional changes beyond only changing the max_completion_tokens.

o1 appears to use a different format streaming sections of the response back within nested calls back.

I found additional problems using AI Genie to work with the "o1" model. Simple queries worked, but extensive queries seemed to come back with responses that AI Genie was not able to parse so it would come back with blank results. I suspect there is a change with nested queries for sections that the client needs to individually query to get the data for each section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants