Is Workflow Streams intended as the message-queue bridge for PydanticAI's TemporalAgent event_stream_handler?

[Anjayg]

Pydantic AI's Temporal docs state that Agent.run_stream()/run_stream_events()/iter() aren't supported inside a Temporal-backed run, and instead recommend an event_stream_handler on TemporalAgent, noting that getting events from the handler (running inside an activity) out to the workflow/frontend requires "an external system... like a message queue."
Question: Is Workflow Streams (temporalio.contrib.workflow_streams) the intended/recommended implementation of that "message queue" for this use case — i.e., publishing from within an event_stream_handler via WorkflowStreamClient.from_within_activity(), and having an external HTTP/API layer subscribe to the same workflow's stream to receive those events? Or is there a different pattern the SDK team recommends for bridging activity-side streaming output to an external consumer?

[brianstrauch]

Thanks for bringing this up! Temporal Workflow Streams is a perfect solution for this. Opened pydantic/pydantic-ai#6619, and will fast-follow with a PR once the issue is approved by the Pydantic team.