20 Commits

• Python: [BREAKING] Add sampling guardrails to MCP tools (#6413)

  * Add sampling guardrails to MCP tools
  
  Add approval, token, and request-count controls to the MCP sampling
  callback used when an MCPTool is configured with a chat client.
  
  - Add `sampling_approval_callback`, `sampling_max_tokens`, and
    `sampling_max_requests` parameters to `MCPTool` and its
    `MCPStdioTool`, `MCPStreamableHTTPTool`, and `MCPWebsocketTool`
    subclasses, positioned directly after `client`.
  - Gate each server-initiated `sampling/createMessage` request behind the
    approval callback, which denies by default when no callback is provided.
  - Clamp the requested `maxTokens` to `sampling_max_tokens` and enforce a
    per-session request count via `sampling_max_requests`.
  - Log incoming sampling requests at WARNING level (counts only).
  - Export `SamplingApprovalCallback` from the public API.
  - Add tests, a sample, and documentation updates.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Make sampling denial message context-aware
  
  Distinguish the deny-by-default case (no approval callback configured)
  from an explicit denial by a configured `sampling_approval_callback`, so
  the returned ErrorData message is accurate for callback-driven denials
  and exceptions.
  
  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-10 10:17:36 +00:00
  9a56bc9f16
• Python: Filter MCP tool kwargs to declared params via allowlist (#6399)

  * Filter MCP tool kwargs to declared params via allowlist
  
  Previously MCPTool combined framework runtime kwargs (from
  FunctionInvocationContext.kwargs) with the LLM-supplied arguments and
  stripped only a hardcoded denylist of known framework keys before
  forwarding to the MCP server. Any new framework-injected kwarg leaked to
  the server unless the denylist was updated.
  
  Switch to an allowlist built from each tool's declared parameters
  (inputSchema.properties). Only declared params are forwarded; everything
  else is stripped. Add an `additional_tool_argument_names` constructor
  argument so users can opt extra names back in, globally (Sequence[str])
  and/or per remote tool name (Mapping with reserved "*" global key). The
  existing denylist is kept as a safety net for framework-named params a
  server declares in its schema; explicitly opted-in extras always win. The
  reserved _meta handling is unchanged.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address MCP allowlist review comments and fix reload arg loss
  
  - Fix pyright reportUnknownArgumentType in _load_tools (cast schema properties).
  - Register declared param names before the existing-tool skip guard so that
    tool-list reloads preserve the allowlist for already-loaded tools (previously
    unchanged tools silently dropped all declared args after a background reload).
  - Handle bare-string values in an additional_tool_argument_names mapping instead
    of iterating their characters.
  - Clarify the framework denylist comment: explicit extras override the denylist.
  - Make the extras-override-denylist test unambiguous (opt in a denylisted name).
  
  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-09 07:37:11 +00:00
  cfb033e5d4
• Python: MCP long-running task support in Python (#6319)

  * MCP long-running task support in Python
  
  * Fix pyupgrade and AGENTS.md reconnect description
  
  - pyupgrade: drop forward-reference string annotations in _mcp.py (Python 3.10+ resolves them natively now that MCPTaskOptions is defined before use).
  
  - AGENTS.md: align reconnect description with current behavior. Phase 1 (initial tools/call) does NOT retry on connection loss; raises 'connection lost; task state unknown' instead, so a server that accepted the request but lost the response cannot start the operation twice. Phase 2 (tasks/get / tasks/result) still reconnects once against the same task_id.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix bandit nosec marker for CI pipeline
  
  * Address PR feedbacks
  
  * Clarifiied comments and addressed more PR feedbacks.
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Peter Ibekwe · 2026-06-05 00:04:55 +00:00
  bf4ad48cf2
• Python: progressive tool exposure via FunctionInvocationContext (#6233)

  * Python: progressive tool exposure via FunctionInvocationContext
  
  Add first-class progressive tool exposure to the Python core function-calling
  loop. Tools can now add or remove real FunctionTool schemas at runtime via the
  injected FunctionInvocationContext, taking effect on the next iteration of the
  loop.
  
  - FunctionInvocationContext gains a live `tools` list plus experimental
    `add_tools()` / `remove_tools()` helpers (feature: PROGRESSIVE_TOOLS).
  - The function-calling loop establishes a run-local, normalized tools list and
    threads it into the context at both invocation paths so mutations propagate.
  - Add a sample (dynamic_tool_exposure.py) and a tools samples README, including
    a note that CodeAct providers (Monty/Hyperlight) use their own provider-level
    tool management instead.
  
  Supersedes #3877.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Validate non-negative input in dynamic_tool_exposure sample tools
  
  Address review feedback: factorial and fibonacci now return an error
  message for negative n instead of producing incorrect results.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Make add_tools atomic and surface swallowed function errors
  
  Address review feedback on progressive tool exposure:
  
  - add_tools now validates the full batch against a throwaway copy before
    committing, so a duplicate-name clash partway through a sequence leaves
    the live tool list unchanged (all-or-nothing).
  - _auto_invoke_function now logs a warning (with traceback) when a tool
    raises, so contract errors such as a duplicate-name ValueError from
    add_tools are debuggable without enabling include_detailed_errors.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Avoid retaining tracebacks when logging swallowed function errors
  
  Logging with exc_info=exc fed the exception traceback to the logging
  machinery, whose frame references created reference cycles collected
  lazily by the cyclic GC. On Windows that could drop a hyperlight
  WasmSandbox on a non-owning thread ("unsendable, dropped on another
  thread"), crashing the xdist worker. Log a pre-formatted message with
  the exception repr instead, so no traceback object is retained.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * added missing decorator
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-06-03 09:01:07 +00:00
  49a6e433a3
• Python: Adding AgentFileStore and FileAccessProvider to support file access operations. (#6099)

  * Adding AgentFileStore and FileAccessProvider to support file ased operations for agents.
  
  * Address PR review feedback on FileAccessProvider
  
  - Probe symlinks on the unresolved candidate path so in-root symlinks
    cannot silently pass and out-of-root symlinks surface the correct
    error message.
  - Validate matching_lines elements in FileSearchResult.from_dict and
    raise a clean ValueError for non-mapping entries.
  - Cap search regex pattern length (256 chars) via a new
    _compile_search_regex helper to mitigate ReDoS, and surface the cap
    in the file_access_search_files tool description.
  - Skip non-UTF-8 files during filesystem search instead of aborting
    the entire directory walk.
  - Replace the module-scope trailing string in the data-processing
    sample with comments to avoid Ruff B018.
  - Remove the checked-in working/region_totals.md sample artifact so
    the save flow works from a clean checkout.
  - Expand the Windows stdout reconfiguration comment in task_runner.py
    for clarity.
  - Add tests for invalid/oversize regex, non-UTF-8 file search, and
    in-root symlink rejection.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix mypy redundant-cast in FileSearchResult.from_dict
  
  Use cast(list[object], ...) instead of cast(list[Any], ...) so the
  cast represents a real type change (lists are invariant) and is no
  longer flagged by mypy as redundant, while still satisfying pyright's
  reportUnknownVariableType. Matches the existing pattern in _memory.py.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Tighten path normalization and directory resolution in FileAccess
  
  - _normalize_relative_path now strips surrounding whitespace up front
    so leading/trailing spaces never leak into file segments, and
    rejects trailing path separators for file paths so 'foo/' is no
    longer silently coerced to 'foo'.
  - FileSystemAgentFileStore._resolve_safe_directory_path normalizes
    with is_directory=True and maps an empty normalized result to the
    root. This matches InMemoryAgentFileStore so whitespace-only
    directory inputs resolve to the root instead of raising.
  - Added tests for whitespace stripping, trailing-separator rejection,
    and whitespace-only directory listing on the filesystem store.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Harden FileAccess search and atomic save in store API
  
  - Add wall-clock timeout (10s) around regex scans so a pathological pattern (e.g. `(a+)+`) below the length cap cannot stall the event loop.
  - Offload the InMemoryAgentFileStore regex scan to a worker thread, matching the filesystem store.
  - Fail closed when `Path.is_symlink` raises during the safe-path probe so a permission error cannot silently bypass the symlink/reparse-point rejection.
  - Add `overwrite: bool = True` to `AgentFileStore.write_file`; the in-memory store performs the check under the existing lock and the filesystem store uses `open(mode='x')` so concurrent callers cannot race past `overwrite=False`.
  - `file_access_save_file` now relies on the atomic store call instead of a separate `file_exists` round-trip.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix Python 3.10 timeout handling and add directory arg to list/search tools
  
  - Catch asyncio.TimeoutError in _run_search_with_timeout. In Python 3.10
    asyncio.wait_for raises asyncio.exceptions.TimeoutError, which is
    distinct from the builtin TimeoutError (the two were unified in 3.11).
    Catching the asyncio alias works on every supported version.
  - Add an optional directory parameter to file_access_list_files and
    file_access_search_files so agents can enumerate / scope searches to
    nested folders, not just the store root.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address FileAccess review feedback: case, errors, signal, TOCTOU
  
  - InMemoryAgentFileStore now stores (display_name, content) so list_files
    and search_files return the original-case names callers wrote, matching
    the behaviour of FileSystemAgentFileStore on case-preserving filesystems
    and removing the silent in-memory vs. on-disk contract divergence.
  - FileSystemAgentFileStore.read_file raises ValueError instead of letting
    UnicodeDecodeError bubble for binary / non-UTF-8 input, restoring
    symmetry with search_files (which still skips) and giving the tool
    layer a recoverable type to translate.
  - Tool wrappers now catch ValueError and OSError around every operation
    and surface them as readable strings, so 'you used ..' and 'the file
    already exists' are both reported to the model the same way instead of
    the former crashing out as an unhandled exception.
  - _search_files_sync logs per skipped non-UTF-8 file at WARNING and an
    aggregate INFO summary so operators can distinguish 'no matches' from
    'half the corpus was unreadable'.
  - FileSystemAgentFileStore softens its docstrings to acknowledge the
    inherent probe-then-open TOCTOU window. On POSIX both read and write
    now pass O_NOFOLLOW so the kernel refuses if the leaf segment becomes
    a symlink between the probe and the open. Windows has no equivalent
    flag; the limitation is documented.
  - Tests cover: case preservation on list/search, ValueError on non-UTF-8
    read at the store and tool layer, tool-layer string responses for
    path-traversal and oversized-regex inputs, search-skip log output,
    symlink rejection on delete/search/list, and symlinked intermediate
    directory rejection.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address FileAccess nit comments: docstrings, enumerate, opt-in delete approval
  
  - Expand FileSearchMatch/FileSearchResult.to_dict docstrings to explain why
    the override is needed (__slots__ defeats the mixin's __dict__ iteration)
    and why exclude/exclude_none are accepted-but-ignored (mixin signature
    compatibility for callers like to_json).
  - Use enumerate(lines, start=1) in _search_file_content so the +1 below is
    no longer needed; rename loop variable to line_number for clarity.
  - Add opt-in require_delete_approval: bool = False on FileAccessProvider.
    When True, file_access_delete_file is registered with approval_mode
    'always_require' so the host must approve every delete. Default False
    preserves current behaviour and matches the .NET reference, but
    deployments that want a safer-by-default posture can enable it.
  - Add tests covering both delete approval modes.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * FileAccess: require delete approval by default
  
  Flip the default for FileAccessProvider(require_delete_approval=...) from
  False to True so destructive deletes are gated by host approval out of the
  box. Callers that want the previous autonomous behaviour (which matches the
  .NET reference) can pass require_delete_approval=False.
  
  Tests updated accordingly.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fixing linkinspector by installing Chrome for puppeteer first.
  
  ---------
  
  Co-authored-by: Ben Thomas <25218250+alliscode@users.noreply.github.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Ben Thomas · 2026-05-28 20:09:50 +00:00
  b000a2cf51
• 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] [Breaking] Extract skill spec metadata into SkillFrontmatter (#5775)

  * Fix Skill docstring consistency and spelling
  
  - Add ClassSkill to Skill class docstring concrete implementations list
  - Normalize 'defence' to 'defense' for American English consistency
  - Remove extra blank line in InlineSkill docstring example
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix E501 line-too-long lint error in test_skills.py
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix stale test section header to reflect SkillFrontmatter API
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix metadata children overriding top-level frontmatter fields
  
  Scope YAML_KV_RE to column-0 keys only so indented children
  under metadata: are not mistakenly parsed as top-level fields.
  Add regression test and spec fields to sample SKILL.md files.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  SergeyMenshykh · 2026-05-13 20:35:52 +00:00
  ab09246dc4
• Python: information-flow control prompt injection defense (#5331)

  * Python: Information-flow control based prompt injection defense (#5024)
  
  * fides integration
  
  * documentation
  
  * documentation
  
  * documentation
  
  * human-approval on policy violation
  
  * numenous hyena 'works'
  
  * IFC based implementation
  
  * minor edits in documentation
  
  * rebasing the branch and running the email example
  
  * Add security tests for IFC middleware
  
  * Fix Role.TOOL NameError in approval handling
  
  * tiered labelling scheme
  
  * 3 tier labelling scheme in middleware
  
  * Adapt security middleware to list[Content] tool results
  
  * Refactor SecureAgentConfig as context provider and address Copilot review comments
  
  * Update FIDES docs to reflect context provider pattern and update code for ContextProvider rename
  
  * Fix security examples: use OpenAIChatClient instead of non-existent AzureOpenAIChatClient
  
  * Address PR review: consolidate security modules, remove ContentLineage, update docs
  
  * remove unrelated files
  
  * remove comment from _tools.py and rename decision file
  
  * Fix CI failures: Bandit B110, broken md links, hosted approval passthrough
  
  * apply template to decision doc 0024
  
  * minor fixes to decision doc 0024
  
  ---------
  
  Co-authored-by: Aashish <t-akolluri@microsoft.com>
  
  * Python: follow up FIDES security flow (#5330)
  
  * Python: follow up FIDES security flow
  
  Refine the secure approval path, mark the security classes with the FIDES experimental feature label, and clean up the related docs/tests. Also fix workspace-level validation regressions uncovered while running the full Python check suite.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: remove FIDES GitHub MCP sample
  
  Drop the GitHub MCP security sample from the FIDES follow-up branch while keeping the remaining security docs and samples intact.
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address PR review: fix paths and update FIDES implementation (#5352)
  
  * Python: updated import naming and comment from review (#5421)
  
  * updated import naming and comment from review
  
  * Add approval replay None call-id test
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Python: Address PR 5331 comments and track sesssion while calling Agent in email_security_example (#5446)
  
  * Address PR review: fix paths and update FIDES implementation
  
  * Address PR comments and add session tracking in email example in samples
  
  * Fix session creation and resolve merge conflict in docstring example
  
  * Resolve merge conflict in docstring example
  
  * Python: add test for empty-message pruning in approval result replacement (#5617)
  
  Adds test coverage for the second-pass logic in
  `_replace_approval_contents_with_results` that removes messages whose
  `contents` list becomes empty after first-pass content removal.
  
  Addresses review comment on PR #5331:
  https://github.com/microsoft/agent-framework/pull/5331#discussion_r3129039445
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: shrutitople <shruti.tople@gmail.com>
  Co-authored-by: Aashish <t-akolluri@microsoft.com>
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-05-05 18:08:08 +00:00
  ddfbdf5c7a
• Python: add experimental file history provider (#5248)

  * add experimental file history provider
  
  * Improve file history provider writes
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * typo
  
  * cleanup
  
  * cleanup
  
  * fix in readme
  
  * added security messages
  
  * Refine file history provider locking
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * added additional sample
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-04-15 22:23:37 +00:00
  ff05c22c58
• 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] update context provider APIs, middleware, and per-service-call history persistence (#4992)

  * Rename provider base APIs
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Allow provider-added chat and function middleware
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Simulate service-stored history per model call
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix typing regressions in CI
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Fix response ID suppression review feedback
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Rename per-service-call history persistence APIs
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Address context persistence review feedback
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Stabilize markdown sample docs
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  * Persist service continuation state per call
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

  Eduard van Valkenburg · 2026-04-01 16:13:11 +00:00
  b065a4ce51
• 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: Support skill scripts execution (#4558)

  * support skill scripts execution
  
  * fix mixed line endings
  
  * address comments and fix syntax issues
  
  * use few try/except instead of one
  
  * change samples
  
  * validate either script path or script resource is set not both
  
  * fix: separate LLM args from runtime kwargs in skill script execution
  
  * address pr review comments
  
  * address PR review comments
  
  * Update python/packages/core/agent_framework/_skills.py
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/packages/core/agent_framework/_skills.py
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * Update python/packages/core/agent_framework/_skills.py
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  * 1. Fixing the caching bug where parameters_schema would re-inspect on every call when the result was None
     2. Updating the arguments tool description to be more generic (not CLI-specific)
  
  * fix failing tests
  
  * address pr review comments
  
  * address pr review comments
  
  * allow resource function returning any instead of sting
  
  * address PR review comments
  
  ---------
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

  SergeyMenshykh · 2026-03-11 18:28:30 +00:00
  23ebfbc937
• 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
• Removed context parameter from call_next (#3829)
  Dmytro Struk · 2026-02-11 10:47:41 +00:00
  1fdc4be88d
• Python: [BREAKING] Simplify API: ChatAgent -> Agent, ChatMessage -> Message (#3747)

  * [BREAKING] Rename ChatAgent -> Agent, ChatMessage -> Message, ChatClientProtocol -> SupportsChatGetResponse
  
  Simplify the public API by removing redundant 'Chat' prefix from core types:
  - ChatAgent -> Agent
  - RawChatAgent -> RawAgent
  - ChatMessage -> Message
  - ChatClientProtocol -> SupportsChatGetResponse
  
  Also renamed internal WorkflowMessage (was Message in _runner_context) to avoid collision.
  
  No backward compatibility aliases - this is a clean breaking change.
  
  * [BREAKING] Rename Agent chat_client parameter to client
  
  * Fix rebase issues: WorkflowMessage references and broken markdown links
  
  * Fix formatting and lint issues from code quality checks
  
  * Fix import ordering in workflow sample files
  
  * fixed rebase
  
  * Fix test failures: use WorkflowMessage and A2AMessage after ChatMessage→Message rename
  
  - Replace Message(data=..., source_id=...) with WorkflowMessage(...) in workflow tests
  - Fix isinstance check in A2A agent to use A2AMessage instead of Message
  - Fix import in test_workflow_observability.py (Message→WorkflowMessage)
  
  * Fix lint, fmt, and sample errors after ChatMessage→Message rename
  
  - Auto-fix 70+ ruff lint issues across samples (ChatMessage→Message refs)
  - Fix HostedVectorStoreContent→Content.from_hosted_vector_store in file search sample
  - Fix _normalize_messages→normalize_messages in custom agent sample
  - Fix context.terminate→raise MiddlewareTermination in middleware samples
  - Fix with_update_hook→with_transform_hook in override middleware sample
  - Add TOptions_co import back to custom_chat_client sample
  - Add noqa for FastAPI File() default in chatkit sample
  - Fix B023 loop variable capture in weather agent sample
  
  * fix: update Agent constructor calls from chat_client to client in declaration-only tool tests
  
  * fix: add register_cleanup to devui lazy-loading proxy and type stub
  
  * fixed tests and updated new pieces
  
  * fix agui typevar
  
  * fix merge errors
  
  * fix merge conflicts
  
  * fiux merge
  
  * Remove unused links
  
  ---------
  
  Co-authored-by: Evan Mattson <evan.mattson@microsoft.com>

  Eduard van Valkenburg · 2026-02-10 23:04:32 +00:00
  0521f5bed8
• Python: [BREAKING] Renamed next middleware parameter to call_next (#3735)

  * Renamed next middleware parameter to call_next
  
  * Resolved comments

  Dmytro Struk · 2026-02-09 21:21:27 +00:00
  e4ca3e60f8
• Python: [BREAKING] Renamed AgentProtocol to SupportsAgentRun (#3717)

  * Renamed AgentProtocol to AgentLike
  
  * Resolved comments
  
  * Renamed AgentLike to SupportsAgentRun
  
  * Resolved comments

  Dmytro Struk · 2026-02-06 17:53:21 +00:00
  15256bb616
• Python: [BREAKING] Renamed AgentRunContext to AgentContext (#3714)

  * Renamed AgentRunContext to AgentContext
  
  * Update python/packages/core/AGENTS.md
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
  
  ---------
  
  Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

  Dmytro Struk · 2026-02-06 06:47:51 +00:00
  09f59b21ad
• .NET: Python: Add AGENTS.md files and update coding standards (#3644)

  * Add AGENTS.md files and update coding standards for Python
  
  - Add root python/AGENTS.md with project structure and package links
  - Add AGENTS.md for each package describing purpose and main classes
  - Update .github/copilot-instructions.md with improved structure
  - Update python/CODING_STANDARD.md with API review guidance:
    - Future annotations convention (#3578)
    - TypeVar naming convention (#3594)
    - Mapping vs MutableMapping (#3577)
    - Avoid shadowing built-ins (#3583)
    - Explicit exports (#3605)
    - Exception documentation guidelines (#3410)
  - Simplify python/.github/instructions/python.instructions.md to reference AGENTS.md
  - Remove AGENTS.md from .gitignore
  
  * Fix purview import path in AGENTS.md
  
  * Address PR review comments and restructure instructions
  
  - Slim down .github/copilot-instructions.md to reference language-specific docs
  - Add ADR section explaining templates and purpose
  - Create dotnet/AGENTS.md with .NET-specific build commands, conventions, and sample guidance
  - Update Python build/test instructions for core vs isolated changes
  - Fix Microsoft.Extensions.AI package references
  - Update kwargs guidance per issue #3642
  - Fix Python sample helper placement (top, not bottom)
  - Document new 'typing' poe task in DEV_SETUP.md
  
  * Add 'typing' poe task to run both pyright and mypy
  
  * Add kwargs guidelines from issue #3642 to CODING_STANDARD.md
  
  * Clarify that connector packages pull in core as dependency

  Eduard van Valkenburg · 2026-02-05 10:27:46 +00:00
  eaad042241