Agentic Todo example: where to put it?

[Emmanuel Bernard]

Hey folks,

I now have (thank you Devoxx) an Agentic Todo app demo that is the classic Todo app but that can try and do your todos for you via A2A remote agents.

I like it and I find it a good example but I wonder how to ship it? 

I could add it to the main todo app but it makes this intro demo more complicated and I think that's not a great idea as newcomer is still a primary target.

The second problem is that this demo relies on one Weather agent in Quarkus and one Movie agent in JS, to which you can also add A2A inspector.

The third problem is that you need API keys:

- the movie agent does need a TheMovieDataBase API key and a GEMINI key

- the todo app needs a Open AI key

So it's a great new user experience in the zero to woohoo in 10 mins scale. (Even though my code gracefully degrade when agents are not available).

So I think we should either

1. fork the repo and create an agentic-todo-app-demo

2. use a different branch in the same repo

I think 1 is better in discoverability. We _could_ keep them more aligned in approach 1 but it's still cherry picking.

WDYT?

Emmanuel

PS: is there a way to put the weather agent and the Movie agent as dev services easily? That would simplify the demo a bit for people.

Generally allowing people to put another Quarkus app as a dev serivce to the main app could be interesting, e.g. doing `git clone other-microservice ; quarkus dev`

[Georgios Andrianakis]

On Wed, Oct 8, 2025 at 7:16 PM 'Emmanuel Bernard' via Quarkus Development mailing list <quark...@googlegroups.com> wrote:

Hey folks,

I now have (thank you Devoxx) an Agentic Todo app demo that is the classic Todo app but that can try and do your todos for you via A2A remote agents.

I like it and I find it a good example but I wonder how to ship it? 

I could add it to the main todo app but it makes this intro demo more complicated and I think that's not a great idea as newcomer is still a primary target.

The second problem is that this demo relies on one Weather agent in Quarkus and one Movie agent in JS, to which you can also add A2A inspector.

The third problem is that you need API keys:

- the movie agent does need a TheMovieDataBase API key and a GEMINI key

- the todo app needs a Open AI key

So it's a great new user experience in the zero to woohoo in 10 mins scale. (Even though my code gracefully degrade when agents are not available).

So I think we should either

1. fork the repo and create an agentic-todo-app-demo

I vote for this

 

2. use a different branch in the same repo

I think 1 is better in discoverability. We _could_ keep them more aligned in approach 1 but it's still cherry picking.

WDYT?

Emmanuel

PS: is there a way to put the weather agent and the Movie agent as dev services easily? That would simplify the demo a bit for people.

Generally allowing people to put another Quarkus app as a dev serivce to the main app could be interesting, e.g. doing `git clone other-microservice ; quarkus dev`

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CANYWk7OJg1R8b_CuqUnLKfZaM5qQJiixpQ7KSYd3f9Wy0c3yOw%40mail.gmail.com.

[Phillip Kruger]

What about converting the todo app to a multi-module app ? 

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALeTM-mnRaS89J6YhFk8nVxoLaynfyAsYdpVznpfOZ6WwNJ9CQ%40mail.gmail.com.

[Georgios Andrianakis]

On Mon, Oct 13, 2025 at 1:58 PM Phillip Kruger <phillip...@gmail.com> wrote:

What about converting the todo app to a multi-module app ? 

I believe it will negatively impact the user experience for people just looking for a typical to-do application in Quarkus 

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CAEyd7D5LEM8TBr7jHpcdcKjRD7u%2BoBpYMRTW82tZCGUSv86Vjg%40mail.gmail.com.

[Phillip Kruger]

Yeah maybe. The other option is a new GH org, with multiple repos ?

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALeTM-mDGLCKvTYMY7AZBcPmAp9mxoa17ev8Wfco5uo%3Ds4SY5g%40mail.gmail.com.

[Sanne Grinovero]

Would it be too complex to be listed among the other quickstarts?

 - https://github.com/quarkusio/quarkus-quickstarts

Or do we want to keep demos strictly separated from quickstarts? They serve slightly different purposes, but so far we've been blurring the distinction.

To view this discussion visit https://groups.google.com/d/msgid/quarkus-dev/CALeTM-mDGLCKvTYMY7AZBcPmAp9mxoa17ev8Wfco5uo%3Ds4SY5g%40mail.gmail.com.