-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support oncokb agent and agent selector #20
Conversation
item: ChatCompletionsPostModel, | ||
# request: Request, # ChatCompletionsPostModel, | ||
# item: ChatCompletionsPostModel, | ||
request: Request, # ChatCompletionsPostModel, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we go back to Request due to the connection issue. If we use ChatCompletionsPostModel, biochatter-next can't communicate in this endpoint, which is a bug, and I'll fix it in next PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fengsh27 thanks; I merged use_reflexion in biochatter
, so it makes sense to merge here as well, right? Should we merge and bump minor version here, or do we need to wait for other changes?
@slobentanzer I updated biochatter version to 0.7.3, and now we are ready to merge to main |
merging, bumping to |
Abstract
This submission is to support OncoKB API agent and Rag Agent selector. To achieve this, this submission introduced the following parameters when requesting chat completion:
1). useKG, kgConfig
2). useRag, ragConfig
3). oncokbConfig
4). useAutoAgent
Regarding individual agents, the rule that determines if the agent is enabled:
**Config is not None and (useAutoAgent or useXxx)
.For example, in the case KG,