Python SDK 0.13.0

Python SDK 0.13.0 includes the durable initial-history replay fix (AGNT5-1108), the merged response-wait behavior, and published SDK core 0.3.1 for graceful draining of accepted pull work during intentional shutdown, including Unix SIGTERM (AGNT5-1129).

Upgrade prerequisite

Deploy the AGNT5-1108 runtime compatibility fix before upgrading deployed Python workers. It accepts the session creation event emitted with durable completion. Publishing or installing this package does not deploy that runtime prerequisite.

Breaking changes and migration

• Client.run() and AsyncClient.run() now return accepted 202 pending receipts directly instead of polling detached runs to completion. Check response.is_pending before consuming response.output. Synchronous callers can continue waiting with client.wait_for_result(response.run_id, timeout=...); async callers can use get_status() and get_result() under their own bounded polling policy.
• Gateway response waiting defaults to 300 seconds. Set wait_timeout from zero to 86400 seconds; zero returns after acceptance. Accepted execution continues after waiting ends or the client disconnects.
• Default HTTP operation timeouts allow at least wait_timeout + 10 seconds (310 seconds by default), or the client timeout if longer. Set per-call timeout explicitly when needed.
• Event streams expose stream.wait_expired or stream.detached; chunk-only stream() raises RunError carrying the run ID when response waiting ends. Retain that run ID to retrieve status/results.
• WorkflowProxy.run() reserves timeout and wait_timeout; WorkflowProxy.stream_events() additionally reserves wait_timeout. Pass payload fields with those names through the explicit input dictionary of client.run(..., component_type="workflow") or client.stream_events(...).

The history fix preserves the initial snapshot across replay for runs that record it after upgrade. It cannot reconstruct a missing snapshot for a run already in flight on an older SDK. Fresh runs continue to load the session's latest history.

Dependency and validation

The native extension builds against crates.io agnt5-sdk-core 0.3.1 using its published checksum. Local validation passed a fresh native build, 67 focused tests, and 891 unit tests (13 skipped), plus Ruff, Rust formatting, locked dependency resolution, and source-package inspection. The release workflow builds Linux x86_64 and ARM64 wheels, a macOS ARM64 wheel, and a source distribution.

python SDK 0.12.0

0.12.0 - 2026-09-11

Fixed

• Share activation counters across sibling agents in one invocation (AGNT5-1111), while isolating durable parents and fresh invocations so skipped replayed steps do not shift later model/tool keys.

Changed

• Build the native extension against released agnt5-sdk-core 0.3.0.

• Workers now default to pull when AGNT5_WORKER_MODE is unset or empty.
  Explicit push remains supported; set it before upgrading if your worker
  relies on coordinator-push dispatch (AGNT5-1100).

Python SDK 0.11.2

AGNT5 Python SDK 0.11.2 improves durable workflow state and execution timing.

• Await workflow state writes without blocking the asyncio event loop.
• Route state responses to the dispatch that requested them.
• Measure business execution through the shared native clock while preserving user errors and cancellation if telemetry fails.
• Use the published SDK core 0.2.7 crate for worker session refresh, bounded slot scaling, and execution observations.

Validation: the release changes passed SDK CI, including 865 standalone unit tests; the final registry dependency passed native build validation.

Changes: #39

Published core dependency: #40

v0.11.1

Builds the Python native extension against agnt5-sdk-core 0.2.6.

AGNT5 Python SDK v0.11.0b2

What's Changed

• feat: capture third-party agent runs by @arunreddy in #15
• fix(agent): export skill discovery helpers by @arunreddy in #16
• Enable certificate-bound BYOC identities in Python by @arunreddy in #17
• fix(workflows): avoid blocking event loop on step checkpoint emit by @MalukiMuthusi in #18
• Batch workflow start lifecycle events by @arunreddy in #21
• fix(python): publish portable wheels and preserve durable child context by @arunreddy in #22
• fix(tests): capture async workflow pause events by @arunreddy in #23
• ci: reduce release workflow build time by @arunreddy in #24
• chore(release): prepare Python SDK 0.11.0b2 by @arunreddy in #25

New Contributors

• @MalukiMuthusi made their first contribution in #18

Full Changelog: v0.11.0b0...v0.11.0b2

Python SDK 0.11.0b0

Prerelease for third-party provider capture validation. Adds OpenAI Agents SDK and Google ADK integrations with capture_mode controls. Intended for template and local AGNT5 runtime testing before stable promotion.

Python SDK 0.10.0

What's Changed

• fix(logging): reduce duplicate executor lifecycle logs by @arunreddy in #13
• feat: add durable activation and async worker hardening by @arunreddy in #14

Full Changelog: v0.9.8...v0.10.0

Python SDK 0.9.8

Fixed\n\n- Let the runtime own gateway-managed agent session history so workers do not reload or persist the same conversation through legacy entity storage.\n- Exclude the unresolved assistant tool call that triggered an agent handoff before passing conversation history to the target agent.\n- Make the worker entity-state adapter available while constructing execution contexts.\n\n### Changed\n\n- Align API compatibility and integration tests with the current LM streaming event shape, runtime endpoints, journal event names, and package imports.

Python SDK 0.9.7

What's Changed

• feat(serverless): add component and framework parity by @arunreddy in #11

Full Changelog: v0.9.6...v0.9.7

Python SDK 0.9.6

AGNT5 Python SDK 0.9.6

• Upgrade agnt5-sdk-core to 0.1.6.
• Include the Bedrock event-stream CRC validation fix from AGNT5-822.
• Include the Google provider endpoint and SSE error handling fixes from AGNT5-722.

Validated across Linux x64, Linux ARM64, and macOS ARM64 wheels before release.