feat: Add buttons to suggest agency tools

[marcelklehr]

Kooha-2025-12-11-15-02-25.webm

These buttons would only be present if context_agent is enabled.

[marcoambrosini]

I'd use tertiary buttons here and a flex layout for the container, wrapping them only when there's no available space.

[marcelklehr]

I'd use tertiary buttons here and a flex layout for the container, wrapping them only when there's no available space.

@marcoambrosini Good point! Thanks! What do you think about the general idea?

[marcelklehr]

[jancborchardt]

Considering they are hardcoded suggestions, I’d say the first one is better as:

• What’s the weather tomorrow?

Automatically taking your location from the profile.

And just layout-wise:

• It would be good to put the suggestions directly above the input field so it’s related
• Left-align them
• Display them more as chips, so it seems a bit clickable (I preferred secondary to tertiary, but I get the concern with the nav on the top)

[marcelklehr]

What’s the weather tomorrow?

Agreed. Context agent doesn't offer this, yet, though :S

[jancborchardt]

Agreed. Context agent doesn't offer this, yet, though :S

Is the problem the "tomorrow" part or the "place" part? Cause we could also do "What’s the weather today?", automatically taking your city from the profile, or asking a follow-up if it’s not set? Would just be strange if we hardcode "Berlin".

[marcelklehr]

"What’s the weather today?", automatically taking your city from the profile

Yep, we can do that :)

[marcelklehr]

@marcoambrosini mentioned that it might be nice to group suggested prompts by categories (maybe apps?) and only display the category names in the buttons, instead of the full prompts

[jancborchardt]

@marcoambrosini mentioned that it might be nice to group suggested prompts by categories (maybe apps?) and only display the category names in the buttons, instead of the full prompts

Yeah, we talked about that (also e.g. vertically aligning the input field on emptycontent, like others do) – but I would recommend to tackle this step by step to prevent blocking or overloading this. Let’s get this adjusted and in, and then continue to the next PR.

Does that make sense @marcelklehr? :)

[marcelklehr]

In my humble opinion, the NcChip compomnent looked worse and was less a11y friendly. So I stuck to the tertiary buttons for now:

[jancborchardt]

Yup, let's go with this and then we can continue with the other changes @marcoambrosini and you suggested. :)