 Eduard van Valkenburg
|
f2d02e58b3
|
Python: Add hosting core and Responses channel (#6580)
* Add Python hosting core and Responses channel
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address hosting core review feedback
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Adopt source pyright typing setup for hosting packages
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Cover ResponsesChannel custom path routing
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Align hosting tests with package layout
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix hosting workflow fixture imports in aggregate tests
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Apply useful Responses channel hardening
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix hosting package typing checks
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix hosting pyright under Python 3.11
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Avoid static diskcache dependency in hosting
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix aggregate typing and Docker test resilience
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Simplify local Responses workflow sample
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Clarify generic hosting is not Foundry hosting
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Revert "Clarify generic hosting is not Foundry hosting"
This reverts commit 73b584d919053bed43a258d75dc2b76406e9c181.
* Clarify isolation key source flexibility
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Clarify isolation header reuse boundary
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Support multimodal Responses channel outputs
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Preserve multimodal streaming Responses output
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Stream Responses output items from updates
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Improve Responses streaming output handling
* Tighten Responses channel default option handling
- Restore full option parsing in parse_responses_request: known fields
are remapped (max_output_tokens→max_tokens, parallel_tool_calls→
allow_multiple_tool_calls), transport/session keys excluded, None
values dropped, everything else forwarded as-is so run_hook can
inspect the full set.
- Add a default _strip_options_hook on ResponsesChannel that removes
all parsed options before reaching the agent. Callers cannot inject
generation params (temperature, instructions, tools, …) unless the
host explicitly allows it.
- A custom run_hook replaces the default entirely and receives the
full ChannelRequest.options plus the raw protocol_request.
- Update tests to cover remap, default-strip, and custom-hook paths.
- Clarify host debug-log docstring to match new option flow.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
2026-06-23 20:56:46 +00:00 |
|