Skip to content
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.

Sign up for GitHub

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

Jump to bottom

AKAI: Content vs GPT flag #572

Open
MaunicaKolla815 opened this issue Oct 14, 2024 · 3 comments
Open

AKAI: Content vs GPT flag #572

MaunicaKolla815 opened this issue Oct 14, 2024 · 3 comments
Assignees
@prtkjakhar @Amruth-Vamshi

Comments

@MaunicaKolla815
Copy link

MaunicaKolla815 commented Oct 14, 2024 •
edited
Loading

Requirements

Backend - @Amruth-Vamshi

Add the responseType flag for the following cases - for unguided flows

  1. response fetched from GPT | GPT
  2. response fetched from content | Content
  3. response fetched from GPT, even when content exists | chunkGPT

Frontend

TBD - to be showcased in the Diagnosis, add a column responseType

Timeline

For sprint 2422
@MaunicaKolla815
Copy link
Author

@prtkjakhar - any update on this?

@PriyanshiSoni11
Copy link
Collaborator

@MaunicaKolla815
Tested this on Admin staging with KMAI bot, getting responseType in Diagnosis.

@MaunicaKolla815
Copy link
Author

@prtkjakhar - can we move this to UAT, so that @PriyanshiSoni11 and I can test it there..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@prtkjakhar prtkjakhar

@Amruth-Vamshi Amruth-Vamshi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@prtkjakhar @Amruth-Vamshi @PriyanshiSoni11 @MaunicaKolla815