Skip to content

Python: Fix stale Foundry Toolbox call IDs #9059

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Eduard van Valkenburg (eavanvalkenburg) merged 2 commits into from
Oct 6, 2026
+558 −112
Merged

Python: Fix stale Foundry Toolbox call IDs #9059

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2a262da
Python: Fix Foundry Toolbox call ID propagation
eavanvalkenburg Oct 5, 2026
c6bca24
Python: Reject runtime-only Toolbox skill headers
eavanvalkenburg Oct 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions python/packages/foundry_hosting/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,11 +107,13 @@ state. This is not an exactly-once guarantee for external tools: make
side-effecting operations idempotent. Legacy unscoped workflow state is not
read; migration starts a fresh Responses chain.

For Responses integrations, use a factory when an MCP connection, provider, tool
cache or client carries request identity. A Toolbox's streamable-HTTP writer
inherits the context of the request that **connects** it; sharing that connection
across callers can retain the first call ID. Create the Toolbox and its skills
provider inside the factory, not at process startup.
For Responses integrations, use a factory when a provider, tool cache, client or
credential carries request identity or needs request-owned cleanup.
`FoundryToolbox` resolves platform headers at each operation boundary and
rebinds its MCP session when that identity changes, so a long-lived Toolbox does
not retain the first request's call ID. The integration samples still construct
it inside the factory because they also own request-scoped clients, credentials
and providers.

Factory agents are entered/exited for each request, including failed entry and
cancellation. `Agent` manages context-managed clients and MCP tools, but it does
Expand Down
240 changes: 191 additions & 49 deletions python/packages/foundry_hosting/agent_framework_foundry_hosting/_toolbox.py
View file
Open in desktop

Large diffs are not rendered by default.

Loading
Loading