40 Commits

• Simplify Python hosting core (#6492)

  Remove linking, multicast, durable delivery, and host push machinery from the v1 hosting core. Keep those scenarios in a proposed follow-up ADR and update channel packages, samples, docs, tests, and workspace metadata around the smaller host/channel contract.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-06-12 08:34:08 +02:00
  36ce0950e4
• Python: feat(python): cross-channel hosting improvements (endpoint paths, Activity push, Telegram/Teams fixes) (#6307)

  * Update hosting channel endpoint paths
  
  Treat channel paths as concrete endpoint paths so built-in channels can be mounted at their defaults or at the app root without sample-specific subclasses. Update docs, tests, and the Foundry Telegram Invocations sample accordingly.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Add push support to ActivityProtocolChannel
  
  Implement the ChannelPush protocol so the Activity Protocol channel can
  receive cross-channel fan-out (ResponseTarget.all_linked) and echo_input
  replay as a non-originating destination:
  
  - Add push() that reconstructs a proactive Bot Framework activity (bot/user
    swap) from the stored conversation reference and POSTs it to
    /v3/conversations/{id}/activities.
  - Record a ChannelIdentity (service_url, conversation, bot, user, channel_id,
    locale) on ChannelRequest.identity so the host registers the channel under
    its isolation key for fan-out resolution.
  - Route the streaming path through deliver_response so Activity-originated
    turns broadcast like Telegram/Discord.
  - Add tests for push delivery, service_url validation, ChannelPush instance
    check, and inbound identity recording.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Don't delete Telegram webhook on shutdown by default
  
  The TelegramChannel deleted its webhook on shutdown in webhook mode. During
  a rolling redeploy the new revision registers the webhook on startup, then
  the old revision's shutdown deletes it, silently breaking inbound delivery
  until the next boot. setWebhook is overwriting/idempotent, so startup
  re-asserts the webhook every boot and no teardown is needed.
  
  Add a delete_webhook_on_shutdown flag (default False) so teardown is opt-in
  for ephemeral deployments, and leave the webhook in place otherwise.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix Activity channel streaming on non-Teams channels (405 on updateActivity)
  
  The Activity Protocol channel streamed replies the Teams way: POST a
  placeholder, then PUT-edit it as tokens arrive. Only Teams supports the
  updateActivity REST op; Web Chat, Direct Line and the Emulator return
  405 Method Not Allowed on the PUT, so the user saw only the placeholder.
  
  Gate the placeholder+edit flow on edit-capable channels (msteams). Other
  channels now buffer the stream and POST a single final message, mirroring
  the non-streaming path's fan-out and response-hook semantics. Also add a
  defensive 405 fallback inside the Teams edit loop so an unexpected 405
  can never strand the user on the placeholder.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(hosting-activity-protocol): don't parse Teams inline attachment content as a URI
  
  Teams message activities include a text/html attachment whose inline
  `content` is raw HTML (not a URL). _parse_activity fell back to
  `attachment["content"]` and passed it to Content.from_uri, raising
  ContentError ("URI must contain a scheme") and failing the whole turn,
  so Teams users got no response.
  
  Only treat `contentUrl` as a URI, require an absolute scheme, and skip
  unparseable attachments defensively instead of failing the message.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * feat(hosting-activity-protocol): native slash-command dispatch for Teams/Activity
  
  Add a commands= parameter to ActivityProtocolChannel that intercepts a
  leading /command (after stripping the bot's own @mention) and dispatches
  to ChannelCommand handlers, mirroring the Telegram channel. Unknown
  commands fall through to the agent. The channel run_hook is applied to
  command requests so handlers observe the same resolved isolation key as
  ordinary messages, and handler errors are swallowed (200, no Bot Service
  retry of non-idempotent commands).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * feat(hosting): silent attributed Telegram echoes + Teams markdown rendering
  
  - hosting-telegram: send cross-channel input echoes with disable_notification
    (silent) and detect echo payloads so they aren't re-broadcast.
  - hosting-activity-protocol: render outbound + push activities as textFormat
    'markdown' so Teams shows formatted replies (enables per-channel variants).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(hosting-activity-protocol): address PR #6307 review feedback
  
  Consult the host delivery pipeline even for empty streamed replies so
  ResponseTarget.none is honoured and non-originating fan-out is consulted
  instead of always emitting an originating "(no response)" message. Applies
  to both the progressive-edit (Teams) and buffered (Web Chat/Direct Line)
  streaming paths.
  
  Re-validate service_url against the allow-list in push(): the identity is
  read from a persisted store and push runs out-of-band, so the captured
  service_url must be re-checked before a bearer token is sent.
  
  Adds tests for empty-stream host consultation/suppression on both streaming
  paths and for push rejecting a disallowed service_url.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-06-03 16:37:03 +02:00
  e5a6e35843
• Python: add hosting Channels sample apps (#5645)

  * samples(hosting): add hosting Channels sample apps under samples/04-hosting/af-hosting
  
  Adds five end-to-end sample apps under
  ``python/samples/04-hosting/af-hosting/`` that exercise the
  ``agent-framework-hosting`` Channels stack from the simplest single-channel
  case up to a multi-channel deployment with cross-channel identity linking.
  
  Samples (ordered by complexity)
  -------------------------------
  
  * ``foundry_hosted_agent/`` — minimal Responses + Invocations host with a
    Foundry-backed agent and ``FoundryHostedAgentHistoryProvider``.
    ``agd``-deployable; bundles a ``Dockerfile`` and
    ``scripts/vendor-packages.sh`` that copies workspace packages into
    ``_vendor/`` for self-contained builds. ``_vendor/`` is gitignored.
  * ``local_responses/`` — single-channel Responses host with a
    ``run_hook`` that strips caller-supplied options and forces a
    reasoning preset. Demonstrates the hook seam over the uniform
    ``ChannelRequest`` envelope.
  * ``local_responses_workflow/`` — Responses + Invocations exposing a
    three-agent workflow with per-conversation checkpoint storage.
  * ``local_telegram/`` — Responses + Telegram with a ``@tool``,
    ``FileHistoryProvider``, hooks, and a ``ResponseTarget`` multicast
    variant (``call_server_multicast.py``) that pushes a single Responses
    reply to a separate Telegram chat.
  * ``local_identity_link/`` — full surface: Responses + Invocations +
    Telegram + Activity Protocol (Teams) + the ``EntraIdentityLinkChannel``
    sidecar. Resolves per-channel ids onto a single Entra object id so a
    user's history follows them across surfaces.
  
  Notes
  -----
  
  * Samples that use Telegram/Teams via Activity Protocol depend on the
    renamed ``agent-framework-hosting-activity-protocol`` package (see the
    PR-5 series).
  * All samples use ``[tool.uv.sources]`` editable workspace deps, except
    ``foundry_hosted_agent/`` which uses the ``./_vendor/`` self-contained
    layout for ``azd`` Docker builds.
  * Each sample includes a ``README.md`` with run instructions and an
    ``app.py`` ASGI entrypoint plus a ``call_server.py`` client harness.
  
  Depends on the prior hosting PRs (foundry-hosted-agent refactor +
  hosting-core + the per-channel packages). After those merge, this
  branch can be rebased onto ``main`` cleanly.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * samples(hosting): point sample deps at the feature/python-hosting GitHub branch
  
  Switches every sample's ``[tool.uv.sources]`` from in-monorepo
  editable path deps (which only resolve when running inside the
  agent-framework workspace) to git refs targeting the
  ``feature/python-hosting`` branch on
  ``microsoft/agent-framework``. Samples now install standalone outside
  the monorepo while the ``agent-framework-hosting*`` packages are still
  pre-PyPI; once they publish, the ``[tool.uv.sources]`` block can be
  dropped and the declared deps resolve from PyPI.
  
  Cleanup
  -------
  
  * Drops ``foundry_hosted_agent/scripts/vendor-packages.sh``,
    ``_vendor/`` from ``.gitignore``, the ``hooks.prepackage`` block in
    ``azure.yaml`` and the ``COPY _vendor/`` step in the Dockerfile —
    vendoring is no longer needed because git refs make the deps
    network-resolvable from any context.
  * Drops obsolete ``workspace.pyproject.toml`` reference and ``scripts/``
    / ``workspace.pyproject.toml`` entries from
    ``Dockerfile.dockerignore``.
  * Updates the foundry sample's Dockerfile to ``uv sync --no-dev``
    (no ``--frozen``) so it locks fresh against the GitHub-hosted deps
    at build time.
  * Drops every committed ``uv.lock`` because the resolver needs network
    access to ``feature/python-hosting`` to lock — they regenerate the
    first time a user runs ``uv sync`` after the branch lands.
  * Refreshes the per-sample READMEs to mention the GitHub install path
    instead of "in-tree workspace packages".
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * samples(hosting): address PR #5645 review comments
  
  - foundry_hosted_agent/call_server.py: replace hard-coded
    project_endpoint and service_session_id with FOUNDRY_PROJECT_ENDPOINT,
    FOUNDRY_HOSTED_AGENT_NAME, and optional FOUNDRY_HOSTED_SESSION_ID
    environment variables. Session-id is now optional so the sample
    exercises the new-conversation path by default.
  
  - local_identity_link/app.py:
    * make_telegram_hook: apply the reasoning bump regardless of
      identity-link state (the previous early-return on linked chats
      silently dropped the high-effort preset for the very flow the
      sample exists to demonstrate).
    * make_responses_hook: add a prominent DEV-ONLY warning that the
      client-supplied entra_oid shortcut bypasses identity verification
      and must be replaced by a JWT validator in production.
    * /link command: early-return when chat_id is missing instead of
      minting an authorize URL keyed on "telegram:None" (which would
      poison the link store with a binding any future chat_id-less
      update would collapse onto).
    * Switch ENTRA_CERT_PATH / ENTRA_CERT_PASSWORD env vars to the
      longer ENTRA_CERTIFICATE_PATH / ENTRA_CERTIFICATE_PASSWORD names
      that the README already documents.
    * channels: Sequence[Channel] -> list[Channel] (the next line
      appends, which a Sequence type doesn't expose).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * chore(hosting-samples): apply sample formatting
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(hosting-samples): guard command input text
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-05-28 14:57:46 +02:00
  6b822853eb
• Python: Show more authentication methods in Foundry Toolbox MCP (#5719)

  * Show more authentication methods in Foundry Toolbox MCP
  
  * Remove hardcoded toolbox version num
  
  * Add Foundry MCP OAuth consent handling
  
  * Use message instead of the dedicated item type
  
  * Go back to using OAuthConsentRequestOutputItem
  
  * WIP: sample testing
  
  * Update error code
  
  * Address review on Foundry Toolbox MCP samples
  
  Reviewed feedback addressed:
  
  - Drop the branch-pinned `git+https://...@feature/...` entries from
    `04_foundry_toolbox/requirements.txt`; restore the simple comment + `mcp`
    runtime dep. The git pins were only useful while iterating on the PR and
    shouldn't ship. (eavanvalkenburg)
  
  - Fix the `/toolsets/` typo in both `04_foundry_toolbox/README.md` and
    `06_files/README.md`. Verified empirically against the
    research_toolbox in the test workspace: the toolbox MCP gateway lives at
    `/toolboxes/{name}/mcp?api-version=v1` and requires the
    `Foundry-Features: Toolboxes=V1Preview` header. `/toolsets/{name}/mcp`
    returns 403 with `preview_feature_required: Toolsets=V1Preview` (a
    different opt-in feature).
  
  - Wrap `httpx.AsyncClient(...)` in `async with ... as http_client:` in both
    samples so the connection pool is cleaned up. (Copilot reviewer)
  
  - Make the `TOOLBOX_NAME` env var consistent in both samples. Previously the
    tool name silently fell back to `"toolbox"` when `TOOLBOX_NAME` was unset,
    but `resolve_toolbox_endpoint()` still required `TOOLBOX_NAME` and would
    raise `KeyError`. The samples now resolve the endpoint once and derive the
    tool name from the resolved URL when `TOOLBOX_NAME` isn't set, so the
    local tool name always matches the upstream toolbox identity regardless
    of which env var the user set. (Copilot reviewer)
  
  - Rename `_responses.is_consent_error` to `consent_url_from_error`: the
    helper returns `str | None` (the consent URL), not a bool, so the new
    name matches behavior. Update the test class accordingly. (eavanvalkenburg)
  
  - Tighten `_handle_inner_agent`'s lazy-entry catch from `Exception` to
    `AgentFrameworkException`, the type the MCP layer actually wraps consent
    errors in via `MCPStreamableHTTPTool.__aenter__` →
    `ToolExecutionException(inner_exception=mcp_error)`. Network failures,
    cancellations, and other non-framework exceptions now propagate normally
    instead of being briefly caught and re-raised. The test helper
    `_make_consent_error` is updated to use `ToolExecutionException` so it
    matches the real-world wrapping. (eavanvalkenburg)
  
  - Clarify the `github_pat` description in `agent.manifest.yaml` to note
    it's only needed when the PAT-based connection (`github-mcp-pat-conn`)
    is chosen; users selecting the OAuth2 connection (`github-mcp-oauth-conn`)
    can leave it empty. (Copilot reviewer)
  
  Validation: ran both samples end-to-end against a real Foundry toolbox
  (`research_toolbox`) -- the samples connect successfully and the agent
  lists the toolbox's MCP tools (`api_specs___fetch_azure_rest_api_docs`,
  etc.). `uv run poe test -P foundry_hosting` passes (119 tests), pyright +
  mypy clean.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * docs: fix broken Foundry samples link in 04_foundry_toolbox README
  
  The previous URL pointed to an old location of the toolbox supported-scenarios
  doc; the doc moved to /samples/python/hosted-agents/SUPPORTED_TOOLBOX_SCENARIOS.md
  and the old /samples/python/toolbox/azd path now 404s.
  
  Caught by the markdown-link-check CI step.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Tao Chen · 2026-05-20 12:00:38 +00:00
  d74d26c917
• [BREAKING] Python: Enable instrumentation by default (#5865)

  * Enable instrumentation by default
  
  * Update samples
  
  * Optimization when span is not recording
  
  * Address Copilot comments
  
  * Revert uv.lock
  
  * Add warning
  
  * Formatting
  
  * Fix mypy
  
  * Add disable_instrumentation() with sticky user-intent semantics
  
  Add a public disable_instrumentation() entry point so users can explicitly opt
  out of Agent Framework telemetry, with a sticky-disable flag that makes the
  user's intent "leading" — no framework code path (foundry's
  configure_azure_monitor, configure_otel_providers, enable_instrumentation,
  enable_sensitive_telemetry, or direct OBSERVABILITY_SETTINGS.enable_*
  writes) can re-enable instrumentation until the user explicitly clears the
  disable with enable_instrumentation(force=True) /
  enable_sensitive_telemetry(force=True).
  
  Also addresses the two remaining unresolved review threads on the PR:
  1. test_observability_settings_defaults_instrumentation_true pins the new
     "ENABLE_INSTRUMENTATION defaults to True when env unset" behavior.
  2. test_enable_instrumentation_reads_env_sensitive_data restores coverage
     for the post-import load_dotenv() fallback path.
  
  Implementation:
  - ObservabilitySettings.enable_instrumentation / enable_sensitive_data become
    properties backed by _enable_*. While _user_disabled is True, the getters
    return False and the setters drop True writes (defense in depth so third-
    party writes can't subvert the disable).
  - Public is_user_disabled read-only property lets integrations (e.g. foundry's
    configure_azure_monitor) cheaply check the disable state without poking at
    privates.
  - enable_instrumentation() and enable_sensitive_telemetry() short-circuit with
    an info log when disabled; gain a force=True kwarg that clears the disable.
  - configure_otel_providers() still creates providers / exporters / views so a
    later force-enable can use them, but logs an info message when called while
    disabled.
  - Foundry's FoundryChatClient.configure_azure_monitor and
    FoundryAgent.configure_azure_monitor early-return when the user has
    disabled, so Azure Monitor's global providers aren't installed unnecessarily.
  
  Tests: 11 new tests covering default-on, env re-read at call time, sticky
  behavior against each re-enable surface (enable_instrumentation,
  enable_sensitive_telemetry, configure_otel_providers, direct attribute
  writes), force=True override, re-arming the disable, and the __all__ export.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * docs: document disable_instrumentation() and force=True paths
  
  Add a "Disabling instrumentation" section to the observability sample README
  that walks through:
  
  - The distinction between the ENABLE_INSTRUMENTATION env var (initial,
    non-sticky) and disable_instrumentation() (process-wide, sticky).
  - Why the sticky semantics matter: framework integrations like
    FoundryChatClient.configure_azure_monitor() can call
    enable_instrumentation() as part of their setup, and the user's opt-out
    needs to win.
  - All five surfaces guarded by the sticky disable (property reads, public
    enable functions, configure_otel_providers, direct attribute writes,
    is_user_disabled-aware integrations).
  - The force=True escape hatch on both enable_instrumentation() and
    enable_sensitive_telemetry().
  - How third-party integrations should consult OBSERVABILITY_SETTINGS.is_user_disabled.
  - The limits of the disable (does not tear down existing providers /
    in-flight spans / third-party instrumentation, does not persist across
    processes).
  
  Cross-links the new section from the ENABLE_INSTRUMENTATION row in the env
  vars table.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * docs: soften disable_instrumentation() overclaim about telemetry guarantees
  
  Replace 'no telemetry will be emitted no matter what' (which is too strong,
  since callers can still pass force=True or mutate private attributes) with
  language framing the disable as a user-intent contract that library and
  framework code is expected to honor: the framework actively short-circuits
  the public enable paths, force=True and private-attribute writes are
  acknowledged as out-of-contract escape hatches that integrations should
  not use on the user's behalf.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * docs: correct observability Dependencies section
  
  - opentelemetry-sdk is no longer a hard dependency; it is lazily imported by
    create_resource(), create_metric_views(), and configure_otel_providers()
    with a clear ImportError when missing. Day-to-day instrumentation works
    with opentelemetry-api alone provided some other component configures the
    global OpenTelemetry providers (Azure Monitor, an APM agent, application
    bootstrap, etc.).
  - opentelemetry-semantic-conventions-ai is no longer used anywhere in the
    source; remove it from the listed dependencies.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * docs: replace stale observability migration guide with current PR's only relevant migration
  
  The old guide documented the move away from setup_observability(otlp_endpoint=...)
  which was an earlier-release API change unrelated to this PR and stale enough that
  it's more confusing than helpful at this point. Replace it with a short note on the
  single migration this PR introduces: callers of
  enable_instrumentation(enable_sensitive_data=True) should switch to
  enable_sensitive_telemetry(). Cross-link to the Disabling instrumentation section
  for the rare 'force on without enabling sensitive data' use case where
  enable_instrumentation() still applies.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Tao Chen · 2026-05-20 11:52:08 +00:00
  72a6157c6a
• Python: feat: add agent-framework-monty (Monty-backed CodeAct provider) (#5915)

  * Python: feat: add agent-framework-monty (Monty-backed CodeAct)
  
  New alpha package that wraps pydantic-monty (a Rust-based Python
  interpreter) behind the same CodeAct API surface as
  agent-framework-hyperlight, so users can swap providers with minimal
  code change.
  
  Public API (agent_framework_monty):
  - MontyCodeActProvider — ContextProvider that injects a run-scoped
    execute_code tool plus dynamic CodeAct instructions.
  - MontyExecuteCodeTool — standalone FunctionTool for mixed-tool agents
    or manual static wiring.
  - FileMount / FileMountInput / MountMode — public types mirroring the
    Hyperlight names, with Monty's mode (read-only/read-write/overlay)
    and write_bytes_limit on FileMount.
  
  Constructor kwargs (both classes) mirror Hyperlight where possible:
  tools, approval_mode, workspace_root, file_mounts; plus a Monty-only
  resource_limits forwarding ResourceLimits to Monty.start().
  
  Filesystem flow:
  - workspace_root auto-mounts at /input (read-write), matching Hyperlight.
  - file_mounts accepts string shorthand, (host, mount) tuple, or
    FileMount with mode + write cap.
  - Files written under read-write mounts are scanned post-execution and
    returned as Content.from_data items (mirrors Hyperlight /output).
  - overlay mounts buffer writes in-memory; read-only mounts reject writes.
  
  Internals:
  - _monty_bridge.InlineCodeBridge ports the inline (non-durable) bridge
    from anthonychu/maf-codeact-monty-python; handles FunctionSnapshot /
    FutureSnapshot pause/resume, dispatches direct typed calls + the
    call_tool fallback, forwards mount/limits to Monty.start(...).
  - generate_type_stubs emits per-tool stubs so Monty's `ty` type-checker
    rejects bad calls before any host tool runs.
  
  Alpha-policy compliance (per python-package-management skill):
  - Added agent-framework-monty = { workspace = true } to root
    pyproject.toml.
  - Added row to python/PACKAGE_STATUS.md.
  - Added monty entry under Experimental in python/AGENTS.md.
  - NOT added to core[all]; NO agent_framework.monty lazy shim (deferred
    to beta promotion).
  
  Samples (three sets, import from agent_framework_monty directly):
  - samples/02-agents/context_providers/code_act/monty_code_act.py
    (provider pattern) + updated local README.
  - samples/02-agents/tools/monty_code_interpreter/ (standalone +
    manual-wiring + README).
  - samples/04-hosting/foundry-hosted-agents/responses/11_monty_codeact/
    (full hosted-agent layout with uv-based pyproject.toml + Dockerfile,
    Azure Monitor wiring via APPLICATIONINSIGHTS_CONNECTION_STRING +
    enable_instrumentation, ENABLE_INSTRUMENTATION and
    ENABLE_SENSITIVE_DATA env vars). The alpha wheel is vendored into
    ./wheels/ (gitignored) via vendor-wheel.sh; new row added to the
    parent Responses-API README.
  
  Tests:
  - 28 hermetic unit tests (stubbed pydantic_monty).
  - 18 integration tests marked @pytest.mark.integration, auto-skipped
    when pydantic_monty is unimportable; exercise the real Monty
    runtime: print round-trip, last-expression value, direct typed
    tool dispatch, call_tool fallback, async tool, asyncio.gather
    parallelism, ty type-check rejection, OS blocked by default,
    workspace_root read+write capture, read-only / overlay mount
    semantics, resource_limits.max_duration_secs abort, approval
    gating end-to-end, full Agent run with a scripted chat client.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix: monty FileMount test compares against the normalized POSIX path
  
  The shorthand string mount goes through _normalize_mount_path, which
  rewrites Windows drive letters like 'C:\\Users\\...' into
  '/C:/Users/...' (POSIX-style). The Windows CI runners surfaced this
  because tmp_path resolves to a backslashed Windows path; the test was
  comparing against the raw str(host_a) instead of the normalized form.
  
  Compare against _normalize_mount_path(str(host_a)) so the assertion is
  platform-independent.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix: address PR #5915 review feedback
  
  - _execute_code_tool docstring: clarify that the Monty backend supports
    scoped filesystem access via workspace_root / file_mounts (blocked by
    default).
  - _to_monty_mount: import pydantic_monty lazily through load_monty so
    missing-dependency errors surface as the same actionable RuntimeError
    the rest of the package raises (not a bare ImportError at module load).
    Renamed _load_monty -> load_monty for the same reason.
  - _python_type_repr: emit None for type(None) instead of Any, and
    normalize both typing.Union[...] and PEP-604 X | Y to PEP-604 syntax
    so Optional[X] / Union[..., None] / -> None signatures round-trip
    correctly through ty validation. Added a regression test.
  - _PrintCollector: track a running character count instead of
    recomputing sum(len(c) for c in self.chunks) per callback. Eliminates
    the O(n^2) cost on print-heavy code.
  - Instructions: mention that the value of the final expression is also
    returned alongside captured stdout (matches actual behavior).
  - 11_monty_codeact Dockerfile: pin ghcr.io/astral-sh/uv to 0.11.6
    instead of :latest for reproducible builds.
  - 11_monty_codeact README: replace the bare "see parent README" pointer
    with sample-specific steps (./vendor-wheel.sh + uv sync + uv run),
    since the sample uses pyproject.toml + a vendored wheel rather than
    requirements.txt.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: sample: 11_monty_codeact installs agent-framework-monty from PyPI
  
  Drop the vendored-wheel scaffolding now that agent-framework-monty is on
  PyPI as an alpha (1.0.0a*) release:
  
  - pyproject.toml: remove [tool.uv.sources] override; keep [tool.uv]
    prerelease = "allow" so uv pulls the alpha automatically.
  - Dockerfile: drop the COPY wheels/ step.
  - README: drop the ./vendor-wheel.sh setup step and the
    not-yet-on-PyPI warning.
  - Delete vendor-wheel.sh and the gitignored wheels/ directory.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix(monty): harden post-execution file capture against symlink escape
  
  Same class of issue as the MSRC-reported Hyperlight finding: the
  post-execution capture walked workspace_root with Path.rglob() +
  is_file() + read_bytes() - all of which follow symlinks. An attacker
  who controls the workspace (cloned repo, extracted archive, shared
  workspace) could pre-place `workspace/leak.txt -> /etc/passwd` or
  `workspace/outside_dir -> /etc/` and have host files surface as
  captured Content items.
  
  Monty's mount layer already rejects symlink reads from inside the
  sandbox across all three modes (verified empirically), so the runtime
  path was safe. This commit closes the post-execution scan path.
  
  Changes:
  - New `_iter_real_files(root)` walker that uses iterdir() +
    is_symlink() to skip symlinks at every directory level and yields
    only real files. Replaces the previous `host_root.rglob("*")` calls
    in both `_snapshot_writable_mounts` and `_capture_written_files`.
  - Use `Path.lstat()` instead of `Path.stat()` so size/mtime can never
    be taken from a symlink target.
  - Three new integration tests reproducing the MSRC attack shape
    against the workspace_root flow: symlink-to-file outside workspace,
    symlink-to-directory outside workspace, and a guard ensuring
    legitimate sandbox writes are still captured when symlinks are
    present.
  
  Per user request, hyperlight is untouched in this commit (separate fix).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix(monty): skip symlink regression tests when unsupported
  
  Apply the same Windows-CI safety guard as the hyperlight fix in PR #5919:
  the three symlink integration tests create symlinks via Path.symlink_to(),
  which fails with OSError / NotImplementedError on unprivileged Windows
  runners. Add a local _symlinks_supported helper (mirroring the one in
  packages/core/tests/core/test_skills.py) and pytest.skip when symlinks
  aren't available, so the tests no longer fail for environment reasons.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix(monty): address PR #5915 follow-up review feedback
  
  - _invoke_tool: drop the inspect.iscoroutinefunction(...) branch and
    always `await self.tool_map[name](**kwargs)`. Every entry in
    tool_map is `partial(FunctionTool.invoke, skip_parsing=True)` and
    FunctionTool.invoke is `async def`, so the branching was dead code -
    and on Python versions affected by cpython#98590,
    iscoroutinefunction(partial(bound_async_method, ...)) returns False,
    causing the bridge to take the asyncio.to_thread path, return an
    unawaited coroutine, and surface it as a JSON-serialization failure
    for every tool call. Added a regression test
    test_invoke_tool_awaits_partial_wrapped_async_method.
  
  - generate_type_stubs: skip tools whose name is not a valid Python
    identifier or is a Python keyword. FunctionTool.name has no upstream
    validation, so a name like "weird-name" produced a syntax error in
    the stubs and a name like "broken\n    pass\nasync def injected"
    would inject arbitrary stub source. Non-identifier names stay
    reachable via `call_tool("weird-name", ...)` at runtime; they just
    don't get type-checked stubs. Added regression test
    test_generate_type_stubs_skips_non_identifier_tool_names.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-05-20 00:35:23 +00:00
  4609535e22
• Python: Improve the handling of intermediate outputs for workflows and orchestrations (#5623)

  * Improve the handling of intermediate outputs for workflows and orchestrations
  
  * Address PR review feedback on intermediate output forwarding
  
  - Switch workflow.as_agent() forwarding to an explicit allowlist of {output,
    intermediate, data, request_info} so orchestration-internal events
    (group_chat, handoff_sent, magentic_orchestrator) stay inside the workflow
    instead of leaking into agent responses via str(data) coercion.
  - Stop raising on intermediate AgentResponseUpdate in non-streaming run();
    surface the partial as a Message with text_reasoning content. The defensive
    raise still applies to terminal output events, where Update payloads would
    corrupt message ordering.
  - Extend the DevUI workflow-event mapper so intermediate yields wrapping
    plain strings, Messages, and list[Message] render as visible output items
    instead of generic completed-trace events.
  - Add orchestration coverage for GroupChat, Handoff, and Magentic builders
    (default vs intermediate_outputs=True; structural where end-to-end is heavy).
  
  * Lift output-designation policy into a value type
  
  Replace the ``Workflow._output_executors`` list and the
  ``RunnerContext.should_label_as_intermediate`` Protocol method with a single
  immutable ``OutputDesignation`` value type owned by ``Workflow``. Thread the
  designation as a parameter through the existing call chain (Runner ->
  EdgeRunner -> Executor -> WorkflowContext) so ``yield_output`` consults the
  threaded snapshot directly rather than calling back into the runner context.
  
  Removes the ``InProcRunnerContext._workflow`` back-reference and the
  ``WorkflowBuilder.build()`` assignment that wired it up. Adds the public
  predicate ``Workflow.is_terminal_executor(executor_id)`` for external
  observers; ``OutputDesignation`` itself stays package-internal.
  
  Key decisions
  - ``OutputDesignation.designated`` is ``frozenset[str] | None`` -- ``None``
    preserves legacy "every yield is type='output'" behavior, any frozenset
    (including empty) opts into strict mode. The ``DeprecationWarning`` for
    legacy mode at build time is unchanged.
  - ``output_designation`` is an optional parameter on ``Runner``,
    ``EdgeRunner.send_message``, ``EdgeRunner._execute_on_target``,
    ``Executor.execute``, ``Executor._create_context_for_handler``, and
    ``WorkflowContext.__init__``. Each defaults to legacy ``OutputDesignation()``
    so direct callers (Azure Functions ``CapturingRunnerContext``,
    ``test_runner`` recording fixtures) keep working without ceremony.
  - The workflow-level filter in ``_run_core`` reads ``self._output_designation``
    live, preserving today's semantics where mutating the designation after
    build still affects subsequent runs (used by two existing tests).
  - ``Workflow.to_dict()`` continues to emit ``"output_executors":
    list[str] | None`` (sorted from the frozenset). Checkpoint format unchanged.
  
  Files changed
  - _workflow.py: add ``OutputDesignation`` dataclass; replace
    ``_output_executors`` with ``_output_designation``; add
    ``is_terminal_executor``; delete ``_should_yield_output_event``.
  - _runner_context.py: drop ``should_label_as_intermediate`` Protocol method
    and ``InProcRunnerContext`` impl; drop ``_workflow`` back-reference.
  - _workflow_builder.py: remove ``context._workflow = workflow`` assignment.
  - _runner.py, _edge_runner.py, _executor.py, _workflow_context.py: thread
    ``output_designation`` parameter through the call chain.
  - tests/workflow/test_output_designation.py (new): three-state coverage of
    the value type plus the public predicate delegation.
  - tests/workflow/test_workflow_builder.py, test_validation.py,
    test_workflow.py, test_runner.py and
    orchestrations/tests/test_orchestration_intermediate_vs_terminal.py:
    switch probes from ``_output_executors`` set checks to
    ``get_output_executors`` / ``is_terminal_executor``; update two
    post-build mutation tests to set ``_output_designation`` instead.
  
  Verification
  - core/tests/workflow/, orchestrations/tests/, azurefunctions/tests/:
    1119 passed, 42 skipped, 2 xfailed.
  - ``uv run poe lint``: clean.
  - ``uv run poe typing``: only the pre-existing
    ``_AGENT_FORWARDED_EVENT_TYPES`` pyright warning from 394bcd607 remains.
  
  Notes for next iteration
  - The builder's own ``_output_executors`` attribute (``list[Executor |
    SupportsAgentRun]``) is intentionally untouched; the issue scoped the
    rename to the workflow attribute.
  - Adjacent review candidates (twin ``WorkflowAgent`` translators,
    ``_AGENT_FORWARDED_EVENT_TYPES`` kind classifier,
    ``_event_origin_context`` ContextVar removal, ``WorkflowEvent`` ADT
    split, legacy-mode removal) remain out of scope.
  
  * Add explicit workflow output designation
  
  Key decisions
  
  - Extend the internal OutputDesignation value type from terminal-only membership to output/intermediate/hidden classification. Legacy mode remains outputs=None, so workflows built without output_executors or intermediate_executors still label every yield_output as type='output'.
  
  - WorkflowBuilder now accepts intermediate_executors. Providing either designation enters explicit mode; output executors emit output, intermediate executors emit intermediate, and unlisted yield_output payloads are hidden from caller-facing events while remaining in executor_completed data.
  
  - Empty explicit designation, duplicate entries, overlaps, unknown executors, and designated executors without workflow output annotations fail build validation. Existing orchestration builders pass intermediate-capable participants through intermediate_executors to preserve current intermediate_outputs behavior until participant-oriented designation lands.
  
  Files changed
  
  - packages/core/agent_framework/_workflows/_workflow.py, _workflow_builder.py, _workflow_context.py, _validation.py, _events.py
  
  - packages/core/tests/workflow/test_output_designation.py, test_output_executors_contract.py, test_strict_mode_event_labeling.py, test_validation.py, test_workflow.py, test_workflow_agent_intermediate.py
  
  - packages/orchestrations/agent_framework_orchestrations/_sequential.py, _concurrent.py, _group_chat.py, _magentic.py
  
  - packages/core/AGENTS.md
  
  Verification
  
  - uv run pytest packages/core/tests/workflow packages/orchestrations/tests packages/devui/tests/devui/test_mapper.py -q
  
  - uv run pytest packages/azurefunctions/tests -q
  
  - uv run poe lint
  
  - uv run poe typing fails only on pre-existing packages/core/agent_framework/_workflows/_agent.py _AGENT_FORWARDED_EVENT_TYPES private-use pyright error.
  
  Notes for next iteration
  
  - issues/03-core-workflow-explicit-designation.md was moved to issues/done but issues/ remains untracked and intentionally excluded from this commit.
  
  - Slice 4 should tighten workflow.as_agent() mapping for hidden emissions and streaming-only update payloads; Slice 5 should replace orchestration intermediate_outputs with participant-oriented designation.
  
  * Tighten workflow-as-agent output mapping
  
  Key decisions
  
  - Treat AgentResponseUpdate as a streaming-only payload across the workflow.as_agent() adapter, so non-streaming agent runs now reject both terminal output and intermediate workflow events carrying updates.
  - Keep streaming classification behavior explicit: terminal update payloads remain normal text content, while intermediate update payloads are rewritten to text_reasoning content.
  - Add explicit-mode coverage proving hidden yield_output emissions do not appear in non-streaming AgentResponse messages or streaming AgentResponseUpdate chunks.
  
  Files changed
  
  - packages/core/agent_framework/_workflows/_agent.py
  - packages/core/tests/workflow/test_workflow_agent_intermediate.py
  
  Verification
  
  - uv run pytest packages/core/tests/workflow/test_workflow_agent_intermediate.py -q
  - uv run pytest packages/core/tests/workflow/test_workflow_agent.py packages/core/tests/workflow/test_workflow_agent_intermediate.py -q
  - uv run pytest packages/core/tests/workflow packages/orchestrations/tests packages/devui/tests/devui/test_mapper.py -q
  - uv run poe lint
  - uv run poe typing fails only on the pre-existing packages/core/agent_framework/_workflows/_agent.py _AGENT_FORWARDED_EVENT_TYPES private-use pyright error.
  
  Blockers or notes for next iteration
  
  - issues/04-workflow-as-agent-output-mapping.md was moved to issues/done/ but issues/ remains untracked and intentionally excluded from this commit.
  - Slice 5 should replace orchestration intermediate_outputs with participant-oriented designation.
  
  * Add orchestration participant output designation
  
  Key decisions
  
  - Replace orchestration intermediate_outputs with participant-oriented output_participants and intermediate_participants across Sequential, Concurrent, GroupChat, Magentic, and Handoff builders.
  - Keep synthetic final executors terminal by default for Concurrent, GroupChat, and Magentic; keep Sequential's final participant terminal by default; keep Handoff participants terminal by default.
  - Centralize participant designation validation for empty explicit designation, duplicates, overlaps, and unknown participants, then map validated participants to workflow output/intermediate executors.
  
  Files changed
  
  - packages/orchestrations/agent_framework_orchestrations/_participant_designation.py
  - packages/orchestrations/agent_framework_orchestrations/_sequential.py
  - packages/orchestrations/agent_framework_orchestrations/_concurrent.py
  - packages/orchestrations/agent_framework_orchestrations/_group_chat.py
  - packages/orchestrations/agent_framework_orchestrations/_magentic.py
  - packages/orchestrations/agent_framework_orchestrations/_handoff.py
  - packages/orchestrations/tests/test_orchestration_intermediate_vs_terminal.py
  - packages/orchestrations/tests/test_magentic.py
  
  Blockers or notes for next iteration
  
  - issues/05-orchestration-participant-designation.md was moved to issues/done/ but issues/ remains untracked and intentionally excluded from this commit.
  - Slice 7 should migrate samples and docs away from intermediate_outputs to the new participant designation API.
  - uv run poe typing still fails only on the pre-existing packages/core/agent_framework/_workflows/_agent.py _AGENT_FORWARDED_EVENT_TYPES private-use pyright error.
  
  * Migrate samples to explicit output designation
  
  Key decisions
  
  - Replace sample usage of the removed orchestration intermediate_outputs boolean with participant-oriented intermediate_participants designation.
  - Update raw workflow guidance to show output_executors together with intermediate_executors, and document that unlisted yields are hidden in explicit designation mode.
  - Keep orchestration final outputs terminal while streaming designated participant responses as intermediate progress, including workflow.as_agent() samples where intermediates map to text_reasoning content.
  - Refresh workflow and orchestration README guidance plus the changelog reference so public docs no longer point users at intermediate_outputs.
  
  Files changed
  
  - CHANGELOG.md
  - packages/orchestrations/README.md
  - samples/README.md
  - samples/03-workflows/README.md
  - samples/03-workflows/control-flow/intermediate_vs_terminal_outputs.py
  - samples/03-workflows/orchestrations/README.md
  - samples/03-workflows/orchestrations/group_chat_agent_manager.py
  - samples/03-workflows/orchestrations/group_chat_philosophical_debate.py
  - samples/03-workflows/orchestrations/group_chat_simple_selector.py
  - samples/03-workflows/orchestrations/magentic.py
  - samples/03-workflows/orchestrations/magentic_human_plan_review.py
  - samples/03-workflows/orchestrations/sequential_chain_only_agent_responses.py
  - samples/03-workflows/agents/group_chat_workflow_as_agent.py
  - samples/03-workflows/agents/magentic_workflow_as_agent.py
  - samples/03-workflows/agents/sequential_workflow_as_agent.py
  - samples/semantic-kernel-migration/orchestrations/group_chat.py
  - samples/semantic-kernel-migration/orchestrations/magentic.py
  
  Blockers or notes for next iteration
  
  - issues/07-samples-and-docs-explicit-output-designation.md was moved to issues/done/ but issues/ remains untracked and intentionally excluded from this commit.
  - issues/06-devui-intermediate-event-rendering.md remains present and appears already satisfied by existing DevUI mapper/tests from the prior implementation slice.
  - PRD-explicit-workflow-output-designation.md remains untracked and intentionally excluded from this commit.
  
  * Render DevUI intermediate workflow outputs
  
  Key decisions
  
  - Preserve workflow output designation metadata on visible DevUI output messages and text deltas so intermediate/data emissions remain distinguishable from terminal output.
  - Render intermediate workflow message items in the execution timeline using executor metadata, while excluding them from the final workflow result aggregation.
  - Keep terminal output message rendering unchanged and retain legacy data events on the intermediate compatibility path.
  
  Files changed
  
  - packages/devui/agent_framework_devui/_mapper.py
  - packages/devui/frontend/src/components/features/workflow/execution-timeline.tsx
  - packages/devui/frontend/src/components/features/workflow/workflow-view.tsx
  - packages/devui/frontend/src/types/openai.ts
  - packages/devui/tests/devui/test_mapper.py
  
  Blockers or notes for next iteration
  
  - issues/06-devui-intermediate-event-rendering.md was moved to issues/done/ but issues/ remains untracked and intentionally excluded from this commit.
  - PRD-explicit-workflow-output-designation.md remains untracked and intentionally excluded from this commit.
  - uv run poe typing still fails only on the pre-existing packages/core/agent_framework/_workflows/_agent.py _AGENT_FORWARDED_EVENT_TYPES private-use pyright error.
  
  * Fix mypy
  
  * Clarify orchestration participant output config
  
  * Rename participant output kwargs for clarity
  
  output_participants -> final_output_from, intermediate_participants ->
  intermediate_output_from. The old names read like categories of
  participant; the new names make it clear the kwarg designates which
  participants' outputs surface as final vs. intermediate events.
  
  * Rename core workflow output kwargs with deprecation shim
  
  Adds final_output_from / intermediate_output_from as canonical kwargs on
  Workflow and WorkflowBuilder. Old output_executors / intermediate_executors
  kwargs continue to work but emit DeprecationWarning via a shared coalesce
  helper that also rejects supplying both. Wire-format keys in to_dict()
  stay as output_executors / intermediate_executors so checkpoint
  compatibility is preserved.
  
  Internal call sites in orchestrations and samples updated to the new
  names so users following sample code learn the canonical vocabulary;
  legacy callers still work with a one-shot warning.
  
  * Suppress pyright reportPrivateUsage on cross-module sentinel import
  
  * Update docstrings
  
  * Propagate sub-workflow intermediate outputs, fix handoff/sequential intermediate-only designation, and shore up tests, sample, and docstrings around the intermediate output contract.
  
  * Add canonical workflow output_from selection
  
  Key decisions:\n- Make output_from the canonical workflow-output allow-list and keep output_executors/final_output_from as deprecated compatibility aliases.\n- Treat empty output_from/intermediate_output_from lists as explicit selections and keep validation responsible for empty, duplicate, overlap, and unknown selections.\n- Remove the branch-only public intermediate_executors WorkflowBuilder kwarg while preserving legacy wire keys in to_dict().\n\nFiles changed:\n- packages/core/agent_framework/_workflows/_workflow.py\n- packages/core/agent_framework/_workflows/_workflow_builder.py\n- packages/core/agent_framework/_workflows/_workflow_context.py\n- packages/core/agent_framework/_workflows/_agent.py\n- packages/core/agent_framework/_workflows/_agent_executor.py\n- packages/core/tests/workflow/* output-selection coverage updates\n- packages/core/AGENTS.md\n- issues/done/001-canonical-list-based-output-selection.md\n\nBlockers/notes:\n- Orchestration builders still pass final_output_from internally; follow-up issue 004 should migrate them to output_from.\n- Legacy omitted-selection behavior and explicit all/all_other literals are left for issues 002 and 003.
  
  * Add explicit all workflow output selection
  
  Key decisions:
  - Treat output_from='all' as an explicit workflow-output selection sentinel and expand it at build time to executors with declared workflow output types.
  - Keep omitted output selections in legacy all-output mode with a deprecation warning that names output_from and intermediate_output_from and points to output_from='all'.
  - Reject intermediate_output_from='all' at construction because the all-output literal is output-only for this issue.
  
  Files changed:
  - packages/core/agent_framework/_workflows/_workflow_builder.py
  - packages/core/tests/workflow/test_output_executors_contract.py
  - issues/done/002-explicit-all-output-and-legacy-migration.md
  
  Blockers/notes:
  - all_other intermediate-output selection remains for issue 003.
  - Workflow-as-agent/orchestration parity remains for issue 004.
  
  * Add all-other intermediate output selection
  
  Key decisions:
  - Treat intermediate_output_from='all_other' as an explicit intermediate-output selection sentinel and expand it at build time after the workflow graph is complete.
  - Expand all_other to output-capable executors not selected by output_from; omitted or empty output_from selects no workflow outputs, while output_from='all' leaves an empty intermediate selection.
  - Keep output_from='all_other' invalid so all_other remains intermediate-output-only and runtime classification still receives concrete executor-id sets.
  
  Files changed:
  - packages/core/agent_framework/_workflows/_workflow_builder.py
  - packages/core/tests/workflow/test_output_executors_contract.py
  - issues/done/003-all-other-intermediate-output-selection.md
  
  Blockers/notes:
  - Workflow-as-agent and orchestration parity remains for issue 004.
  - Full documentation updates remain for issue 005.
  
  * Add orchestration output selection parity
  
  Key decisions:
  - Expose output_from on sequential, concurrent, group chat, handoff, and magentic builders while keeping final_output_from as a deprecated compatibility alias.
  - Resolve orchestration participant selections through the same explicit rules as workflows: output_from='all', intermediate_output_from='all_other', hidden unselected participant payloads, and overlap/duplicate/unknown/invalid-literal validation.
  - Continue preserving documented orchestration defaults by always designating each pattern's terminal internal executor where applicable.
  
  Files changed:
  - packages/orchestrations/agent_framework_orchestrations/_participant_output_config.py
  - packages/orchestrations/agent_framework_orchestrations/_sequential.py
  - packages/orchestrations/agent_framework_orchestrations/_concurrent.py
  - packages/orchestrations/agent_framework_orchestrations/_group_chat.py
  - packages/orchestrations/agent_framework_orchestrations/_handoff.py
  - packages/orchestrations/agent_framework_orchestrations/_magentic.py
  - packages/orchestrations/agent_framework_orchestrations/_orchestration_request_info.py
  - packages/orchestrations/tests/test_orchestration_intermediate_vs_terminal.py
  - issues/done/004-workflow-as-agent-and-orchestration-parity.md
  
  Blockers/notes:
  - Full documentation and sample migration wording remains for issue 005.
  - Existing tests that intentionally use final_output_from now emit the new deprecation warning.
  
  * Document workflow output selection contract
  
  Key decisions:
  - Use Workflow Output and Intermediate Output as the developer-facing terms for selected caller-facing emissions.
  - Document output_from and intermediate_output_from as the canonical API, with output_from as an allow-list and unselected payloads hidden unless explicitly selected as intermediate.
  - Add scenario and invalid-selection tables for workflow and orchestration docs, including legacy omission warnings, output_from='all', intermediate_output_from='all_other', list selections, invalid literals, overlap, duplicates, unknown selections, and empty explicit selections.
  - Migrate samples away from final_output_from and output_executors except where compatibility aliases are explicitly documented.
  
  Files changed:
  - packages/core/AGENTS.md
  - packages/orchestrations/README.md
  - packages/orchestrations/agent_framework_orchestrations/_handoff.py
  - packages/orchestrations/agent_framework_orchestrations/_sequential.py
  - samples/03-workflows/README.md
  - samples/03-workflows/control-flow/intermediate_vs_terminal_outputs.py
  - samples/03-workflows/human-in-the-loop/agents_with_approval_requests.py
  - samples/03-workflows/orchestrations/README.md
  - samples/04-hosting/foundry-hosted-agents/responses/05_workflows/main.py
  - scripts/sample_validation/create_dynamic_workflow_executor.py
  - issues/done/005-document-output-selection-contract.md
  
  Blockers/notes:
  - Direct full Ruff on scripts/sample_validation/create_dynamic_workflow_executor.py still reports pre-existing docstring/print/line-length issues outside this docs migration; syntax-focused checks for changed files pass.
  - No remaining AFK issue files are present under issues/.
  
  * Latest updates
  
  * Typing fixes
  
  * Cleanup

  Evan Mattson · 2026-05-19 00:15:25 +00:00
  3bbc81554b
• Python: New Foundry Hosted Agents samples: RAG, Skills, and Memory (#5822)

  * WIP: Add rag sample; need deployment testing
  
  * Rag sample ready
  
  * Add Foundry Skills sample
  
  * WIP: Foundry memory
  
  * Done: Foundry Memory
  
  * Address Copilot comments
  
  * Fix README
  
  * Restore uv.loack

  Tao Chen · 2026-05-15 17:31:57 +00:00
  da308f5f1e
• Python: Fix A2A v1.0 non-streaming response and sample runtime issues (#5849)

  - Fix non-streaming empty response by accumulating intermediate WORKING
    status updates and flushing them when an empty terminal event arrives
  - Fix sample agent_executor.py to enqueue Task before status events
    (required by v1.0 ActiveTask validation)
  - Fix create_jsonrpc_routes() calls to include required rpc_url param
  - Fix TYPE_CHECKING imports in sample agent_definitions.py
  - Add tests for non-streaming content accumulation behavior
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-05-14 22:28:02 +00:00
  68357b0250
• Python: [BREAKING] Migrate agent-framework-a2a to a2a-sdk v1.0 (#5752)

  * Python: Migrate agent-framework-a2a to a2a-sdk v1.0
  
  Upgrade the a2a-sdk dependency from v0.3.x to v1.0.0 and migrate all
  source, tests, samples, and documentation to the v1.0 API.
  
  Key changes:
  - Dependency: a2a-sdk>=1.0.0,<2 (was >=0.3.5,<0.3.24)
  - Types are now protobuf-based: Part replaces TextPart/FilePart/DataPart
  - Enums use SCREAMING_SNAKE_CASE (e.g. TaskState.TASK_STATE_COMPLETED)
  - Roles: Role.ROLE_AGENT, Role.ROLE_USER
  - Client: SendMessageRequest wrapper, subscribe() replaces resubscribe()
  - Server: A2AStarletteApplication replaced by Starlette + route factories
  - DefaultRequestHandler now requires agent_card parameter
  - TaskUpdater: final parameter removed, add_artifact gains last_chunk
  - AgentCard.url removed; use supported_interfaces with AgentInterface
  - Stream yields StreamResponse with WhichOneof('payload')
  
  Closes #5661
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review: validate fallback URL, remove unused task_id vars
  
  - Raise ValueError with clear message when transport negotiation fails
    and no fallback URL is available (neither url arg nor supported_interfaces)
  - Remove unused task_id local in status_update branch
  - Inline artifact_event.task_id directly in artifact_update branch
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-05-11 22:46:12 +00:00
  4ad96b64e7
• Python: Add support for function approval flow in Foundry hosted agent (#5666)

  * Add support for function approval flow in Foundry hosted agent
  
  * Address comments
  
  * Address comments
  
  * Address comments

  Tao Chen · 2026-05-07 14:55:26 +00:00
  213491da66
• Python: Remove bespoke Foundry toolbox helpers; standardize on MCP for toolbox consumption (#5671)

  * Remove Foundry toolbox helpers; standardize on MCP for toolbox consumption
  
  - Remove RawFoundryChatClient.get_toolbox() and its fetch_toolbox import
  - Remove fetch_toolbox, select_toolbox_tools, get_toolbox_tool_name,
    get_toolbox_tool_type, FoundryHostedToolType, ToolboxToolSelectionInput
    from agent_framework_foundry._tools
  - Remove ExperimentalFeature.TOOLBOXES from _feature_stage.py (no consumers)
  - Drop toolbox re-exports from agent_framework_foundry/__init__.py and
    agent_framework.foundry namespace
  - Update _sanitize_foundry_response_tool docstring to remove toolbox framing;
    sanitization logic itself is unchanged
  - Update _agent.py docstring: 'toolbox-fetched MCP' → 'hosted MCP'
  - Delete tests/test_toolbox.py (all tests covered removed helpers)
  - Update test_foundry_chat_client.py: rename/redoc tests that mentioned
    toolbox but test sanitization that remains
  - Delete foundry_chat_client_with_toolbox.py (bespoke toolbox API sample)
  - Delete foundry_toolbox_context_provider.py (relied on select_toolbox_tools)
  - Rename foundry_chat_client_with_toolbox_mcp.py →
    foundry_chat_client_with_toolbox.py (canonical MCP pattern)
  - Rewrite 04_foundry_toolbox/main.py to use MCPStreamableHTTPTool
  - Update provider/README, context_providers/README, 04_foundry_toolbox/README
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(samples): update 06_files sample to consume toolbox via MCP (#5670)
  
  Replace removed get_toolbox/select_toolbox_tools APIs with
  MCPStreamableHTTPTool, using allowed_tools=["code_interpreter"] to
  select only the code interpreter from the toolbox endpoint.
  
  Update .env.example and README to use FOUNDRY_TOOLBOX_ENDPOINT
  instead of TOOLBOX_NAME.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(foundry): remove non-existent toolbox helper APIs from README (#5670)
  
  Remove the 'fetch, optionally filter, and pass tools directly' pattern
  from the FoundryChatClient toolbox documentation, as select_toolbox_tools
  and get_toolbox were removed. Only the MCP endpoint pattern is documented.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(foundry): remove residual toolbox docstring references and reproduction report
  
  Remove REPRODUCTION_REPORT.md (workflow artifact that should not be committed),
  and update two remaining docstring references that still said 'toolbox reads'
  /'toolbox definition' after the toolbox helpers were removed.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: Remove bespoke Foundry toolbox helpers; standardize on MCP for toolbox consumption
  
  Fixes #5670
  
  * fix(#5670): resolve toolbox endpoint from TOOLBOX_NAME fallback; add namespace regression tests
  
  - Add _resolve_toolbox_endpoint() helper in 04_foundry_toolbox/main.py and
    06_files/main.py that prefers FOUNDRY_TOOLBOX_ENDPOINT but falls back to
    deriving the MCP URL from FOUNDRY_PROJECT_ENDPOINT + TOOLBOX_NAME — fixing
    the startup KeyError when agents are deployed via azd provision (which injects
    TOOLBOX_NAME, not FOUNDRY_TOOLBOX_ENDPOINT).
  - Update 04_foundry_toolbox/.env.example to use FOUNDRY_TOOLBOX_ENDPOINT
    (consistent with 06_files).
  - Add TOOLBOX_NAME env var to 06_files/agent.yaml so deployed agents have it
    available for the fallback derivation.
  - Update both READMEs to document the two ways to supply the toolbox endpoint.
  - Add test_foundry_namespace_no_longer_exposes_toolbox_helpers() with negative
    assertions for FoundryHostedToolType, get_toolbox_tool_name,
    get_toolbox_tool_type, and select_toolbox_tools — guarding against accidental
    re-introduction of removed symbols.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix(samples): fail fast on empty FOUNDRY_TOOLBOX_ENDPOINT; add unit tests
  
  Addresses review feedback for #5670:
  
  - In _resolve_toolbox_endpoint() (04_foundry_toolbox/main.py and
    06_files/main.py) change the walrus-operator check from a truthy
    test to an explicit 'is not None' guard.  An explicitly set empty
    string now raises ValueError immediately with a clear message
    instead of silently falling through to the fallback URL
    construction.
  
  - Add tests/samples/hosting/test_toolbox_endpoint.py covering both
    sample modules:
      (a) FOUNDRY_TOOLBOX_ENDPOINT set → returned as-is
      (b) FOUNDRY_TOOLBOX_ENDPOINT set to empty string → ValueError
      (c) fallback constructs URL from FOUNDRY_PROJECT_ENDPOINT + TOOLBOX_NAME,
          stripping trailing slashes
      (d) neither variable group set → KeyError
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback: remove extraneous test and docstring content
  
  - Remove test_foundry_namespace_no_longer_exposes_toolbox_helpers (no longer warranted)
  - Remove docstring from _agent.py _prepare_tools_for_openai (extraneous)
  - Trim _chat_client.py _prepare_tools_for_openai docstring to one-liner (toolbox references no longer relevant)
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix: remove remaining extraneous docstring from RawFoundryChatClient._prepare_tools_for_openai
  
  Address review comment on PR #5671: reviewer noted the description
  isn't warranted now that toolbox helpers have been removed. Matches
  the pattern in RawFoundryAgentChatClient which has no docstring.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Evan Mattson · 2026-05-06 23:56:16 +00:00
  e56e6dad4d
• Python: Fix hyperlight WasmSandbox cross-thread Drop and harden hosted-agent sample (#5603)

  * update hyperlight to beta and move samples, add hosted agent sample
  
  * Python: Fix hyperlight WasmSandbox cross-thread Drop and harden sample
  
  Root cause: when a worker-side closure raised, the exception's __traceback__
  retained frame locals that included the partially constructed PyO3 sandbox.
  Future.result() re-raised that exception on the caller thread, and when the
  caller's exception was eventually GC'd the frame locals were released
  off-thread, dec_ref'ing the unsendable sandbox from the wrong thread and
  tripping the PyO3 panic
  '_native_wasm::WasmSandbox is unsendable, but is being dropped on another thread'.
  
  Fix:
  * Add _SandboxWorker._run_on_worker which catches every exception on the
    worker, drops __traceback__ there, deletes the original exception, and
    re-raises a fresh instance on the caller thread. initialize and execute
    route through it; dispose keeps its bare-submit semantics.
  * Add an opt-in diagnostic module _drop_diagnostic (no-op unless
    HYPERLIGHT_TRACE_DROPS=1) that installs a sys.unraisablehook and dumps
    owner-thread + per-thread stacks on any future cross-thread unsendable
    Drop. Useful for triaging similar PyO3 regressions.
  * Tests: cross-thread invocation, traceback-leak isolation, _SandboxEntry
    attribute-shape check, and a stale-reference stress test driven through
    asyncio.to_thread.
  
  Sample (samples/04-hosting/foundry-hosted-agents/responses/06_hyperlight_codeact):
  * Dockerfile installs agent-framework-* from in-tree source with python/ as
    build context so unreleased fixes can be validated end-to-end.
  * call_server.py pins the Responses API version.
  * main.py enables include_detailed_errors=True so future tool failures
    surface the actual exception text instead of a bare 'Error: Function
    failed.' string.
  * README.md documents the in-tree-package build and the Hyperlight
    hypervisor requirement (/dev/kvm on Linux, MSHV on Windows). Hosted
    environments without hypervisor passthrough surface 'No Hypervisor was
    found for Sandbox'; this is a hosting constraint, not a hyperlight bug.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: remove _drop_diagnostic from hyperlight package
  
  The diagnostic module was useful while bisecting the cross-thread Drop bug,
  but it is no longer needed now that _SandboxWorker._run_on_worker prevents
  the panic at the source.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: address PR review feedback on hyperlight
  
  - Use lazy agent_framework.hyperlight import in sample main.py.
  - Env-driven endpoint (FOUNDRY_AGENT_ENDPOINT) in call_server.py; remove personal URLs.
  - Align agent.yaml model deployment with manifest (gpt-4.1-mini).
  - Tighten Dockerfile requirements guard; drop dangling deploy.ps1 reference.
  - Preserve exception args when sanitizing tracebacks in _run_on_worker.
  - Add public _SandboxWorker.is_alive(); update test to avoid private attr.
  - Add namespace coverage tests for agent_framework.hyperlight lazy loader.
  - Add prominent note: Foundry hosted-agent runtime does not yet support
    Hyperlight (no hypervisor exposed); container works locally with /dev/kvm.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: bump hyperlight-sandbox dependencies to 0.4.x
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: renumber hyperlight codeact sample to 08
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Coerce worker exception args to strings for cross-thread safety
  
  Stringify exc.args on the worker thread before propagating, so any
  PyO3 unsendable object captured in args (e.g. via a caller-supplied
  callback or underlying SDK) cannot be Dropped on the calling thread.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * moved sample
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-05-05 10:06:16 +00:00
  57c901a245
• Python: Add hosted agent sample with observability (#5608)

  * Add hosted agent sample with observability
  
  * Address comments
  
  * Remove unneeded changes
  
  * Update README

  Tao Chen · 2026-05-04 22:31:47 +00:00
  5a087885a2
• Python: docs(python/samples): recommend uv venv and document Windows ensurepip hang workaround (#5508)

  * docs(samples): recommend uv venv to avoid Windows ensurepip hang
  
  Replace bare 'python -m venv .venv' with 'uv venv .venv' as the
  recommended approach in azure_functions and foundry-hosted-agents
  READMEs. Add a note explaining that python -m venv can hang
  indefinitely on Windows with Microsoft Store Python due to a known
  ensurepip issue.
  
  This matches the pattern already used in a2a/README.md which uses
  uv run exclusively.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: docs(python/samples): recommend `uv venv` and document Windows ensurepip hang workaround
  
  Fixes #5401
  
  * fix: correct Windows venv activation commands in foundry-hosted-agents README (#5401)
  
  Split the Windows activation section into separate PowerShell (.venv\Scripts\Activate.ps1)
  and Command Prompt (.venv\Scripts\activate.bat) instructions, replacing the incorrect
  extensionless `Activate` path.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback for #5401: Python: [Samples][Python] `python -m venv` hangs on Windows — READMEs should recommend uv or document workaround
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Evan Mattson · 2026-05-04 04:46:17 +00:00
  6582926af5
• Python: Add redis[asyncio] to requirements.txt for streaming samples (#5509)

  * fix: add redis[asyncio] to streaming sample requirements.txt
  
  Both streaming samples import redis.asyncio in redis_stream_response_handler.py
  but neither included redis in their requirements.txt, causing ModuleNotFoundError
  on fresh installs.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: Add `redis[asyncio]` to requirements.txt for streaming samples
  
  Fixes #5396
  
  * Revert unrelated formatting and cleanup changes
  
  Revert formatting-only edits in sample files and unrelated cleanup
  (unused import removal, __all__ reordering) that were accidentally
  included in the redis dependency fix (issue #5396).
  
  The only intended changes for this PR are the Redis dependency
  additions to requirements.txt files for the streaming samples.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback for #5396: Python: [Samples][Python] redis package missing from requirements.txt in streaming samples
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Evan Mattson · 2026-05-04 04:45:07 +00:00
  0507179d3b
• Python: Add sample for hosted agent with files (#5596)

  * Add sample for hosted agent with files
  
  * Update python/samples/04-hosting/foundry-hosted-agents/responses/06_files/README.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/samples/04-hosting/foundry-hosted-agents/responses/06_files/README.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/samples/04-hosting/foundry-hosted-agents/responses/06_files/README.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/samples/04-hosting/foundry-hosted-agents/responses/04_foundry_toolbox/README.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/samples/04-hosting/foundry-hosted-agents/responses/06_files/README.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Improve README
  
  * Address comments
  
  ---------
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

  Tao Chen · 2026-05-01 18:40:42 +00:00
  18293ffb31
• Python: Reduce flaky integration tests and improve CI signal quality (#5454)

  * Enable Ollama integration tests in CI and rename report to Integration Test Report
  
  - Install Ollama, cache models (qwen2.5:0.5b + nomic-embed-text), and start
    server in the Misc integration job for both workflow files
  - Set OLLAMA_MODEL and OLLAMA_EMBEDDING_MODEL env vars so the 5 Ollama tests
    are no longer skipped
  - Rename Flaky Test Report to Integration Test Report throughout (job names,
    artifact names, cache keys, file names, script titles/docstrings)
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Bump Ollama model to qwen2.5:1.5b for better instruction following
  
  The 0.5b model was too small to reliably follow simple prompts like
  'Say Hello World', causing test assertion failures. The 1.5b model
  follows instructions more reliably while still being small enough
  for fast CI pulls (~1GB).
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Re-enable reliable streaming integration tests
  
  Remove the hard skip on test_03_reliable_streaming tests that was
  temporarily disabled for instability investigation. CI infrastructure
  (Azurite, DTS emulator, Redis, func CLI) is already in place.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Re-enable skipped Functions/DurableTask tests and bump timeout to 480s
  
  - Remove hard skips from 4 tests in test_11_workflow_parallel.py
  - Remove hard skip from test_conditional_branching in test_06_dt_multi_agent_orchestration_conditionals.py
  - Increase pytest --timeout from 360 to 480 for Functions+DurableTask CI job
  - Updated in both python-merge-tests.yml and python-integration-tests.yml
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Re-skip failing Functions/DurableTask tests with specific root causes
  
  - test_11_workflow_parallel (4 tests): xdist worker crashes during execution
  - test_conditional_branching: orchestration fails with RuntimeError, not a timeout
  - Keep 480s timeout bump for remaining Functions tests
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix auth routing in samples 06/11: api_key -> credential for Azure OpenAI
  
  Both samples passed a bearer token provider via api_key= which caused the
  client to route to api.openai.com instead of Azure OpenAI, resulting in
  401 Unauthorized. Changed to credential= which correctly triggers Azure
  routing and picks up AZURE_OPENAI_ENDPOINT from the environment.
  
  - samples/azure_functions/11_workflow_parallel/function_app.py: 1 fix
  - samples/durabletask/06_multi_agent_orchestration_conditionals/worker.py: 2 fixes
  - Re-enable 4 parallel workflow tests and 1 conditional branching test
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Re-skip parallel workflow tests: xdist worker distribution issue
  
  The 4 parallel workflow tests crash because xdist worksteal distributes
  them across separate workers, each spawning its own func process against
  shared emulators. Auth fix (api_key->credential) was valid and stays.
  test_conditional_branching now passes with the auth fix.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix E501 line-too-long in azurefunctions parallel test skip reasons
  
  Wrap skip reason strings to stay within 120 char line limit.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Add retry logic and port-conflict fix for Ollama CI setup
  
  - Kill any auto-started Ollama before launching serve (fixes port
    conflict: 'address already in use')
  - Retry ollama pull up to 3 times with 15s backoff (fixes 429 rate
    limit failures)
  - Applied to both python-merge-tests.yml and python-integration-tests.yml
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix flaky integration tests and re-enable skipped tests
  
  - Foundry agent: add allow_preview=True to custom client test
  - Foundry hosting: raise max_output_tokens 50->200, add temperature,
    relax assertion in test_temperature_and_max_tokens
  - Foundry embedding: update skip reason with root cause (endpoint mismatch)
  - OpenAI file search: fix vector store indexing race condition by polling
    file_counts before querying; fix get_streaming_response -> get_response(stream=True)
  - Azure OpenAI file search: remove skip (transient 500 resolved)
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Remove temperature from foundry hosting test (unsupported by CI model)
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Stabilize Ollama tool call integration tests with no-arg function
  
  Use a no-argument greet() function instead of hello_world(arg1) for
  integration tests. The 1.5B model in CI is unreliable at generating
  correct tool call arguments, causing 'Argument parsing failed' errors.
  A no-arg function eliminates this flakiness entirely.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Increase reliable streaming test timeouts from 30s to 60s
  
  The LLM call through Azure OpenAI + Redis streaming pipeline can exceed
  30s in CI due to cold starts or throttling. Raise to 60s to reduce
  flaky timeouts while still bounded by pytest's 120s per-test limit.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Re-enable workflow parallel tests with xdist_group marker
  
  The tests were skipped because xdist distributes module tests across
  workers, each spawning their own func process (port conflicts). Adding
  xdist_group forces all tests in this module onto a single worker so
  the module-scoped function_app_for_test fixture works correctly.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Revert "Re-enable workflow parallel tests with xdist_group marker"
  
  This reverts commit 455c28da62.
  
  * Rename flaky_report to integration_test_report and add try/finally cleanup
  
  - Rename scripts/flaky_report/ to scripts/integration_test_report/ to
    reflect expanded scope beyond flaky-test detection
  - Update workflow references in both CI files
  - Wrap file search integration tests in try/finally to ensure vector
    store cleanup runs even on test failure or timeout
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix Ollama pull failure propagation and Azure OpenAI vector store readiness
  
  - Ollama CI: fail the step immediately if model pull fails after 3
    retries instead of silently proceeding to tests
  - Azure OpenAI file search: add the same vector-store readiness polling
    that was applied to the non-Azure OpenAI tests, preventing eventual
    consistency race conditions
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * remove load_dotenv from test file
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-05-01 00:41:39 +00:00
  540193ccef
• Python: Update hosting agent samples + fixes (#5485)

  * Update foundry hosting samples
  
  * Add file data type support
  
  * Fix file content and add more tests
  
  * Fix README
  
  * Address comments
  
  * Fix int tests
  
  * remove temp

  Tao Chen · 2026-04-28 04:24:05 +00:00
  88347f6494
• Python: Add requirements.txt and .env.example to the a2a/ sample for pip-based setup (#5510)

  * Add requirements.txt and .env.example to a2a sample
  
  Beginners following the a2a/ sample had no pip-based install path:
  the directory lacked requirements.txt and .env.example, unlike every
  other 04-hosting/ sample.
  
  - Add requirements.txt with editable local package paths matching the
    pattern used in azure_functions/ and similar hosting samples
  - Add .env.example documenting FOUNDRY_PROJECT_ENDPOINT, FOUNDRY_MODEL,
    and A2A_AGENT_HOST
  - Update README Quick Start to cover both pip (.venv) and uv workflows
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: Add `requirements.txt` and `.env.example` to the `a2a/` sample for pip-based setup
  
  Fixes #5395
  
  * fix(a2a-sample): address PR review feedback for issue #5395
  
  - Remove 'from repo root' wording from Option B uv heading in README
    to avoid contradicting the 'run from this directory' instruction
  - Fix A2A_AGENT_HOST default in .env.example from 5001 to 5000 to match
    function-tools flow; add clarifying comments about port usage
  - Add note for pip users explaining they can replace 'uv run python'
    with 'python' once the virtual environment is activated
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback for #5395: Python: [Samples][Python] a2a/ sample missing requirements.txt — beginners cannot install dependencies
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Evan Mattson · 2026-04-27 22:22:07 +00:00
  9b22ecd119
• Python: update FoundryAgent for hosted agent sessions (#5447)

  * fixes to FoundryAgent to connect to new hosted agents
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * fix mypy
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * Python: remove Foundry service session helpers
  
  Remove the public hosted-agent service session CRUD helpers from FoundryAgent and drop the related feature-stage inventory entry.
  
  Update the hosted-agent sample to create and delete service sessions directly through the preview AIProjectClient APIs, and tighten a few test harnesses surfaced by full workspace validation.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix from merge
  
  * fix hosted env detection
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * reverted sample update
  
  * fix tests and code
  
  Co-authored-by: Copilot <copilot@github.com>
  
  * remove aenter
  
  * skipping some tests
  
  Co-authored-by: Copilot <copilot@github.com>
  
  ---------
  
  Co-authored-by: Copilot <copilot@github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-04-24 09:25:03 +00:00
  62e02da698
• Python: feat: Add Agent Framework to A2A bridge support (#2403)

  * feat: Add Agent Framework to A2A bridge support
  
  - Implement A2A event adapter for converting agent messages to A2A protocol
  - Add A2A execution context for managing agent execution state
  - Implement A2A executor for running agents in A2A environment
  - Add comprehensive unit tests for event adapter, execution context, and executor
  - Update agent framework core A2A module exports and type stubs
  - Integrate thread management utilities for async execution
  - Add getting started sample for A2A agent framework integration
  - Update dependencies in uv.lock
  
  This integration enables agent framework agents to communicate and execute within the A2A (Agent to Agent) infrastructure.
  
  * fix: Update references from agent_thread_storage to _agent_thread_storage in A2A executor tests
  
  * Refactor A2A agent framework and improve code structure
  
  - Reordered imports in various files for consistency and clarity.
  - Updated `__all__` definitions to maintain a consistent order across modules.
  - Simplified method signatures by removing unnecessary line breaks.
  - Enhanced readability by adjusting formatting in several sections.
  - Removed redundant comments and example scenarios in the execution context.
  - Improved handling of agent messages in the event adapter.
  - Added type hints for better clarity and type checking.
  - Cleaned up test cases for better organization and readability.
  
  * fix: Lint fix new line added
  
  * test: Add unit tests for AgentThreadStorage and InMemoryAgentThreadStorage
  
  * refactor: Update type hints to use new syntax for Union and List
  
  * fix: Validate RequestContext for context_id and message before execution
  
  * Refactor tests and remove A2aExecutionContext references
  
  - Deleted the test file for A2aExecutionContext as it is no longer needed.
  - Updated A2aExecutor tests to remove dependencies on A2aExecutionContext and adjusted method calls accordingly.
  - Modified event adapter tests to use ChatMessage instead of AgentRunResponseUpdate.
  - Removed A2aExecutionContext from imports in agent_framework.a2a module and updated type hints accordingly.
  
  * Refactor A2AExecutor tests and remove event adapter
  
  - Updated test cases to use A2AExecutor instead of A2aExecutor for consistency.
  - Removed mock_event_adapter fixture and related tests as A2aEventAdapter is deprecated.
  - Consolidated event handling tests into TestA2AExecutorEventAdapter.
  - Adjusted imports in various files to reflect the removal of deprecated components.
  - Ensured all references to A2aExecutor are updated to A2AExecutor across the codebase.
  
  * refactor: Remove AgentThreadStorage and InMemoryAgentThreadStorage classes from threads and tests
  
  * feat: A2AExecutor to have its own override able save and get threads methods for persistent storage.
  
  * fix: linter bugs
  
  * removed unnecessary changes form core package
  
  * new line added
  
  * Refactor A2AExecutor tests and update imports
  
  - Consolidated mock agent fixtures in test_a2a_executor.py to simplify agent mocking.
  - Removed redundant tests related to thread storage and agent types, focusing on A2AExecutor's core functionality.
  - Updated test assertions to reflect changes in message handling with new Message and Content classes.
  - Enhanced integration tests to ensure compatibility with the new agent framework structure.
  - Added A2AExecutor to the module exports in __init__.py and __init__.pyi for better accessibility.
  
  * Update A2A documentation: enhance usage examples for A2AAgent and A2AExecutor
  
  * Updated uv lock
  
  * Fix metadata assertion in TestA2AExecutorHandleEvents and reorder load_dotenv call in agent_framework_to_a2a.py
  
  * Update agent card configuration: add default input and output modes, and fix agent creation method
  
  * Fix assertion for metadata in TestA2AExecutorHandleEvents
  
  * Fix formatting issues in TestA2AExecutorExecute and TestA2AExecutorIntegration
  
  * Enhance A2AExecutor documentation with examples and clarify agent execution process
  
  * Revert uv lock to main
  
  * Refactor A2AExecutor: Improve formatting and streamline constructor parameters
  
  * Apply suggestions from code review
  
  Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>
  
  * Refactor A2AExecutor to use SupportsAgentRun and enhance logging; update agent framework sample for flight and hotel booking capabilities
  
  * Enhance A2AExecutor with streaming support and custom run arguments; update tests for initialization and execution scenarios
  
  * Enhance A2AExecutor event handling with streamed artifact tracking; update tests for new behavior
  
  * Refactor A2AExecutor to enforce type hints for stream and run_kwargs attributes
  
  * Refactor A2AExecutor and tests: replace AsyncMock with MagicMock for response stream handling; clean up imports in agent_framework_to_a2a.py
  
  * refactor: streamline imports and improve code readability across multiple files
  
  * feat: enhance A2AExecutor cancel method with context validation and fixed review comments
  
  * feat: implement get_uri_data utility function for extracting base64 data from data URIs and update references
  
  * fix: update import path for get_uri_data utility function in A2AExecutor and A2AAgent
  
  * fix: correct error message handling in A2AExecutor and update test assertions
  
  ---------
  
  Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>

  Shubham Kumar · 2026-04-24 08:35:40 +00:00
  b00465d7be
• Python: fix(foundry): reconcile toolbox hosted-tool payloads with Responses API (#5414)

  * fix(foundry): reconcile toolbox hosted-tool payloads with Responses API
  
  * docs(foundry): update create_sample_toolbox docstring to reflect all tools created

  Evan Mattson · 2026-04-22 17:43:26 +00:00
  fffd0acb3e
• Python: Foundry hosted agent V2 (#5379)

  * Python: Wrapper + Samples 1st (#5177)
  
  * Experiment
  
  * Update dependency and add non streaming
  
  * Add more samples
  
  * Rename samples
  
  * Add invocations
  
  * Comments 1
  
  * Comments 2
  
  * Comments 3
  
  * Improve README
  
  * Add local shell sample
  
  * WIP: Add eval and memory samples
  
  * Update user agent prefix
  
  * Update user agent prefix doc
  
  * Update dependency (#5215)
  
  * Add tests and more content types (#5235)
  
  * Add tests
  
  * fix tests and sample
  
  * Fix formatting
  
  * Remove function approval contents
  
  * Python: Refine samples and upgrade packages (#5261)
  
  * Refine samples and upgrade pacakges
  
  * Upgrade to a new package that fixes a bug
  
  * Update model env var
  
  * Move samples (#5281)
  
  * Python: Upgrade agentserver packages (#5284)
  
  * Upgrade agentserver packages
  
  * Fix new types
  
  * Python: Add special handling for workflows (#5298)
  
  * Add special handling for workflows
  
  * Address comments
  
  * Improve samples (#5372)
  
  * Python: Add more types (#5378)
  
  * Add more type supports
  
  * Upgrade packages
  
  * Remove TODOs in README
  
  * Fix README
  
  * Comments and mypy
  
  * User agent scoped
  
  * Fix README
  
  * Fix pre commit
  
  * Fix pre commit 2
  
  * Fix pre commit 3
  
  * Fix pre commit 4
  
  * Fix pre commit 5
  
  * Fix pre commit 6
  
  * Add azure-monitor-opentelemetry to dev deps
  
  Fixes Samples & Markdown CI failure. The PR's new transitive dep on
  azure-monitor-opentelemetry-exporter (via azure-ai-agentserver-core) makes
  pyright resolve the azure.monitor.opentelemetry namespace, flipping the
  check_md_code_blocks diagnostic for `configure_azure_monitor` from
  reportMissingImports (filtered) to reportAttributeAccessIssue (not filtered).
  Installing the umbrella azure-monitor-opentelemetry package in dev makes
  pyright resolve the symbol correctly, matching the install guidance the
  observability README already gives users.
  
  ---------
  
  Co-authored-by: Evan Mattson <evan.mattson@microsoft.com>

  Tao Chen · 2026-04-21 05:21:27 +00:00
  ce8b6305d8
• Python: [BREAKING] update to v1.0.0 (#5062)

  * updates to final deprecated pieces and versions
  
  * fix mypy
  
  * fix readme links

  Eduard van Valkenburg · 2026-04-02 15:26:30 +00:00
  3446eb8d5d
• Python: [BREAKING] Standardize model selection on model (#4999)

  * Refactor Anthropic model option and provider clients
  
  Rename the Anthropic client model option from model_id to model, add provider-specific Anthropic wrappers for Foundry, Bedrock, and Vertex, and expose them through the Anthropic, Foundry, Amazon, and Google namespaces. Update core option handling, docs, samples, and tests accordingly.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix Anthropic skills sample typing
  
  Cast the Anthropic beta client to Any in the skills sample so the pre-commit sample pyright check no longer fails on beta skills and files endpoints that are not exposed by the current SDK stubs.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * undo sample mypy
  
  * Retry CI after transient external failures
  
  Retrigger PR validation after an unrelated Copilot review workflow SAML failure and a transient external tau2 git fetch failure in the Windows Python test setup.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address review feedback on model option merging
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address Anthropic compatibility review feedback
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * moved all to `model`
  
  * fixes for azure ai search
  
  * Python: standardize remaining sample env var names
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: fix foundry-local pyright compatibility
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * updated env vars in cicd
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-04-01 19:00:18 +00:00
  6acab3d1d6
• fix and unify devui samples (#5025)
  Eduard van Valkenburg · 2026-04-01 13:47:20 +00:00
  2cb78ea12e
• Python: [BREAKING] Remove deprecated Python OpenAI/Azure AI surfaces (#4990)

  * [BREAKING] Remove deprecated Python OpenAI/Azure AI surfaces
  
  Also clean up follow-on docs, environment guidance, package metadata, and lab test stability.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix deleted semantic-kernel sample links
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review feedback
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * improve foundry language
  
  * Fix A2A Foundry sample regression
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-03-31 20:36:21 +00:00
  3a49b1d6dd
• Python: Add Python A2A agent-as-function-tools sample (#4889)

  * Add Python A2A agent-as-function-tools sample
  
  Port of the .NET A2AAgent_AsFunctionTools sample to Python.
  Resolves a remote A2A agent card, converts each skill to a
  FunctionTool via as_tool(), and registers them with a host agent
  using AzureOpenAIResponsesClient.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Sanitize A2A skill names before passing to as_tool()
  
  as_tool() only auto-sanitizes when name is omitted. Since we pass
  skill.name explicitly, we need to strip special characters ourselves.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-03-31 20:00:40 +00:00
  a5eacbbe65
• Python: [BREAKING] Remove deprecated kwargs compatibility paths (#4858)

  * [BREAKING] Remove deprecated kwargs compatibility paths
  
  Remove the deprecated kwargs compatibility shims across core agents, clients, tools, middleware, and telemetry.
  
  Keep workflow kwargs behavior intact in this branch and follow up separately in #4850.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix PR CI fallout for kwargs removal
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review feedback
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * updates
  
  * Fix Azure AI CI fallout
  
  Remove the stale _get_current_conversation_id override from the Azure AI client after the OpenAI base helper was deleted.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fixed new classes
  
  * Fix Assistants deprecated import gating
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix integration replay regressions
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Switch multi-agent hosting samples to Azure chat completions
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Simplify Azure multi-agent sample config
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-03-27 21:00:12 +00:00
  b1b528e4a8
• Python: [BREAKING] Python: Provider-leading client design & OpenAI package extraction (#4818)

  * Python: Provider-leading client design & OpenAI package extraction
  
  Major refactoring of the Python Agent Framework client architecture:
  
  - Extract OpenAI clients into new `agent-framework-openai` package
  - Core package no longer depends on openai, azure-identity, azure-ai-projects
  - Rename clients for discoverability: OpenAIResponsesClient → OpenAIChatClient,
    OpenAIChatClient → OpenAIChatCompletionClient
  - Unify `model_id`/`deployment_name`/`model_deployment_name` → `model` param
  - New FoundryChatClient for Azure AI Foundry Responses API
  - New FoundryAgent/FoundryAgentClient for connecting to pre-configured Foundry agents
  - Remove OpenAIBase/OpenAIConfigMixin from non-deprecated client MRO
  - Deprecate AzureOpenAI* clients, AzureAIClient, OpenAIAssistantsClient
  - Reorganize samples: azure_openai+azure_ai+azure_ai_agent → azure/
  - ADR-0020: Provider-Leading Client Design
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix: missing Agent imports in samples, .model_id → .model in foundry_local sample
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix: CI failures — mypy errors, coverage targets, sample imports
  
  - azure-ai mypy: add type ignores for TypedDict total=, model arg, forward ref
  - Coverage: replace core.azure/openai targets with openai package target
  - project_provider: add type annotation for opts dict
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix: populate openai .pyi stub, fix broken README links, coverage targets
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fixes
  
  * updated observabilitty
  
  * reset azure init.pyi
  
  * fix errors
  
  * updated adr number
  
  * fix foundry local
  
  * fixed not renamed docstrings and comments, and added deprecated markers to old classes
  
  * fix tests and pyprojects
  
  * fix test vars
  
  * updated function tests
  
  * update durable
  
  * updated test setup for functions
  
  * Fix Foundry auth in workflow samples
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Stabilize Python integration workflows
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Update hosting samples for Foundry
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Trigger full CI rerun
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Trigger CI rerun again
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * trigger rerun
  
  * trigger rerun
  
  * fix for litellm
  
  * undo durabletask changes
  
  * Move Foundry APIs into foundry namespace
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix Foundry pyproject formatting
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Split provider samples by Foundry surface
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Restore hosting sample requirements
  
  Also fix the Foundry Local sample link after the provider sample move.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * updated tests
  
  * udpated foundry integration tests
  
  * removed dist from azurefunctions tests
  
  * Use separate Foundry clients for concurrent agents
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * fix client setup in azfunc and durable
  
  * disabled two tests
  
  * updated setup for some function and durable tests
  
  * improved azure openai setup with new clients
  
  * ignore deprecated
  
  * fixes
  
  * skip 11
  
  * remove openai assistants int tests
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-03-25 09:56:29 +00:00
  5e056b672e
• Python: Simplify Python Poe tasks and unify package selectors (#4722)

  * updated automation tasks and commands, with alias for the time being
  
  * Restore aggregate test exclusions
  
  Preserve the legacy all-tests scope for test --all by excluding lab and devui from the default aggregate sweep, while still allowing explicit package selection. Also ignore hidden/generated test directories such as .mypy_cache during aggregate discovery.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * updated versions in pre-commit
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-03-18 18:39:11 +00:00
  f48c4512d3
• Python: Remove bad dependency (#4696)

  * Remove bad dependency in requirements
  
  * Remove bad dependency in requirements.txt

  Laveesh Rohra · 2026-03-13 23:15:56 +00:00
  2f4c4aa614
• Python: Add A2A server sample (#4528)

  * Python: Add A2A server sample and fix client streaming bug
  
  Add a pure Python A2A server sample so testing the A2A client no longer
  requires running the .NET server. The server uses the a2a-sdk's
  A2AStarletteApplication with uvicorn and supports three agent types
  (invoice, policy, logistics) backed by AzureOpenAIResponsesClient.
  
  New files:
  - a2a_server.py: Main server entry point with CLI args
  - agent_executor.py: Bridges a2a-sdk AgentExecutor to Agent Framework
  - agent_definitions.py: Agent and AgentCard factory definitions
  - invoice_data.py: Mock invoice data and query tool functions
  - a2a_server.http: REST Client requests for testing
  
  Also fixes a streaming bug in agent_with_a2a.py where async with was
  used on ResponseStream which does not support the async context manager
  protocol. Changed to async for to match all other samples.
  
  Closes #4045
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review: handle CancelledError and fix end_date filtering
  
  - Re-raise asyncio.CancelledError before the broad exception handler
    so cooperative cancellation is not swallowed.
  - Make end_date filter inclusive of the full day by comparing with
    < end + timedelta(days=1) instead of <= midnight.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Giles Odigwe · 2026-03-10 00:00:49 +00:00
  ded32f3ff8
• Python / .NET Samples - Restructure and Improve Samples (Feature Branc… (#4092)

  * Python: .NET Samples - Restructure and Improve Samples (Feature Branch) (#4091)
  
  * Moved by agent (#4094)
  
  * Fix readme links
  
  * .NET Samples - Create `04-hosting` learning path step (#4098)
  
  * Agent move
  
  * Agent reorderd
  
  * Remove A2A section from README 
  
  Removed A2A section from the Getting Started README.
  
  * Agent fixed links
  
  * Fix broken sample links in durable-agents README (#4101)
  
  * Initial plan
  
  * Fix broken internal links in documentation
  
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * Revert template link changes; keep only durable-agents README fix
  
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * .NET Samples - Create `03-workflows` learning path step (#4102)
  
  * Fix solution project path
  
  * Python: Fix broken markdown links to repo resources (outside /docs) (#4105)
  
  * Initial plan
  
  * Fix broken markdown links to repo resources
  
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * Update README to rename .NET Workflows Samples section
  
  ---------
  
  Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * .NET Samples - Create `02-agents` learning path step (#4107)
  
  * .NET: Fix broken relative link in GroupChatToolApproval README (#4108)
  
  * Initial plan
  
  * Fix broken link in GroupChatToolApproval README
  
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * Update labeler configuration for workflow samples
  
  * .NET - Reorder Agents samples to start from Step01 instead of Step04 (#4110)
  
  * Fix solution
  
  * Resolve new sample paths
  
  * Move new AgentSkills and AgentWithMemory_Step04 samples
  
  * Fix link
  
  * Fix readme path
  
  * fix: update stale dotnet/samples/Durable path reference in AGENTS.md
  
  Co-authored-by: crickman <66376200+crickman@users.noreply.github.com>
  
  * Moved new sample
  
  * Update solution
  
  * Resolve merge (new sample)
  
  * Sync to new sample - FoundryAgents_Step21_BingCustomSearch
  
  * Updated README
  
  * .NET Samples - Configuration Naming Update (#4149)
  
  * .NET: Restore AzureFunctions index parity with ConsoleApps under DurableAgents samples (#4221)
  
  * Clean-up `05_host_your_agent`
  
  * Config setting consistency
  
  * Refine samples
  
  * AGENTS.md
  
  * Move new samples
  
  * Re-order samples
  
  * Move new project and fixup solution
  
  * Fixup model config
  
  * Fix up new UT project
  
  ---------
  
  Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>

  Chris · 2026-02-26 00:56:10 +00:00
  904a5b843e
• Python: Add load_dotenv() to samples for .env file support (#4043)

  * Initial plan
  
  * Add load_dotenv() to 303 Python samples for environment variable loading
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Update SAMPLE_GUIDELINES.md to document load_dotenv() requirement
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Update samples README.md to document .env file usage
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Run ruff format on all changed sample files
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Clarify load_dotenv() usage in README - local dev vs production
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Remove deprecated getting_started folder as requested
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Document env_file_path parameter for per-client configuration
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Merge main branch to resolve conflicts
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Fix run_evaluation.py file that was empty in merge commit
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Remove dotnet changes from merge - out of scope for this PR
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Remove package and test changes from merge - only sample changes needed
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Remove test_func_utils.py - only sample changes needed
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Revert sample files not in original changeset - keep only load_dotenv additions
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Move load_dotenv() outside snippet tag in 06_host_your_agent.py
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Fix comment placement - move load_dotenv before code comments
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Fix load_dotenv() placement across all samples - after docstring, before code comments
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Merge latest main branch with load_dotenv changes
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Remove non-sample changes from merge - keep only load_dotenv additions
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Revert non-load_dotenv sample changes from merge
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Fix run_evaluation.py - use main's improved version (file already had load_dotenv)
  
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  
  * Manual update
  
  * Manual update 2
  
  * Fix Role usage and load_dotenv placement per PR review feedback
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  * Fix Role usage - use string literals not enum attributes
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  * Fix SAMPLE_GUIDELINES.md example - load_dotenv before docstring per guidance
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  * Move load_dotenv() before docstrings in all samples per SAMPLE_GUIDELINES ordering
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  * Address PR review: rename files, fix placement, add session usage, remove note
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  * Update Redis README to reference renamed file redis_history_provider.py
  
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
  Co-authored-by: TaoChenOSU <12570346+TaoChenOSU@users.noreply.github.com>
  Co-authored-by: Tao Chen <taochen@microsoft.com>
  Co-authored-by: eavanvalkenburg <13749212+eavanvalkenburg@users.noreply.github.com>
  Co-authored-by: Eduard van Valkenburg <eavanvalkenburg@users.noreply.github.com>

  Copilot · 2026-02-19 10:55:13 +00:00
  b05fc9e849
• Python: Fixed Anthropic and GitHub Copilot samples (#4025)

  * Fixed Anthropic advanced example
  
  * Small improvement
  
  * Simplified skills sample
  
  * Fixed custom agent sample
  
  * Added service_session_id parameter
  
  * Added tests
  
  * Resolved comments

  Dmytro Struk · 2026-02-18 06:23:35 +00:00
  f900febb6f
• Python: Durable Support for Workflows (#3630)

  * Add workflow support for Azure Functions
  
  * fix compatability with latest framework changes and add integration tests
  
  * refactor code
  
  * remove white space
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * align help text with actual port used
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * replace instance id with a place holder
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * remove unused import
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * remove redundant typing import and fix SIM115
  
  * fix latest breaking changes
  
  * fix mypy issues
  
  * clean up imports
  
  * define source marker strings as constants
  
  * fix json module name
  
  * refactor _extract_message_content_from_dict
  
  * refactor serialization
  
  * add helper method for error response construction and remove _extract_message_content_from_dict since it is not needed
  
  * use strict tpe checking for edges
  
  * change how duplicate agent registrations are handled
  
  * cancel approval_task on HITL timeout
  
  * update docstring
  
  * fix: align azurefunctions package with core API changes after rebase
  
  - State.import_state/export_state are now sync (removed await)
  - Add State.commit() before export_state() in activity execution
  - Rename executor parameter shared_state -> state
  - Rename ctx.set_shared_state/get_shared_state -> set_state/get_state (sync)
  - WorkflowBuilder now takes start_executor as constructor kwarg
  - Update WorkflowOutputEvent -> WorkflowEvent with type='output'
  - Update RequestInfoEvent -> WorkflowEvent[Any]
  - Update SharedState -> State in test imports
  - Update duplicate agent name tests to match new warning behavior
  - Update sample README API references
  
  * fix sample check errors
  
  * fix mypy issues
  
  * fix trailing white spaces
  
  * fix test imports
  
  * feat: add durable workflow samples and adapt to main branch changes
  
  - Add workflow samples 09-12 to 04-hosting/azure_functions/
  - Adapt to ChatMessage -> Message rename from main
  - Adapt to pickle-based checkpoint encoding from main
  - Simplify _serialization.py to delegate to core encode/decode
  - Fix Message -> WorkflowMessage disambiguation in _context.py
  - Remove non-existent _checkpoint_summary import
  
  * fix: update create_checkpoint signature to match superclass
  
  * fix: correct relative link in HITL sample README
  
  * fix: resolve import breakage after rebase (State, DurableAgentThread, get_logger)
  
  ---------
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  Co-authored-by: Dmytro Struk <13853051+dmytrostruk@users.noreply.github.com>

  Ahmed Muhsin · 2026-02-17 22:11:33 +00:00
  bb3d3c2efc
• Python: [BREAKING] PR2 — Wire context provider pipeline, remove old types, update all consumers (#3850)

  * PR2: Wire context provider pipeline and update all internal consumers
  
  - Replace AgentThread with AgentSession across all packages
  - Replace ContextProvider with BaseContextProvider across all packages
  - Replace context_provider param with context_providers (Sequence)
  - Replace thread= with session= in run() signatures
  - Replace get_new_thread() with create_session()
  - Add get_session(service_session_id) to agent interface
  - DurableAgentThread -> DurableAgentSession
  - Remove _notify_thread_of_new_messages from WorkflowAgent
  - Wire before_run/after_run context provider pipeline in RawAgent
  - Auto-inject InMemoryHistoryProvider when no providers configured
  
  * fix: update all tests for context provider pipeline, fix lazy-loaders, remove old test files
  
  * refactor: update all sample files for context provider pipeline (AgentThread→AgentSession, ContextProvider→BaseContextProvider)
  
  * fix: update remaining ag-ui references (client docstring, getting_started sample)
  
  * fix: make get_session service_session_id keyword-only to avoid confusion with session_id
  
  * refactor: rename _RunContext.thread_messages to session_messages
  
  * refactor: remove _threads.py, _memory.py, and old provider files; migrate devui to use plain message lists
  
  * rename: remove _new_ prefix from test files
  
  * refactor: rewrite SlidingWindowChatMessageStore as SlidingWindowHistoryProvider(InMemoryHistoryProvider)
  
  * fix: read full history from session state directly instead of reaching into provider internals
  
  * fix: update stale .pyi stubs, sample imports, and README references for new provider types
  
  * fix: remove stale message_store, _notify_thread_of_new_messages, and session_id.key references in samples
  
  * refactor: merge context_providers and sessions sample folders into sessions, remove aggregate_context_provider
  
  * refactor: UserInfoMemory stores state in session.state instead of instance attributes
  
  * feat: add Pydantic BaseModel support to session state serialization
  
  Pydantic models stored in session.state are now automatically serialized
  via model_dump() and restored via model_validate() during to_dict()/from_dict()
  round-trips. Models are auto-registered on first serialization; use
  register_state_type() for cold-start deserialization.
  
  Also export register_state_type as a public API.
  
  * fix mem0
  
  * Update sample README links and descriptions for session terminology
  
  - Replace 'thread' with 'session' in sample descriptions across all READMEs
  - Update file links for renamed samples (mem0_sessions, redis_sessions, etc.)
  - Fix Threads section → Sessions section in main samples/README.md
  - Update tools, middleware, workflows, durabletask, azure_functions READMEs
  - Update architecture diagrams in concepts/tools/README.md
  - Update migration guides (autogen, semantic-kernel)
  
  * Fix broken Redis README link to renamed sample
  
  * Fix Mem0 OSS client search: pass scoping params as direct kwargs
  
  AsyncMemory (OSS) expects user_id/agent_id/run_id as direct kwargs,
  while AsyncMemoryClient (Platform) expects them in a filters dict.
  Adds tests for both client types.
  
  Port of fix from #3844 to new Mem0ContextProvider.
  
  * Fix rebase issues: restore missing _conversation_state.py and checkpoint decode logic
  
  - Add back _conversation_state.py (encode/decode_chat_messages) lost in rebase
  - Fix on_checkpoint_restore to decode cache/conversation with decode_chat_messages
  - Fix on_checkpoint_restore to use decode_checkpoint_value for pending requests
  - Add tests/workflow/__init__.py for relative import support
  - Fix test_agent_executor checkpoint selection (checkpoints[1] not superstep)
  
  * Add STORES_BY_DEFAULT ClassVar to skip redundant InMemoryHistoryProvider injection
  
  Chat clients that store history server-side by default (OpenAI Responses API,
  Azure AI Agent) now declare STORES_BY_DEFAULT = True. The agent checks this
  during auto-injection and skips InMemoryHistoryProvider unless the user
  explicitly sets store=False.
  
  * Fix broken markdown links in azure_ai and redis READMEs
  
  * Fix getting-started samples to use session API instead of removed thread/ContextProvider API
  
  * updates to workflow as agent
  
  * fix group chat import
  
  * Rename Thread→Session throughout, fix service_session_id propagation, remove stale AGUIThread
  
  - Fix: Propagate conversation_id from ChatResponse back to session.service_session_id
    in both streaming and non-streaming paths in _agents.py
  - Rename AgentThreadException → AgentSessionException
  - Remove stale AGUIThread from ag_ui lazy-loader
  - Rename use_service_thread → use_service_session in ag-ui package
  - Rename test functions from *_thread_* to *_session_*
  - Rename sample files from *_thread* to *_session*
  - Update docstrings and comments: thread → session
  - Update _mcp.py kwargs filter: add 'session' alongside 'thread'
  - Fix ContinuationToken docstring example: thread=thread → session=session
  - Fix _clients.py docstring: 'Agent threads' → 'Agent sessions'
  
  * Fix broken markdown links after thread→session file renames
  
  * fix azure ai test

  Eduard van Valkenburg · 2026-02-12 21:00:32 +00:00
  1e350ea22f
• Python: restructure: Python samples into progressive 01-05 layout (#3862)

  * restructure: Python samples into progressive 01-05 layout
  
  - 01-get-started/: 6 numbered steps (hello agent → hosting)
  - 02-agents/: all agent concept samples (tools, middleware, providers, etc.)
  - 03-workflows/: ALL existing workflow samples preserved as-is
  - 04-hosting/: azure-functions, durabletask, a2a
  - 05-end-to-end/: demos, evaluation, hosted agents
  - Old files moved to _to_delete/ for review
  - Added AGENTS.md with structure documentation
  - autogen-migration/ and semantic-kernel-migration/ preserved at root
  
  * fix: switch to AzureOpenAI Foundry, fix CI failures
  
  - Switch all 01-get-started samples to AzureOpenAIResponsesClient with
    Azure AI Foundry project endpoint (AZURE_AI_PROJECT_ENDPOINT +
    AZURE_OPENAI_RESPONSES_DEPLOYMENT_NAME + AzureCliCredential)
  - Add _to_delete/ and 05-end-to-end/ to pyrightconfig.samples.json excludes
  - Fix test paths in packages/ that referenced old getting_started/ dirs:
    durabletask conftest + streaming test, azurefunctions conftest,
    devui conftest + capture_messages + openai_sdk_integration
  - Fix workflow_as_agent_human_in_the_loop.py import (sibling import)
  - Update hosting READMEs and tool comment paths
  - Replace root README.md with new structure overview
  - Update AGENTS.md to document Azure OpenAI Foundry as default provider
  
  * cleanup: remove _to_delete folder, copy resource files to active dirs
  
  All files in _to_delete/ were either:
  - Exact duplicates of files in the new structure (240 files)
  - Same file with only comment path updates (100 files)
  - One import-fix diff (workflow_as_agent_human_in_the_loop.py)
  - One superseded minimal_sample.py
  
  Resource files (sample.pdf, countries.json, employees.pdf, weather.json)
  copied to 02-agents/sample_assets/ and 02-agents/resources/ since active
  samples reference them.
  
  * fix: address PR review comments, centralize resources, remove root duplicates
  
  - Fix type annotation in 04_memory.py (string union -> proper types)
  - Fix old sample paths in observability files
  - Fix grammar/spelling in observability samples
  - Move sample_assets/ and resources/ to shared/ folder
  - Remove 8 duplicate observability files from 02-agents root
  - Update resource path references in multimodal_input and provider samples
  
  * fix: update broken links from old getting_started paths to new structure
  
  - Update relative paths in READMEs: getting_started/ → 01-get-started/,
    02-agents/, 03-workflows/, 04-hosting/, 05-end-to-end/
  - Fix absolute GitHub URLs in package READMEs
  - Fix broken link in ollama package README
  
  * fix: convert absolute GitHub URLs to relative paths for link checker
  
  Absolute URLs to python/samples/ on main branch 404 until PR merges.
  Converted to relative paths that linkspector can verify locally.
  
  * fix: update link for handoff sample moved to orchestrations/
  
  * fix: update chatkit-integration README path from demos/ to 05-end-to-end/
  
  * fix: update broken links in orchestrations README to match flat directory structure

  Eduard van Valkenburg · 2026-02-12 17:36:36 +00:00
  a2856d3b92