Escape prompt prefix/suffix along with prompt #2151
Merged
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.
I've been using some models that are a bit picky about the prompt format during chats. In particular, it seems like some of them prefer a newline after the reverse prompt (e.g.,
ASSISTANT:\n
). The existing "main" example does allow parsing newlines and other escape characters in the prompt with-e
, but not in the prompt prefix or suffix (--in-prefix
and--in-suffix
). This pull request adds escaping to those parts as well, allowing for things like this:This inserts "ASSISTANT:" and a newline after the user presses enter, which works a bit better in some of my cases. I haven't needed escape characters in the prompt prefix, but it seems better to parse them anyway for consistency. Possibly there are use cases where it would be needed that I haven't encountered.