DOC: Clarifying PromptTargets from PromptChatTargets #658
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A prompt chat target is a target where you can explicitly set the conversation history using memory.
This is not something we've explicitly said in the past, but as we're implementing new targets (like RealTimeTarget) which are a LOT like PromptChatTargets, it's important to clarify the difference between the two, because with RealTimeTarget we can't set the conversation history. And this has implications for which attacks will work. For example, PAIR won't work with RealTimeTarget (at least without modification) because you can't set the conversation history the same way.