zlacker

>>meetpa+(OP)
I agree it's very good but the UI is still usually an unusable, scroll-jacking disaster. I've found it's best to let a chat sit for around a few minutes after it has finished printing the AI's output. Finding the `ms-code-block` element in dev tools and logging `$0.textContext` is reliable too.

>>herpdy+Y4
I've noticed this has gotten a bit better lately, they have obviously been making a lot of UI changes to studio. But yeah, the scroll-jacking as response chunks are streamed in is incredibly frustrating since the model is pretty wordy.

I should add as well, on long complex threads the UI can become completely unusable. I'll hover over the tab and see it using over 2Gb of memory in chrome. Every so often I have to open a completely new tab, cut-n-paste the url and continue the conversation in that new tab (where the memory tends to drop back down to 600MB).