Make long thread warning optional
The warning in question: “Long threads can lower response quality and use limits faster. Consider starting a new one.”
Since t3.chat consumption model has changed, I hope it would make sense to make this warning optional. I’ve been getting it on first prompt lately too and I rarely use more then 10% of me limits.
Also the warning keeps reappearing when I switch away and back to the chat tab.
Log in to comment and vote
Comments5
Amaranth Echo
Warning is much less intrusive now. Appreciate the change, thank you!
Mark Florkowski
The reason why you would get this on a first message is because you are attaching a large file or entering a very long prompt.
The warning exists because long contexts degrade model responses and are costly so they will go through your usage rather quickly
Amaranth Echo
Thank you for your reply! I understand you and your points are valid, but sending a first message with a very long initial context is a practical workflow for implementing and understanding a complex feature correctly and well for me. Having a big feature to look at and being able to further prompt about it by editing the subsequent prompt multiple times over is a big plus of t3.chat for me. Being aware of the cost of the prompt, I don’t see the need to constantly see that warning while utilizing that workflow. Hope it becomes something that can be disabled.
Mark Florkowski
makes sense. I am working on a flow that makes it a bit less intrusive.
Amaranth Echo
Will be looking forward to it, good luck with that!