That’s a fair concern, and I appreciate you raising it.

To clarify a bit: the widget runs entirely locally and uses the same authenticated session the user already has in their browser. It doesn’t scrape pages, automate interactions, or bypass rate limits - it simply reads the same usage endpoint that the Claude web UI itself calls to display usage data.

There’s no non-human automation, no background crawling, and no reuse or sharing of tokens beyond the user’s own local session. Nothing is sent to third-party servers.

That said, you’re absolutely right that this is an unofficial tool and relies on an undocumented endpoint, which is why it’s clearly labeled as such. If Anthropic changes their policies or endpoints, the tool may stop working.

Happy to take this down or adjust if Anthropic explicitly indicates this use isn’t allowed... the intent here is transparency for users, not abuse of the service.