fix: max_tokens revert back to 8192 automatically when creating a new thread #4397
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe Your Changes
This PR addresses an issue where the app resets the max_tokens to 8192 whenever users create a new thread. This occurs because the parameter retrieve when creating a new thread is incorrect. It should instead use the max_tokens from the model settings instead of token_limit.
Fixes Issues
max_tokens
automatically revert back to 8192 when users create a new thread #4372Changes made
This pull request includes a small but important change to the
useCreateNewThread
function inweb/hooks/useCreateNewThread.ts
. The change corrects the parameter name fromtoken_limit
tomax_tokens
to ensure the correct value is used.token_limit
tomax_tokens
inuseCreateNewThread
function to ensure the correct value is used.