Python: Feature/hosted dwf by alliscode · Pull Request #5531 · microsoft/agent-framework

alliscode · 2026-04-28T00:28:15Z

This pull request enhances support for passing conversation history into declarative workflow agents, ensuring that workflows receive the full message context (not just the latest user turn) when triggered via agents. It updates the input initialization logic, executor signatures, and hosting integration to handle lists of Message objects, and adds a regression test to guarantee correct population of System.LastMessageText for compatibility with existing YAML workflows.

…rt executor The declarative start executor (JoinExecutor) only advertised dict and str in its input_types, so WorkflowAgent.__init__ rejected it with 'Workflow's start executor cannot handle list[Message]'. Add list[Message] to the JoinExecutor handler annotation and add a matching branch in DeclarativeActionExecutor._ensure_state_initialized that extracts the last user-message text and falls through to the string-input initialization path, so =System.LastMessageText works end-to-end via as_agent(). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

When Workflow.as_agent() is invoked with a list[Message], the start executor now populates Conversation.messages / Conversation.history / System.conversations.{id}.messages with prior turns only (excluding the latest user message), and surfaces the latest user message via Inputs.input and System.LastMessage*. This matches InvokeAzureAgent's contract that the messages binding holds prior turns and the executor itself appends the new user input before invoking, avoiding double-append of the trailing user turn while preserving full history (incl. assistant/system/tool roles and multi-modal content) for downstream actions.

MessageRole and other str-subclass Enums passed isinstance(v, str) and were forwarded to pythonnet unchanged. pythonnet then raised 'MessageRole value cannot be converted to System.String' for every PowerFx primitive when ConditionGroup/Expr eval walked the symbol table containing Conversation.messages. Reduce Enum members to their underlying value before the primitive check so eval sees plain strings/ints.

_handle_inner_workflow only forwarded the latest user turn to WorkflowAgent.run, even though _handle_inner_agent already prepends history fetched from Foundry storage to the messages it sends a regular agent. Declarative workflows reset Conversation.messages on every run (state.initialize), so checkpoint replay alone does not give them prior turns - the host has to pass them in, the same way it does for non-workflow agents. Mirror that contract: fetch context.get_history() and pass [*history, *input_messages] to the workflow agent.

moonbox3 · 2026-04-28T00:30:56Z

Python Test Coverage Report •

File	Stmts	Miss	Cover	Missing
packages/core/agent_framework/_workflows
_agent.py	358	71	80%	66, 74–80, 116–117, 210, 271, 284, 351, 362, 364, 424, 430, 447–448, 455, 457, 463, 525–526, 535, 543, 569, 602–604, 606, 608, 610, 615, 620, 674, 704, 721, 760–763, 769, 775, 779–780, 783–789, 793–794, 802, 863, 870, 876–877, 888, 920, 927, 948, 957, 961, 963–965, 972
_runner.py	174	2	98%	309–310
_workflow.py	278	19	93%	91, 270–272, 274–275, 293, 297, 461, 676, 697, 747, 759, 765, 770, 790–792, 843
packages/declarative/agent_framework_declarative/_workflows
_declarative_base.py	462	58	87%	47, 50, 154, 242, 256, 270, 281, 298, 425–426, 433–434, 449, 479, 562–564, 566–568, 570, 573, 580, 606, 632–638, 640–641, 643–651, 672–673, 675–676, 966–969, 993–994, 1001–1002, 1007, 1016–1017, 1023
_executors_control_flow.py	170	6	96%	82, 90, 153, 343–344, 348
packages/foundry_hosting/agent_framework_foundry_hosting
_responses.py	528	118	77%	151–152, 161–162, 166, 171, 185, 209, 235–237, 256–258, 260–262, 264–266, 270–273, 285–291, 301–302, 320–322, 327, 329, 336, 338–339, 341, 343, 349–352, 354–356, 360, 363, 368–374, 377–378, 380–381, 389–394, 466–467, 1112–1114, 1116, 1163–1164, 1166–1167, 1169–1170, 1172–1173, 1178, 1187, 1190–1192, 1194, 1212, 1215, 1250–1254, 1258–1264, 1271–1275, 1281–1287, 1294, 1300, 1303
TOTAL	30502	3560	88%

Python Unit Test Overview

Tests	Skipped	Failures	Errors	Time
6131	30 💤	0 ❌	0 🔥	1m 36s ⏱️

Copilot

Pull request overview

This PR improves hosted declarative workflow agents so they receive full conversation context (history + current input) when invoked via agent interfaces, aligning behavior with non-workflow agents and maintaining YAML compatibility via System.LastMessageText.

Changes:

Foundry hosting now prepends stored conversation history to workflow-agent inputs before invoking WorkflowAgent.run(...).
Declarative workflow state initialization now accepts list[Message], populating Conversation.* and System.LastMessage* accordingly, and improves PowerFx safety by coercing Enum values.
Adds a regression test ensuring Workflow.as_agent() populates System.LastMessageText correctly.

Show a summary per file

File	Description
python/packages/foundry_hosting/agent_framework_foundry_hosting/_responses.py	Passes Foundry-stored history + current request messages into workflow agent runs.
python/packages/declarative/agent_framework_declarative/_workflows/_declarative_base.py	Adds `list[Message]` trigger initialization and Enum-to-primitive coercion for PowerFx symbol conversion.
python/packages/declarative/agent_framework_declarative/_workflows/_executors_control_flow.py	Updates `JoinExecutor` trigger type to include `list[Message]` so workflows can be exposed as agents.
python/packages/declarative/tests/test_workflow_factory.py	Adds regression coverage for `Workflow.as_agent()` and `System.LastMessageText`.

Copilot's findings

Files reviewed: 4/4 changed files
Comments generated: 2

github-actions

Automated Code Review

Reviewers: 4 | Confidence: 89% | Result: All clear

Reviewed: Correctness, Security Reliability, Test Coverage, Design Approach

Automated review by alliscode's agents

…urn continuation Allow Workflow.run(message=..., checkpoint_id=...) so callers can restore prior workflow state from a checkpoint AND deliver a new message to the start executor in a single call. The existing reset_context logic already preserves shared state when checkpoint_id is set, so this gives us 'fresh start executor invocation with prior state intact' - exactly what hosted multi-turn declarative workflows need. - _workflow.py: drop the message+checkpoint_id mutual exclusion and update _execute_with_message_or_checkpoint to do both (restore then execute) when both are provided. - _agent.py: in _run_core's checkpoint branch, also forward input_messages so WorkflowAgent.run(messages, checkpoint_id=...) works end-to-end. Falls back to the legacy 'restore only' behavior when messages are absent. - _declarative_base.py: detect continuation in _ensure_state_initialized by checking whether DECLARATIVE_STATE_KEY already exists in shared state; if so, refresh inputs/LastMessage* and append non-user trigger messages instead of calling state.initialize() (which would wipe Conversation/Local/System). - foundry_hosting/_responses.py: collapse the host's two-call pattern (restore-only, then fresh run) into a single combined call now that the underlying APIs support it. - tests: drop the assertion that combined message+checkpoint_id raises. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Replace the prior 'combined message + checkpoint_id in one run()' approach with a cleaner default: Workflow.run no longer wipes shared state or runner- context messages between calls. Iteration counting and per-run kwargs still reset on a fresh-message run; checkpoint and responses runs are continuations that preserve everything. This lets a WorkflowAgent be invoked repeatedly on the same instance and maintain multi-turn context (e.g. accumulated Conversation.messages) without asking developers to opt in. Hosted-agent multi-turn pattern becomes two explicit calls: restore-from-checkpoint (drive to idle), then run-with-message. Key changes: - _workflow.py: drop _state.clear() and reset_for_new_run() from run(). Reset iteration count and run kwargs on fresh-message runs only. Restore 'Cannot provide both message and checkpoint_id' validation. Add async guard: fresh-message run with un-drained pending executor messages from a prior run is invalid. - _runner.py: clear _state before import_state in restore_from_checkpoint so restore is authoritative (import_state merges, not replaces). - _agent.py: revert checkpoint branch to restore-only (no message forward). - _responses.py (foundry_hosting): two-call host pattern - restore checkpoint silently, then run with new user input. - tests: state-preservation is the new default; rebuild Workflow for clean slate. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- _workflow.py: collapse nested if (SIM102), drop redundant assignment (RET504) - _declarative_base.py: remove unused last_user_msg = tail assignment whose Message | None type clashed with the prior Message-typed branch Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot

Copilot's findings

Files reviewed: 8/8 changed files
Comments generated: 4

- _declarative_base.py: continuation branch was writing 'Inputs.input' via state.set, which routes to the Custom namespace and never updates the PowerFx-visible Workflow.Inputs.input. Update state_data['Inputs'] in place via get_state_data / set_state_data so =Workflow.Inputs.input and =inputs.input see the new turn's user text on continuation. - _declarative_base.py: refresh docstring to clarify that on a list[Message] trigger, Conversation.messages excludes the current user message at the start of the turn (agent executors append it before invoking the inner agent). - _responses.py: when previous_response_id is supplied (no conversation_id), the prior checkpoint lives under <storage>/<previous_response_id> but new checkpoints must land under <storage>/<current_response_id> for the next turn to find them. Hold onto restore_storage from the get_latest lookup and pass it to the restore-only run; pass write_storage (current id) to the message-delivery run and to checkpoint cleanup. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Replace state._state.get(...) protected access with new public is_initialized() method on DeclarativeWorkflowState (also clearer intent for the continuation detection use case). - Add narrow pyright ignores for the Any-typed trigger paths that pyright cannot fully narrow (the list[Message] isinstance loop and the fallback-DefaultTransform branch). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

github-actions

Automated Code Review

Reviewers: 1 | Confidence: 95%

✓ Design Approach

The patch fixes the immediate continuation bugs, but two parts of the new design still mis-handle multi-turn state. In declarative workflows, the continuation path now replays the entire incoming session history back into already-restored Conversation.* state, so chat history will grow with duplicates on every turn. In foundry hosting, the new unconditional restore-only call can leave WorkflowAgent.pending_requests populated, causing the subsequent user-message call to be interpreted as request responses instead of a fresh turn. Both issues stem from layering new behavior on top of existing stateful abstractions without accounting for what those layers already persist.

Automated review by alliscode's agents

* Add Workflow.reset() public method as recovery escape hatch when an in-flight run aborted (e.g. WorkflowConvergenceException) and the workflow is not checkpointed. Update the in-flight messages guard's error message to point callers at it. * Add test_workflow_run_inflight_messages_guard exercising both the guard (sync + streaming) and the reset() recovery path. * Add test_workflow_reset_rejects_concurrent_runs to lock down the in-progress guard on reset. * Add test_as_agent_continuation_preserves_prior_state covering the is_continuation branch in _ensure_state_initialized: stamps a marker between calls and asserts it survives, while Inputs.input and System.LastMessageText refresh to the new turn. * Add test_powerfx_safe.py regression tests for the Enum branch in _make_powerfx_safe (str-subclass, int-subclass, plain Enum, and Enums nested in dict/list). * Drop redundant @pytest.mark.asyncio on test_as_agent_round_trip_with_last_message_text (asyncio_mode='auto'). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Address Copilot review on _responses.py: the restore-only checkpoint replay populates self._agent.pending_requests for any request_info events captured in the checkpoint. The follow-up run(input_messages) call would then route through WorkflowAgent._process_pending_requests, which expects function-response content and rejects plain text input as 'unexpected content while awaiting request info responses'. Workflows resumed from a checkpoint that was idle-with-pending-requests would therefore fail every subsequent plain-text user turn. Inspect the loaded checkpoint and skip the pre-pass when its pending_request_info_events dict is non-empty. Workflows that don't use request_info (the current sample set) are unaffected; workflows that do will fall through to a fresh-message run rather than silently corrupting the routing state. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The exact-version pins on azure-ai-agentserver-{core,responses,invocations} forced foundry-hosting consumers to upgrade in lockstep with every beta bump from upstream. Switch to '>=current,<next-major' so we pick up patch and feature updates within the same major series without a coordinated release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The in-flight-messages guard prevented silent misbehavior, but the companion Workflow.reset() escape hatch only cleared _messages while leaving iteration count, executor-local state, and shared State mutations in an indeterminate condition after a mid-run failure. That gave a false sense of recovery. Recovery from a mid-run failure is supported only via checkpoint restoration. Keep the guard and reframe its error message accordingly; remove reset() and its tests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Resolve foundry_hosting/pyproject.toml conflict by keeping the loosened azure-ai-agentserver-* pins (>=X.Y.ZbN,<NEXT_MAJOR) while taking main's agent-framework-core>=1.2.1,<2 bump. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

- Rename Workflow._run_workflow_with_tracing parameter is_fresh_message_run -> is_continuation (default False, inverted). Fresh-message turns reset per-run accounting; continuations (checkpoint restores, responses replays) preserve it. - Simplify the in-flight-messages guard: _validate_run_params already enforces that 'message' is mutually exclusive with 'checkpoint_id' and 'responses', so the additional checks were dead code. - foundry_hosting _responses: move the restore-only pre-pass above emit_created/emit_in_progress; restore is preparation, not run progress. Drop the skip-restore gate (state preservation requires unconditional restore) and instead clear agent.pending_requests after the restore-only call. Collapse over-conditioned check. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Pending requests in the restored checkpoint represent genuinely outstanding HITL requests. The next user input may carry function responses (Responses API `function_call_output` items become FunctionResultContent / FunctionApprovalResponseContent), which `WorkflowAgent._process_pending_requests` correctly extracts and matches against the populated `pending_requests`. Clearing them after restore would silently drop that state and force the next turn to be treated as a fresh input even when the caller is responding to the outstanding requests. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Python: bump package versions for 1.2.2 release PATCH bump (1.2.1 -> 1.2.2) for the released cohort. Five PRs land in this window: - agent-framework-openai: fix file_search citations breaking the assistant- message history roundtrip (#5557) — drives the released-tier PATCH - agent-framework-orchestrations: [BREAKING] standardize orchestration terminal outputs as AgentResponse (#5301) - agent-framework-core, agent-framework-declarative: preserve Workflow.run() shared state across calls, accept list[Message] in declarative start executor, and coerce Enum values when serializing PowerFx symbols (#5531) - agent-framework-foundry-hosting: add hosted Durable Workflow support (#5531) - agent-framework-azure-contentunderstanding: new alpha package — Azure AI Content Understanding context provider (#4829) - dependencies: workspace package dependency refresh (#5555) Per lockstep convention, all 21 beta packages stamp 1.0.0b260429 and all 4 alpha packages (now including the new contentunderstanding) stamp 1.0.0a260429. Date stamp reflects 2026-04-29 Pacific. Every non-core package floor on agent-framework-core is raised to >=1.2.2; the new contentunderstanding package's stale >=1.0.0 floor is brought into line. Two follow-on fixes bundled to keep validate-dependency-bounds-test green at lowest-direct resolution: - Bump agent-framework-azure-contentunderstanding's azure-ai-content understanding lower bound from >=1.0.0 to >=1.0.1 (1.0.0 ships without proper typing — pyright reports 65 unknown-type errors) - Add pyright ignore comments to core/foundry/__init__.pyi for the new alpha package's type-stub imports, since alpha packages are not in core's [all] extra and therefore aren't installed at lowest-direct * Python: add #5552 to 1.2.2 CHANGELOG Add the streaming-span observability fix to the Fixed section. PR is on upstream/main but not yet pulled into origin/main; the code itself will land via the PR merge. * Python: address PR #5561 review feedback on dependency bounds Two packaging fixes flagged in review: 1. agent-framework-azure-contentunderstanding: add agent-framework-foundry as a runtime dependency. The package's README directs users to `pip install agent-framework-azure-contentunderstanding --pre` and the basic example imports `FoundryChatClient` from `agent_framework.foundry`, so the documented install path was failing with ImportError. Pulling agent-framework-foundry into deps makes the advertised entry path self-contained. 2. agent-framework-foundry: bump agent-framework-openai lower bound from >=1.1.0 to >=1.2.2,<2. Foundry imports private modules from agent_framework_openai (`_chat_client.py:22`, `_agent.py:34`), so resolvers were free to pair foundry==1.2.2 with older OpenAI versions that lack this release's coordinated Responses/history fix. Lockstep the floor with the released cohort to prevent mismatched installs. Both changes pass `validate-dependency-bounds-test` lower + upper at their respective packages.

alliscode and others added 4 commits April 27, 2026 12:53

Copilot AI review requested due to automatic review settings April 28, 2026 00:28

moonbox3 added the python label Apr 28, 2026

github-actions Bot changed the title ~~Feature/hosted dwf~~ Python: Feature/hosted dwf Apr 28, 2026

Copilot started reviewing on behalf of alliscode April 28, 2026 00:28 View session

Copilot AI reviewed Apr 28, 2026

View reviewed changes

Comment thread python/packages/declarative/agent_framework_declarative/_workflows/_declarative_base.py

github-actions Bot reviewed Apr 28, 2026

View reviewed changes

moonbox3 approved these changes Apr 28, 2026

View reviewed changes

alliscode and others added 2 commits April 28, 2026 08:49

alliscode force-pushed the feature/hosted-dwf branch from b355a43 to e8dfcc9 Compare April 28, 2026 18:10

microsoft deleted a comment from Copilot AI Apr 28, 2026

alliscode requested a review from Copilot April 28, 2026 18:14

Copilot started reviewing on behalf of alliscode April 28, 2026 18:15 View session

Copilot AI reviewed Apr 28, 2026

View reviewed changes

alliscode and others added 2 commits April 28, 2026 11:27

alliscode marked this pull request as ready for review April 28, 2026 18:45

github-actions Bot reviewed Apr 28, 2026

View reviewed changes

Comment thread python/packages/foundry_hosting/agent_framework_foundry_hosting/_responses.py

alliscode and others added 5 commits April 28, 2026 12:43

TaoChenOSU reviewed Apr 28, 2026

View reviewed changes

Comment thread python/packages/foundry_hosting/agent_framework_foundry_hosting/_responses.py Outdated

TaoChenOSU approved these changes Apr 29, 2026

View reviewed changes

alliscode added this pull request to the merge queue Apr 29, 2026

github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Apr 29, 2026

moonbox3 mentioned this pull request Apr 29, 2026

Python: flaky integration tests blocking merge queue (Foundry Hosting + Foundry embeddings) #5553

Open

4 tasks

Merge branch 'main' into feature/hosted-dwf

c7ab201

moonbox3 enabled auto-merge April 29, 2026 00:46

moonbox3 added this pull request to the merge queue Apr 29, 2026

Merged via the queue into main with commit 8b71f94 Apr 29, 2026
33 checks passed

This was referenced Apr 29, 2026

Bump the microsoft group with 7 updates razeone/CloudEngAgent#27

Open

Bump the dotnet group with 1 update dotnet/docs#53477

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Python: Feature/hosted dwf#5531

Python: Feature/hosted dwf#5531
moonbox3 merged 17 commits intomainfrom
feature/hosted-dwf

alliscode commented Apr 28, 2026

Uh oh!

moonbox3 commented Apr 28, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

github-actions Bot left a comment

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

alliscode commented Apr 28, 2026

Uh oh!

moonbox3 commented Apr 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Python Unit Test Overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Copilot's findings

Uh oh!

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Automated Code Review

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions Bot left a comment

Choose a reason for hiding this comment

Automated Code Review

✓ Design Approach

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

moonbox3 commented Apr 28, 2026 •

edited

Loading