Add a /query command.
#28
Merged
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
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
cmyui
reviewed
Feb 1, 2025
|
|
||
| output_messages.append(message_chunk) | ||
|
|
||
| return output_messages |
There was a problem hiding this comment.
wondering if we should use this everywhere?
cmyui
reviewed
Feb 1, 2025
| else: | ||
| messages_to_send = result.response_messages | ||
|
|
||
| # I have no idea whether they actually allow you to send multiple follow-ups. |
There was a problem hiding this comment.
i would kill u for these comment in a workplace rofl
There was a problem hiding this comment.
I think I lost it at the “completely untested” bit
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.
This implements the
/queryslash command to allow you to quickly run queries without the need for context. This is aimed at being used in environments where the bot/you don't have access to threads (such as DMs and group chats).Long-term, this would consider some per-user context (maybe 5 messages).
On top of this, it genericises some of the API to be more re-usable (such as smart message splitting and the GPT query loop).
Note
This does not integrate with the cost count implemented as the logic there was too thread-focused to be done simply.
Also completely untested.