-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat: new threads should default to previous threads configurations #1175
Comments
Threads should indeed default to the same settings as the previous Discussion in progress: Right now, we hardcoded model parameter defaults for thread.json, when model params should inherit from assistants (which inherits from models) (1) First time ever that you chat with a model.
(2) Starting a new thread with existing chat history Option a) default to previous thread configs I prefer (a) |
I will include this issue to epic: #1507 |
🙏
…On Tue, Jan 23, 2024 at 11:12 AM Ashley ***@***.***> wrote:
I will include this issue to epic: #1507
<#1507>
—
Reply to this email directly, view it on GitHub
<#1175 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQVWFCGDHUOREKUCQJ62QWTYP4TDHAVCNFSM6AAAAABBALCDCCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBVGIYTQNBYGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Need Cortex support as in https://github.com/janhq/cortex/issues/617 |
I am always sliding the slider to 4096 tokens every new chat from the default. It should 100% remember what you set it to and persist.
The text was updated successfully, but these errors were encountered: