Responses API: AssistantReasoningDeltaEvent and AssistantReasoningEvent triggered with empty content via BYOK providers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Start by tracing the Responses API handling for AssistantReasoningDeltaEvent and AssistantReasoningEvent, then reproduce the issue using the shown BYOK configuration with OpenAI or vLLM. Compare the provider's reasoning field with the event payload; done when non-empty reasoning is propagated into both events when the provider returns it.
Written by the indexing model from the issue text.
Description
When using GitHub Copilot SDK in a BYOK (Bring Your Own Key) setup—whether the provider is OpenAI or vLLM—the Responses API triggers both AssistantReasoningDeltaEvent and AssistantReasoningEvent, but the content (reasoning or explanation) for these events is always empty.
Steps to reproduce:
- Set up Copilot SDK to use BYOK with OpenAI or vLLM as the provider (Windows or WSL). Example .NET code configuration:
await using var session = await client.CreateSessionAsync(new SessionConfig
{
Provider = new ProviderConfig
{
Type = "openai",
BaseUrl = "https://api.openai.com/v1",
ApiKey = "your_api_key",
WireApi = "responses",
},
ReasoningEffort = "high",
Model = "gpt-5.4-2026-03-05",
OnPermissionRequest = PermissionHandler.ApproveAll,
Streaming = true
});
- Trigger chat completions or requests that should provide reasoning content through the Responses API.
- Observe that AssistantReasoningDeltaEvent and AssistantReasoningEvent are triggered, but the content is always empty.
Expected behavior:
These events should include the reasoning/explanation content returned by the provider's API. Content should not be empty if the provider returns a reasoning field.
Context:
- Environment: Windows, WSL
- Copilot SDK version: 0.3.0
- BYOK provider: OpenAI or vLLM
- Dominant language
- Java
- Stars
- 10.5k
- Forks
- 1.5k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 130
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/copilot-sdk
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2760 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
github/copilot-sdk#2759 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
github/copilot-sdk#2758 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/copilot-sdk#2709 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
github/copilot-sdk#2673 ·
All issues in github/copilot-sdk
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1152 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jenkinsci/blueocean-plugin#5417 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·