-
Notifications
You must be signed in to change notification settings - Fork 138
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
planning: Cortex API supports basic /assistants
(Jan status quo equivalent)
#1573
Comments
/assistants
API and Data Structures
/assistants
API and Data Structures/assistants
@namchuai @louis-jan For migration of Assistant, I think we can scope it down into two things: Legacy "Assistants"
Legacy Retrieval ToolI would like to understand the possible approaches for us to handle this:
I think it is easier for us to scope this to having legacy handlers and focus specifically on migration. With system stability, it is the possible for us to use v2 API handlers to build proper APIs, which will handle new Threads, Assistants and Tools |
@louis-jan @namchuai While this ticket is for a
We should evaluate this; if it is too messy or difficult to align with an OpenAI-compatible API, I am open with also just going with our own (e.g. Runs, etc). |
/assistants
/assistants
/assistants
/assistants
(Jan status quo equivalent)
Hi @namchuai, can you take a look at assistants endpoint I did check and Jan have an assistants folder and I think Jan query assistant endpoint for this folder not from thread
|
Goal
cortex.db
has Assistants tableassistant.yaml
/assistants
API jan#3909The text was updated successfully, but these errors were encountered: