Routine feedback on Studio


  • :sparkles: I liked the new dashboard interface, it’s a lot easier and pleasing to navigate

  • :gear: The new chatbot settings modal is great, much more accessible

  • :mag: The search feature is crazy useful! I like its zoom and focus behavior

  • :page_with_curl: The new emulator logs are very detailed and they will make debugging much easier

  • :checkered_flag: It’s nice that we now can snap nodes to the grid, and also select them with Shift



  1. :robot: Make the production bot available in the emulator as well, maybe with a switch or dropdown to select the environment. Because right now i can only access the production version through the dashboard

  2. :art: The chat in the dashboard should use the same style as the bot sharing page or as the emulator, they’re cleaner and snappier. Maybe standardize all chat interfaces.`

  3. :eyes: Have better markdown support in the emulator, so we have the actual view even on dev mode.


  1. :gear: The button Create chatbot in the dashboard should open a modal with templates to choose from and basic setup like bot name and language instead of creating an bot directly, so we don’t need to edit those after.

  2. :gear: Have the bot settings available in the dashboard, the same modal from the Studio would be nice!


  1. :memo: We should be able to change the message type after having selected one and defined values. Right now the change message type disappears after having typed in stuff. The button should remain and if the user wants to change types he must confirm losing the current settings.

  2. :stopwatch: Option to select how long is the conversation timeout, right now it’s just 5 minutes which is too short for some use cases.

  3. :eight_spoked_asterisk: I would like to able able to select many nodes or cards at once using CTRL, it would help in situations where I want to delete or move several items at once.

  4. :label: The search results should have a label to identify the result type - node / card (with type) / transition / custom code / workflow etc.

  5. :computer: Sometimes the AI generates custom code with uncommented free text, which leads to compilation errors.


  1. :lady_beetle: Values are being added as default to array variables when I run array.push()

  2. :lady_beetle: When I update the label of a choice, the transition is removed

  3. :lady_beetle: If i define a default value to a number I can’t remove it anymore, I should be able to make it empty/undefined by default instead of 0

  4. :lady_beetle: When a workflow ends because no transition is matched in a node the chat ends but it doesn’t transition to the conversation end flow. Maybe it should? Since it’s technically an end.

  5. :lady_beetle: The location title and address is not shown in Telegram nor WhatsApp, the bot sharing page doesn’t show the map nor the address/title, only the GMaps link, and the emulator shows only the title and the address with a link to GMaps. Could we have the same behavior of a map and labels on all (or most) interfaces?

Let me know if you need clarification on any!


@devguilherm AMAZING! What else could I add here? :heart_eyes:

Thank you so much once again for the feedback. Your contribution has been tremendous!

This post is going straight to the Product team. We are beyond lucky to have you in the Community! :handshake:

We’ll keep you posted as things get fixed. :raised_hands:

Hey Sabrina, there are actually a few things! :laughing:

FEEDBACK :speech_balloon:

  • :repeat: It’s amazing that we now can restart conversations from a previous point and all data will be restored too, helps wonder with dev and debugging!

  • :gear: It’s nice that when you click the flow editor background the variables show up without the need a button. I also liked the new behavior of expanding the active panel (workflow properties / emulator)

SUGGESTIONS :sparkles:

  • Flow editor

    • View/Style

      1. :yellow_circle::bulb:Highlight the right active nodes/cards. Right now, it’s very easy to mistake which one is selected, which can lead to accidental deletions. See example below.

      2. :yellow_circle::floppy_disk: The position in the flow editor should be saved so that when we open a workflow or switch tabs, we have the same view as when we left. It’s cumbersome to have to drag around every time you switch flows.

      3. :green_circle::arrow_right: Better separation of transitions leaving a node. Take a look at the choices below, we can’t tell which one goes where.

      4. :green_circle::flashlight: When we select a transition card, only the transition of that card should be highlighted instead of all transitions, so that we can know at once where it goes.

    • Variables

      20.:red_circle::zero: The default value of boolean variables should be undefined, or at least allowed to be undefined. Default for number variables also should be null or undefined instead of 0, and we should be able to clear them after having set a value in the input, with a button like below.
      For my use case and many others, I guess, having a valid value like this is not ideal and requires state handling (has X variable being changed)

      1. :red_circle::question: Allow variables in the retry messages too and make the input big like the main prompt message.

      2. :yellow_circle::memo: When a variable name is changed, ask if the user wants to change it everywhere in the workflow. Very often we need to change names and having to go through every custom code and transition is cumbersome and is very error prone. Right now, it updates the capture cards only.

      3. :green_circle::eyes: Being able to see where the variables are used, not just the number of times. A simple list on hover, or we could click the counter tooltip and it would open the search with the variable name prefilled so we can find its uses easily.

      4. :green_circle::no_entry_sign: When a capture card doesn’t store information in a variable, the “Skip if variable is filled” checkbox should be disabled (greyed out), since it doesn’t apply.

    • Node settings

      1. :yellow_circle::white_check_mark: In the node settings, we could have a personality rewrite toggle to choose whether we want the rewrite to be enable on that node. It should be disabled/greyed out when the Bot Personality is disabled, and it should be enabled by default when the Bot Personality is on. Fan art below:
        fan art

      2. :green_circle::robot: Feature to generate cards for a node (with ai tasks, transitions and all) based on the description provided - This would be sick :ok_hand: and would speed up development even more!

    • Emulator

      1. :red_circle::arrow_left: A button to go back to the previous turn. The Replay from node feature is very good already but it still requires us to find the desired node in the editor and click it, when sometimes we just need to go back a few turns.
      2. :yellow_circle::arrows_counterclockwise: Show the custom code execution status in the emulator logs.

  • Environments

    1. :yellow_circle::eye: Hide environment variables by default on the dashboard

    2. :yellow_circle::label: Flow versioning with Git integration.

    3. :green_circle::gear: Create and manage environments (dev, prod, beta)

    4. :green_circle::round_pushpin: Selection of current/production environment

  • API

    1. :red_circle::bust_in_silhouette: One of the conversation tags for WhatsApp (and other channels) should be whatsapp:userName, for storing the user’s display name which the messenger already provides. That way we can know more of the user’s info by default.

    2. :green_circle::date: The conversation updatedAt should be replaced every time there is a new message in a conversation, instead of just when it is actually updated. It would help when listing the conversations and ordering them by the most recent one.

  • Other

    1. :yellow_circle::speech_balloon: Inbox interface for managing users, conversations, and messages. It would be a GUI for the existing API, with easy access from the dashboard.

    :computer: By the way I am building a dashboard while you don’t release an official one haha. I will make it available in GitHub in a few days, but here’s a preview:

    1. :yellow_circle::world_map: Roadmap of features and releases so that we know exactly what’s being worked on and what are the time estimates (You could use a tool like ProductPlan, to avoid building a whole interface for that).
    2. :green_circle::new: New release summaries, so we know exactly what was added/improved/fixed

BUGS :beetle:

  1. :fire::lady_beetle: If I choose to replay the conv from another node the event debugger doesn’t change, so I can’t know what the state of the conversation was back then, I need to wait for a turn to get the updated values.

  2. :fire::lady_beetle: List entities variables don’t show up on flow transition cards as input variables, neither as input for AI task examples.

  3. :fire::lady_beetle: Retry messages of prompts with buttons don’t show the buttons, just the message. The bot should show the options again otherwise the user may not know the options to choose from. To get the desired behavior I would be forced to use a handle failure transition, but the reprompt message would be the same, and I would need to manage the retry count.

  4. :fire::lady_beetle: Sometimes Capture cards (with “skip if variable is filled” enabled or not) extract the value from the previous response. This happens at least with WhatsApp and Telegram.

  5. :fire::lady_beetle: Sometimes messages are not actually sent to WhatsApp, notice the conv below.

    I answered yes to a confirmation, and then I should be prompted again, but the next prompt is not shown. You can see in the logs that the bot sends the message (line 292), but it’s not displayed.

  6. :fire::lady_beetle:Sometimes the bot mistakes the desired option in a choice prompt. You can see below that I selected an option (:x: Cancel), but the engine extracted another one (:arrow_left: Go back) - This is on WhatsApp only. I think the issues are with the emojis - they are properly displayed on the action buttons on WhatsApp, but the answer text is not sent back correctly or Botpress has a problem reading it. (Proposed solution - the engine should ignore the � (which may be the cause) and try to match only the text)

  7. :lady_beetle: When I rename a node name or a variable used in a capture information card, I sometimes get errors such as “Node not found” in transitions, and values being attributed to variables with the old names - this is on the emulator

  8. :lady_beetle: Example of object outputs for AI Task are not being updated, and also the object editor is quite laggy and buggy.

  9. :lady_beetle: The bot language selected option is being reset to default every time you open the settings panel - only the selection though.

  10. :lady_beetle: Updated choice labels are not shown in the flow editor, the old values remain until readding the transition.

  11. :lady_beetle: Hovering over any variable that hasn’t been filled yet shows a strange error message:

  12. :lady_beetle: Not exactly a bug, but a problem - the bot is too slow on WhatsApp, even with personality disabled and in routes with no ai tasks, it sometimes takes many seconds to get a response.

  13. :lady_beetle: Sometimes the Dashboard Logs get stuck and the refresh button doesn’t work, so I need to reload the page to get the new logs.

:speech_balloon: I understand you guys are working on a lot of new features and fixes right now and this here is quite an extensive list, :pray: but I ask that you give some special attention to these issues and possible improvements because I think Botpress is almost too unstable for production right now.

Tell me if you need any details. Cheers!

1 Like

This is amazing feedback, I read all of your items one by one, we’ll try to address them among our priority list.

As for this one

It’s Upcoming, don’t worry :wink:

1 Like

I appreciate it, thanks a lot!

I updated the list with colors emojis to identify what I think it’s more urgent right now, maybe it will help you guys parse easier through the list!

Nice!!! :rocket: :rocket:


Hey @sabrina, please update this item with the information that it only happens when talking to the bot through the emulator.


Hey @devguilherm ,

First of all, thanks for all of that!!!

I need some clarifications/comments.

Can you give me more info about this?

I understand your comment, will add it, but if you cleared the text the button will show up

Is this still happening?

Isn’t that the same as the one above it?

This one is not clear, can you elaborate more?

And this one too, please.