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
{{ message }}
Repository navigation
Commit a4e1fde
Browse filesBrowse the repository at this point in the historyBrowse files
Preserve typed provider wire contracts across streaming responses
Replace public object sequences and finite object payloads with native JSON
protocol values or concrete response DTOs across OpenAI, Anthropic, Cohere and
Bedrock. Preserve event order, explicit nulls, omitted fields, citation shapes,
argument bytes and terminal usage; keep transport encoding generic without
changing runtime AWS envelope dispatch.
Extend real HTTP and official SDK tool rounds, native citations, continuation
replay, image/audio and primitive decision flows. Release the complete repair
batch once as 1.0.4.
Copy file name to clipboardExpand all lines: docs/Features/OpenAiNativeWebSearch.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,3 +187,9 @@ fixtures expose `usage.server_tool_use.web_search_requests`; neither is converte
187
187
Code interpreter fixtures preserve their configured container ID and native outputs. They do not invent
188
188
per-response container sessions or billing duration: container/session accounting requires a separate
189
189
lifecycle contract from the provider rather than a count of code calls.
190
+
191
+
## Native JSON wire mapping
192
+
193
+
`OpenAiWireMapper.ToResponseStreamEvents` returns a lazy `IEnumerable<JsonElement>`; the six same-contract Responses event helpers and Responses text annotations expose native protocol JSON as well. Their known payloads are constructed once through System.Text.Json at the final wire boundary. Event order, sequence numbers, IDs, explicit nulls, citations, terminal output and usage retain their existing protocol meaning.
194
+
195
+
The remaining four single-result helpers expose concrete models: model lists, image-stream events and the two transcription text events. Image completion usage and partial-image indexes retain their mutually exclusive fields; verbose transcription keeps a typed segment collection, currently emitted empty. Decision choices and probability values use native JSON scalars to preserve caller-authored strings and booleans and numeric score indexes. No custom converter or serializer configuration is added. Running-server HTTP/SDK regressions compare streamed terminal data with independent supported responses and retained conversation evidence where applicable.
0 commit comments