Fredrik Strand Oseberg

Hi @Gaspar1234 Yes, you can instantiate different clients with different tag configurations to achieve what you want. If you instantiate them in the same context in your application and use...

Things to think about: * Today we have a default project, this has proven to create some confusion for our users. Should we think about changing it in the next...

Hi there! Thanks for this suggestion, we'll look into that. I agree that it would be a useful addition.

> Adding on the previous comment, I have a doubt on if we should extend the existing `useEventSearch` hook or create a new one altogether for this use case Hi...

All of your messages live inside the messages array. Simply use the setState function passed to the actionprovider or widgets to clear out the messages array and start the conversation...

Deprecation discussion: * Custom strategies - Is there any use case that couldn't be handled elegantly with constraints? * Builtin strategies - Everything should now be customizable with a single...

> Interesting points! > > > Builtin strategies - Everything should now be customizable with a single strategy and constraints combinations. No reasons to have multiple anymore. > > I...

@chtseac You do actually receive a number of props in the custom message that you can use if I understand your use case correctly. Here's the code that renders the...

@chtseac You're right. You'd need to create a unique identifier in state for this to work, and then it would update all of the other messages in the chat history....

You could simply set this into state. The whole state object will be passed to your widget.