You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This list will be adapted into several individual open issues for better granularity。
1. has a message hierarchy similar to hacker news or reddit, indicating the target of each message reply. Message threads can be collapsed. You can name the thread title.
2. A single message has the following controls: add reply, modify content, regenerate in place or in another branch, delete, publisher.
3. Add a reply: an input box appears at the bottom of the screen, and the top of the input box is labeled with the content being replied to. Add and Close buttons are available. You can select the publisher. When the publisher is a user, only message is added; when the publisher is a model, user's message is added and the model generates a reply, The reply and generate is put under target message, and there is a Quick Chat button (no message is added, and the model's reply appears in a pop-up window).
4. Modify the content: the text display area can be edited, the control changes to send and close buttons.
5. Edit text: support for SGLang semantics (perhaps a difficult task) -- we need to discuss further. Possible approach: direct encapsulation of SGLang methods? wrap up sgl functions as service, similar to Wordware.
6. publisher selection: user, model list (configuration in sidebar, only select/configure button available in list)
7. model configuration: when the thread interface, you can click on the model list, the right side of the pop-up sidebar to select the configuration parameters as well as the system prompt. there are select/save configuration/new copy/delete buttons. You can also enter the specific model configuration page through the left tab.
8. tabs: overall application settings (Api key, etc.); model configuration (imagine you select the google drive tab in your browser, and then a list of documents appears on the screen); thread list. For this functionality, it might be possible to utilize the browser's tab management directly. (Each thread is an html that can be opened directly? The exact form of implementation needs to be carefully considered.)
The text was updated successfully, but these errors were encountered:
This list will be adapted into several individual open issues for better granularity。
regenerate in place orin another branch, delete, publisher.Add a reply: an input box appears at the bottom of the screen, and the top of the input box is labeled with the content being replied to. Add and Close buttons are available. You can select the publisher. When the publisher is a user, only message is added; when the publisher is a model, user's message is added and the model generates a reply,The reply and generate is put under target message, and there is a Quick Chat button (no message is added, and the model's reply appears in a pop-up window).Edit text: support for SGLang semantics (perhaps a difficult task) -- we need to discuss further. Possible approach: direct encapsulation of SGLang methods?wrap up sgl functions as service, similar to Wordware.(imagine you select the google drive tab in your browser, and then a list of documents appears on the screen);thread list.For this functionality, it might be possible to utilize the browser's tab management directly. (Each thread is an html that can be opened directly? The exact form of implementation needs to be carefully considered.)The text was updated successfully, but these errors were encountered: