-
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
bug: thread.json not automatically updated before clicking send button #1212
Comments
@hieu-jan I'd rephrase the bug to be clearer. Expected:
Current:
We expect this to be a common UX and it needs to be handled. Users are highly likely to configure parameters first, before sending their first message. |
Thanks for the clarification. That makes sense, will fix this. |
As discussed with @louis-jan, the Save button is no longer available, so we will need the thread.json to be automatically created / updated on any changes. |
…ttings Signed-off-by: nam <[email protected]>
…ttings (#1570) Signed-off-by: nam <[email protected]>
This is issue is fixed with PR #1570 . Please help to verify it. Thank you! |
Fixed as of nightly, patch no. 143 |
Describe the bug
thread.json not automatically updated before clicking send button
Steps to reproduce
Steps to reproduce the behavior:
thread title
andassistant instruction
after selecting model.Expected behavior
As a discussion in the meeting with @0xSage, we currently expect that the thread.json is automatically generated and updated when user doing any action like type an input to
thread title
,assistant instruction
or selecting model. Thus, when users selecting the model, it's should be remain the same thread title and assistant instruction as thread.json is already created.Screenshots
GIF will need few minutes for loading
Environment details
Additional context
Add any other context or information that could be helpful in diagnosing the problem.
The text was updated successfully, but these errors were encountered: