v2.99.1
The hosted connection now counts requests by an opaque fingerprint of the authenticated account instead of the server's internal network address. Two people can run full assistant sessions at the same time without sharing one limit.
The account fingerprint is one-way and exists only in memory. Bearer tokens are never used as rate-limit keys, so refreshing a connection cannot reset its account allowance.
The issue surfaced only after running every available tool across two accounts in quick succession. The same end-to-end production test now completes cleanly without one account affecting the other.
One short email when something meaningful ships. No streaks required.