This release is a pre-release and may not be stable for production use.
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.
6 maintainers
Metadata
6 maintainers
Release files for agent-framework-foundry-hosting 1.0.0b260813
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agent_framework_foundry_hosting-1.0.0b260813.tar.gz | 27.1 kB | Without provenance | Details for agent_framework_foundry_hosting-1.0.0b260813.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agent_framework_foundry_hosting-1.0.0b260813-py3-none-any.whl | Python 3 | none | any | Details for agent_framework_foundry_hosting-1.0.0b260813-py3-none-any.whl |
Total release size: 55.8 kB
Release files / agent_framework_foundry_hosting-1.0.0b260813.tar.gz
| Download URL | agent_framework_foundry_hosting-1.0.0b260813.tar.gz |
|---|---|
| Size | 27.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de4ca2bf4d0803444b0a8053b5d04dfe2d067550a504341984feb0cb7f0b670f
|
|
BLAKE2b-256 checksum How to use checksums |
bbaaaf6dfc93ba26324f63a58ed1d29b48fce4b46c531872ddd34c9a8e3bf0a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.32 {"installer":{"name":"uv","version":"0.11.32","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / agent_framework_foundry_hosting-1.0.0b260813-py3-none-any.whl
| Download URL | agent_framework_foundry_hosting-1.0.0b260813-py3-none-any.whl |
|---|---|
| Size | 28.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d822ea0f4a1151a7d43d281da9a2141cac8dbcd5810e60afe2b315ee1a815d33
|
|
BLAKE2b-256 checksum How to use checksums |
8dec99441204a9d7276480a853174818d9a6affc51a5d5d37ae841644783d704
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.32 {"installer":{"name":"uv","version":"0.11.32","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for agent-framework-foundry-hosting 1.0.0b260813
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
