You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the OpenAI responses api the responseId that needs to be used needs to be updated on every call to the agent to ensure you are responding to the latest message, unlike the standard ThreadId for the assistants api. I don't see how this is being handled from the backend at all when using the AG-UI integration. I have the feeling it's not supported yet, but i can't find any information about it. Most of the information is in this PR #1776, but it does not refer to the response API itself at all. If it's not supported, what are the future plans and any rough timeline for it?
Similarly I noticed that initializing the history is not supported yet, i suspect MessagesSnapshot will take care of it, what's the timeline for that? Again a rough timeline is good enough.
Currently my slightly simplified backend code is this:
var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAGUI();
// Create the AI agent
var openAiClient = new AzureOpenAIClient(
new Uri(endpoint),
new AzureKeyCredential(apikey));
#pragma warning disable OPENAI001
var responseClient = openAiClient.GetOpenAIResponseClient(deploymentName);
#pragma warning restore OPENAI001
builder.AddAIAgent(AgentId, (s, k) => responseClient.CreateAIAgent(
instructions: AgentDescription,
name: AgentId));
var app = builder.Build();
app.UseCors("Frontend");
var agent = app.Services.GetRequiredKeyedService<AIAgent>(AgentId);
app.MapAGUI($"/{AgentId}", agent);
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For the OpenAI responses api the responseId that needs to be used needs to be updated on every call to the agent to ensure you are responding to the latest message, unlike the standard ThreadId for the assistants api. I don't see how this is being handled from the backend at all when using the AG-UI integration. I have the feeling it's not supported yet, but i can't find any information about it. Most of the information is in this PR #1776, but it does not refer to the response API itself at all. If it's not supported, what are the future plans and any rough timeline for it?
Similarly I noticed that initializing the history is not supported yet, i suspect MessagesSnapshot will take care of it, what's the timeline for that? Again a rough timeline is good enough.
Currently my slightly simplified backend code is this:
Beta Was this translation helpful? Give feedback.
All reactions