When a response is streamed, the user actually wants to read it immediately. In most cases, he is even faster or equal up with the current streamed word, which is still returned in the middle of a stream.
In such a case, it is strange to focus on the beginning of the bubble, rather than the end of the bubble.
Solution approaches:
  1. To place focus on the end of a conversation bubble.
  2. Even better, place it at the end of all conversations.
  3. Or alternatively to disable it temporarily during response generation (i.e. during the stream)
Point 1 and 2 would be more convenient than the current approach. Point 3 would even allow scrolling while the content is generated.
If point 3 is implemented, I would recommend temporarily disabling the syntax and markdown content parser as well, so that it doesn't trigger all the time, but only applies when the bubble response is finished.
Suggested by
Sascha