← Back to context

Comment by exclipy

5 hours ago

I think the first message consumes disproportionately much percentage because it's not cached and includes the system prompt, tools, etc.

Here comes the "you're using it wrong" defence!

Let's be perfectly clear: if user actions had anything to do with hitting these limits, the limits would be prominently displayed within the tool itself, you'd be able to watch it change in real time, and you'd be able to pinpoint your usage per each conversation and per each message within that conversation.

The fact that you cannot do that is not because they can't be bothered to add such a feature, but because they want to be able to tweak those numbers on the backend while still having plausible deniability and being able to blame it on the user.

Instead, the little "usage stats" they give you is grouped by the hour and only split between input and output tokens, telling you nothing.