Usage/rate-limit page gives no explanation when a session is blocked

Hit a Claude Pro usage block while using Claude in Xcode (default Xcode intelligence settings) after what felt like only a few requests. Was locked out for ~3 hours.

Problems:
1. No indication in Xcode of *why* the request failed or that it was a usage-limit block vs. an error.
2. The usage page at claude.ai/settings/usage shows a percentage/bar and a reset time, but no breakdown of what consumed the budget (e.g. how much came from Xcode vs. other surfaces, or why a "couple requests" used so much).
3. No proactive warning before hitting the cap.

Requesting: clearer in-product messaging when a request is blocked by rate limits (not just a generic failure), and a usage breakdown by surface/session on the usage page.

Start by tracing the Claude in Xcode request-failure path and the claude.ai/settings/usage page described in the issue. Define how rate-limit blocks, usage by surface or session, and pre-cap warnings should be exposed; done means blocked requests are distinguishable from generic errors and the usage page explains consumption and reset behavior.

Written by the indexing model from the issue text.