Giles Odigwe
7a2b8038cc
* Bump Python package versions for 1.15.0 release Prepare the CHANGELOG-selected Python packages for the 1.15.0 release. Root and core move to 1.15.0; changed stable extensions receive package-specific minor or patch bumps; changed beta packages receive the 260821 stamp; no beta cohort bump is applied. Core dependency floors use the conservative policy for co-released packages. Release validation also adds the six dependency required by the supported Azure Cosmos SDK floor and retains cross-platform-compatible development-tool pins. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248 * Remove hook-only formatting changes Keep the Python 1.15.0 release commit scoped to package metadata, release notes, dependency floors, and the lockfile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248 * Minimize release lockfile changes Restore the upstream PyPI-backed lockfile and retain only package versions and dependency metadata changed by the Python 1.15.0 release. Also preserve the development-tool upgrades already present on main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248 * Retain OpenAI core compatibility floor Keep agent-framework-openai 1.13.1 compatible with core 1.13 because its streaming tool-call index fix uses the existing additional_properties API and does not require core 1.15. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248 * Raise OpenAI version and core floor Bump agent-framework-openai to 1.14.0 and require core 1.15.0 so the new dependency requirement is signaled as a minor release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 98e979bd-1d07-41fd-946d-00db8a93e248
Foundry Hosting
This package provides the integration of Agent Framework agents and workflows with the Foundry Agent Server, which can be hosted on Foundry infrastructure.
State store
Local persistence
Outside the Foundry hosting environment, state is persisted as JSON files under
~/.agentserver/state_stores by default. Set AGENTSERVER_STATE_ROOT to use a
different root directory; the files will be written to its state_stores
subdirectory instead.
Each logical store is saved as one JSON file whose name is a URL-safe Base64 encoding of the store name. For example:
- Agent sessions:
YWdlbnRfc2Vzc2lvbnM.json - Function approvals:
ZnVuY3Rpb25fYXBwcm92YWxz.json - Workflow checkpoints: one file per context, encoded from
checkpoints/<context_id>
Read more about the Foundry durable state store in the developer guide.
User isolation
When hosted on Foundry, the default state stores automatically isolate data by the platform user ID supplied with each request. Sessions, workflow checkpoints, and function approvals written for one user cannot be read or modified by another user. No additional partitioning configuration is required when using the default stores.
Agent Sessions
ResponsesHostServer persists the Agent Framework AgentSession durably. By default it
uses the FoundryAgentSessionStore, backed by Foundry storage when hosted and file-based
storage locally. Stored sessions are scoped under agent_sessions.
See the custom storage provider sample for an example that uses an in-memory session store locally and Azure Cosmos DB when hosted.
Workflow checkpoints
ResponsesHostServer persists workflow checkpoints durably. By default, it uses the
FoundryCheckpointStore, backed by Foundry storage when hosted and file-based storage
locally. Stored checkpoints are scoped under checkpoints.
Function approvals
ResponsesHostServer persists function approvals durably. By default, it uses the
FoundryFunctionApprovalStore, backed by Foundry storage when hosted and file-based
storage locally. Stored approvals are scoped under function_approvals.