I’d rather it be more informative. How many tokens is the trigger for this model’s warning, and how many has the current conversation used up? Same with the message when the thread limit is reached. What is the thread length cap? How many input tokens will be accepted, if any?
It’s nice seeing how many output tokens were used in a turn. Would be even nicer to see how many input tokens were used. Random example from one app: TTFT: 4.0s Total: 19.3s 65.1 tok/s In: 67141 Out: 1255 Total: 68396
(That app also allows inspecting the API request details, request headers, exact request JSON, parsed response, raw provider stream… That might be asking for too much here, but hopefully asking for the token count isn’t.)
Maroon Quesadilla
I think it would be nice to be able disable similar kinds of messages as well, like when we’re low on credits or when the API key is being used. Or at least move the warnings in a place that doesn’t pertrude as much. I don’t like having to constantly close these toasts.
Mark Florkowski
Team
Most of these warnings are dismissed for the session when you dismiss them, and there are a few that once dismissed a few times will offer the option to permanently dismiss. If there is a specific message that you feel like you are encountering a ton that you shouldn’t, let me know and I can take a look.
Indigo Sandwich
Hey @Mark Florkowski , it’s just after you finish your quota, then you get this all the time:
If i dismiss, then search again later I get it again
Mark Florkowski
Team
That seems correct? If the message limit banner did not appear every time where it applies, there would be no indication of why your message was blocked.
Log in to comment and vote
Comments5
Aqua Chameleon
I’d rather it be more informative. How many tokens is the trigger for this model’s warning, and how many has the current conversation used up? Same with the message when the thread limit is reached. What is the thread length cap? How many input tokens will be accepted, if any?
It’s nice seeing how many output tokens were used in a turn. Would be even nicer to see how many input tokens were used. Random example from one app: TTFT: 4.0s Total: 19.3s 65.1 tok/s In: 67141 Out: 1255 Total: 68396
(That app also allows inspecting the API request details, request headers, exact request JSON, parsed response, raw provider stream… That might be asking for too much here, but hopefully asking for the token count isn’t.)
Maroon Quesadilla
I think it would be nice to be able disable similar kinds of messages as well, like when we’re low on credits or when the API key is being used. Or at least move the warnings in a place that doesn’t pertrude as much. I don’t like having to constantly close these toasts.
Mark Florkowski
Most of these warnings are dismissed for the session when you dismiss them, and there are a few that once dismissed a few times will offer the option to permanently dismiss. If there is a specific message that you feel like you are encountering a ton that you shouldn’t, let me know and I can take a look.
Indigo Sandwich
Hey @Mark Florkowski , it’s just after you finish your quota, then you get this all the time:
If i dismiss, then search again later I get it again
Mark Florkowski
That seems correct? If the message limit banner did not appear every time where it applies, there would be no indication of why your message was blocked.