Hi @michael that's a great question!
That is not the case. If you wanted to not have a pause you would use a Listen behavior with the
heyJibo argument set to true as in the following screenshot. This would allow the listen to require heyJibo to be heard but not to have a pause needed after it:
I can also provide some detail around why Jibo took the slow path in our update. Our desire was to show off the user interaction with Jibo and to give parts of the interaction, like the LED ring glowing when Jibo was listening, time to be seen.
For that reason the parts you are referencing utilized an Idle behavior with a SucceedOnEmbedded decorator which was then followed up with the Listen behavior itself. This is why, from a development level, those interactions had the pause in them.
I hope this clears things up!