Skip to content

add support for Azure OpenAI - #3

Merged
qmuntal merged 1 commit into
mainfrom
dev/gadams/azureai
Oct 27, 2025
Merged

add support for Azure OpenAI#3
qmuntal merged 1 commit into
mainfrom
dev/gadams/azureai

Conversation

@gdams

@gdams gdams commented Oct 27, 2025

Copy link
Copy Markdown
Member

No description provided.

@gdams
gdams requested a review from qmuntal October 27, 2025 16:35
@qmuntal
qmuntal merged commit 5caadb0 into main Oct 27, 2025
1 check passed
@qmuntal
qmuntal deleted the dev/gadams/azureai branch October 27, 2025 19:54
qmuntal added a commit that referenced this pull request Dec 10, 2025
qmuntal added a commit that referenced this pull request Dec 10, 2025
qmuntal added a commit that referenced this pull request Dec 10, 2025
github-actions Bot added a commit that referenced this pull request May 25, 2026
Fix two bugs that prevent parallel tool calls from rendering correctly
in AG-UI protocol clients:

Bug #2: Make ToolCallResultEvent.MessageId deterministically unique
using result-{callId} format. Multiple tool results in the same update
batch previously shared a single generated message ID, collapsing them
in FE reconciliation.

Bug #3: Coalesce consecutive assistant-with-tool-calls messages in
toAgentMessages. The AG-UI client creates one assistant message per
tool call when parentMessageId is absent. Sending them as separate
messages to the LLM triggers HTTP 400 because OpenAI requires tool
results to immediately follow every tool_call_id in an assistant message.

Also removes the now-dead hasFunctionResultContent helper.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gdams pushed a commit that referenced this pull request May 26, 2026
Fix two bugs that prevent parallel tool calls from rendering correctly
in AG-UI protocol clients:

Bug #2: Make ToolCallResultEvent.MessageId deterministically unique
using result-{callId} format. Multiple tool results in the same update
batch previously shared a single generated message ID, collapsing them
in FE reconciliation.

Bug #3: Coalesce consecutive assistant-with-tool-calls messages in
toAgentMessages. The AG-UI client creates one assistant message per
tool call when parentMessageId is absent. Sending them as separate
messages to the LLM triggers HTTP 400 because OpenAI requires tool
results to immediately follow every tool_call_id in an assistant message.

Also removes the now-dead hasFunctionResultContent helper.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants