You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Open Agent Flow
Click on "API Endpoint" or the <> button on the top
Select Share Chatbot
Copy the Sharing URL
Open in another browser tab or window
Chat with the bot
See "Agent Messages"
Expected behavior
Agent Messages display should be toggle-able but the required config is missing from the options. In the "embed" option, the toggle is defined as "showAgentMessages", and when that is set to false, the embedded page does not show Agent Messages. However, in the Sharing chatbot option, there is now way to do so.
Screenshots
Flow
If applicable, add exported flow in order to help replicating the problem.
Thanks, but that's not what I mean. I mean that we should allow showAgentMessages to be set up to False so that the Agent Messages are not shown at all.
The issue is that previously, it was easy to create a chatbot prototype and then share the share the full URL of the bot to others for a quick review, but now with the Agent Messages showing, it can confuse others, such as business users.
Using the "Embed" option, we can turn the messages off but setting showAgentMessages=False. But there is no such option for Share Chatbot.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Agent Messages display should be toggle-able but the required config is missing from the options. In the "embed" option, the toggle is defined as "showAgentMessages", and when that is set to false, the embedded page does not show Agent Messages. However, in the Sharing chatbot option, there is now way to do so.
Screenshots
Flow
If applicable, add exported flow in order to help replicating the problem.
Setup
npx flowise start
,pnpm start
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: