Skip to content

Conversation

yaron2
Copy link
Member

@yaron2 yaron2 commented Aug 15, 2025

This PR adds an example of creating an agentic durable workflow with human in the loop. The quickstart has 3 variants - Anthropic, OpenAI and Google Gemini. This quickstart shows how Dapr Workflows alone could be used with existing, well known SDKs to create stateful long running LLM workflows.

@yaron2 yaron2 requested review from a team as code owners August 15, 2025 20:55
@yaron2 yaron2 requested a review from alicejgibbons August 15, 2025 20:55
@alicejgibbons alicejgibbons added the do-not-merge Do not merge the PR label Aug 26, 2025
@bibryam
Copy link
Contributor

bibryam commented Aug 26, 2025

This is great demonstration of Dapr APIs combined.
That said, it is more than quickstart that are focused around a single API. This has WF and Conversation API, plus requires token to 3rd party services. IMO this is a great sample, that should be linked from the conversation API docs and quickstarts

@alicejgibbons
Copy link
Contributor

Thanks @bibryam agree, @yaron2 happy to help you with writing docs here but due to the multi-api nature, we need to place this elsewhere. What about https://github.com/dapr/samples/tree/master or a new ai-samples repo?

@yaron2
Copy link
Member Author

yaron2 commented Sep 11, 2025

This is great demonstration of Dapr APIs combined. That said, it is more than quickstart that are focused around a single API. This has WF and Conversation API, plus requires token to 3rd party services. IMO this is a great sample, that should be linked from the conversation API docs and quickstarts

This is a single API, Workflows in combination with different LLM providers

@yaron2
Copy link
Member Author

yaron2 commented Sep 15, 2025

Directory structure changed

@alicejgibbons
Copy link
Contributor

alicejgibbons commented Sep 16, 2025

Directory structure looks good and going forward we can add new AI-focused samples for each Dapr Building block API as follows:

  • AI/workflows/...
  • AI/pubsub/...
  • AI/jobs/...

I am leaning towards instead of the "human_in_the_loop" name to use something like "external_system_interaction" (as per tutorials to keep the naming convention consistent?

Signed-off-by: yaron2 <[email protected]>
@yaron2
Copy link
Member Author

yaron2 commented Sep 17, 2025

Directory structure looks good and going forward we can add new AI-focused samples for each Dapr Building block API as follows:

  • AI/workflows/...
  • AI/pubsub/...
  • AI/jobs/...

I am leaning towards instead of the "human_in_the_loop" name to use something like "external_system_interaction" (as per tutorials to keep the naming convention consistent?

Changed

Signed-off-by: yaron2 <[email protected]>
Copy link
Contributor

@bibryam bibryam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, a few minor points

Signed-off-by: yaron2 <[email protected]>
Signed-off-by: yaron2 <[email protected]>
Copy link
Contributor

@alicejgibbons alicejgibbons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@alicejgibbons alicejgibbons merged commit bb2eaed into dapr:master Sep 18, 2025
5 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge Do not merge the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants