Skip to content

[QUESTION] Many Response events are marked internal and cannot be used in 2.2.0 - why? #506

Open
@gaspardpetit

Description

@gaspardpetit

How can we help?

Hello,

I notice that many response events are marked internal in the release of 2.2.0:

 InternalResponseReasoningSummaryPartAddedEvent InternalResponseReasoningSummaryPartDoneEvent InternalResponseReasoningSummaryTextDeltaEvent InternalResponseReasoningSummaryTextDoneEvent InternalResponseImageGenCallGeneratingEvent InternalResponseImageGenCallInProgressEvent InternalResponseImageGenCallPartialImageEvent InternalResponseMCPCallArgumentsDeltaEvent InternalResponseMCPCallArgumentsDoneEvent InternalResponseMCPCallCompletedEvent InternalResponseMCPCallFailedEvent InternalResponseMCPCallInProgressEvent InternalResponseMCPListToolsCompletedEvent InternalResponseMCPListToolsFailedEvent InternalResponseMCPListToolsInProgressEvent InternalResponseReasoningDeltaEvent InternalResponseReasoningDoneEvent InternalResponseReasoningSummaryDeltaEvent InternalResponseReasoningSummaryDoneEvent InternalResponseCodeInterpreterCallCodeDeltaEvent InternalResponseCodeInterpreterCallCodeDoneEvent InternalResponseCodeInterpreterCallCompletedEvent InternalResponseCodeInterpreterCallInProgressEvent InternalResponseCodeInterpreterCallInterpretingEvent 

These map to documented event types, ex. "response.reasoning_summary_part.done", "response.reasoning_summary_text.delta", "response.reasoning_summary_text.delta".

Is there another way to handle these events?

Metadata

Metadata

Assignees

Labels

issue-addressedWorkflow: The OpenAI maintainers believe the issue to be addressed and ready to close.questionCategory: The issue is seeking information about the library or its usage.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions