Add messages parameter to chat_ui() and Chat.ui(); revert #1593
#1736
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.
With this PR, the
messagesparameter ofChat.ui()/chat_ui()becomes the suggested way to provide starting messages. For example:Express
Core
This PR also reverts #1593 since waiting until flush to send is not an ideal way to support dynamic UI. As a result, this PR also closes #1735.
In the next release, we should deprecate
Chat(messages=...)in favor of these new parameters. Deprecating now feels premature since it's still convenient for things like system messages. But, when we move towards recommendingchatlas/LangChainfor managing chat state in a future release, we'll deprecate as a part of that move.