Python: python AG-UI : workflow.as_Agent + AgentFrameworkAgent resume return expected Content, got str

[moonbox3]

Discussed in #7502

^{Originally posted by dgsear August 4, 2026}

1. What I'm trying

• workflow.as_agent exposed via AgentFrameworkAgent
• AG-UI endpoint(texted on both invocations and FastAPI)

2. What Works

• AgentFrameworkWorkflow Path resumes correctly

3. What fails

• resume after function_Approval_request on workflow.as_agent path
• error:Response type mismatch ... expected Content , got str

4. Repro Summary

• first run emits interrupt with tool_call id
• resume with accepted +args payload
• either APPROVAL_RESUME_INVALID or Content/str mismatch depending on payload shape

5.Questions

• Is workflow.as_agent + AgentFrameworkAgent expected to support this interrupt/resume path for Content-typed workflow request_info?
• Or is AgentFrameworkWorkflow the intended adapter for AG-UI workflow resumes?

[dgsear]

Evan Mattson (@moonbox3)
Thanks for the question in the discussion #7502 . You are right that AG-UI natively supports workflows and we wrap only to reuse agent-path client tool injection (A2UI/frontend tools) that is not yet first class in Workflow run . Seems like Even When a workflow is wrapped as an agent , client tools are only injected at the outer AG-UI agent run layer , but not propogated to workflow executor tool contexts.

[dgsear]

Evan Mattson (@moonbox3) Thanks for the update , could you clarify whether this also supports A2UI scenarios for workflow as agents , as i see a PR for A2UI is already merged supporting AgentframeworkAgent adaptor. We are looking for A2UI support with either native workflow or Workflow as agent in AGUI.