Replies: 4 comments 6 replies
-
Memory design looks seamless for users! Amazed how fast you got that worked out and functional. Not a fan of having constructor being same name - So instead of For chain types - will this work with agents? Can we have more than one role there beside |
Beta Was this translation helpful? Give feedback.
-
I think Even for non-chat applications I found that splitting typical prompts into a conversation improves the output. For example my summary prompt:
So I think langchain should treat the entire message array as a prompt. It can still accept a single string for simplicity by internally checking whether the argument type is List or str to conveniently accept simple queries. |
Beta Was this translation helpful? Give feedback.
-
I have a question.
Q1. How to print the prompt with each query? |
Beta Was this translation helpful? Give feedback.
-
updated a pr with more thoughts on how we'll introduce the abstractions pr: #1424 docs: https://langchain.readthedocs.io/en/harrison-chat-models/modules/chat.html |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The ChatGPT API came out today and had a pretty different interface than before. Rather than being "text in, text out" it was exposed with a "list of messages in, list of messages out" format.
The first integration we did was to create a wrapper that just treated ChatGPT API as a normal LLM: #1367
However, this seems a bit limiting in allowing users to take advantage of the full functionality of ChatGPT API (or other chat APIs in the future). Therefore, it probably makes sense to rethink some of the lower level abstractions. This will likely have the consequence of changing a lot of the internals of the chains, although the high level interface should remain similar
An attempt to start doing this is here: #1375
If you just want to use the code, I cut a prerelease to allow people to do so
pip install --pre langchain==0.0.99rc0
So far, some of the more common chains that seem appropriate for chat have been implemented:
I am extremely interested in hearing others opinions on both the low level abstractions that will be needed to support this new type of API as well as the chain types we should prioritize adding support for these types of interfaces.
Beta Was this translation helpful? Give feedback.
All reactions