UsageMeterv1.2.28

• Nuevo

  Ask Claude from the address bar — type "cl", press Space/Tab, type your question and hit Enter: a Claude chat opens with the question pre-filled. Works on Chrome and Firefox desktop, no extra permission needed

• Nuevo

  "Claude finished replying" notification — start a long generation, switch to another tab, and UsageMeter sends a system notification the moment the response completes (only when the tab is actually in the background, once per generation, and never on intermediate Auto-Reply continuations). Clicking it brings you back to the conversation. Toggle under Settings → Notifications

• Nuevo

  Send later in SmartQueue — queued messages can now be scheduled for a specific time (+1h, +3h, tonight 20:00, tomorrow 09:00, or any custom time). Scheduled items survive a 429 drain and browser restarts, fire even when the claude.ai tab is not focused, and can be unscheduled with one click. If no claude.ai tab is open at the chosen time, the message goes out the next time one is

• Nuevo

  The first-run setup is now a real feature tour — every UsageMeter feature is explained AND configurable right from the wizard (usage indicators, page tools, notifications, toolbar badge bucket), with live apply to open claude.ai tabs and a "good to know" section for the zero-config goodies (omnibox, SmartQueue, exports, multi-account). Re-running it no longer wipes preferences it did not show

• Corrección

  Chrome Web Store rejection ("remotely hosted code in a Manifest V3 item") — the bundled PDF library (jsPDF) ships a CDN fallback script URL inside a code path the extension never calls, and the store scanner flags any remote script URL found anywhere in the package. The build now scrubs every remote script URL from that bundle AND refuses to produce a ZIP if any remote script/stylesheet reference ever reappears in the package. Belt-and-braces: the setup page also stopped loading its three font families from Google Fonts — all 17 font files are now bundled locally, so the wizard renders identically offline

• Mejorado

  All the new strings of this release (feature tour, favicon ring, CSV export, finished-reply notification) are translated in the 34 supported languages instead of falling back to English

• Nuevo

  Favicon usage ring — the claude.ai tab icon now wears a colored ring showing your 5h usage at a glance (green < 50%, orange < 75%, red above), updated live and resilient to claude.ai rewriting the tab icon while you navigate. Toggle it under Settings → Features → "Favicon usage ring"

• Nuevo

  Export your usage history as CSV — a small button on the charts in the usage details view downloads every recorded data point (all accounts, all categories, ISO timestamps), because your data belongs to you

• Corrección

  The Weekly Recap notification was double-broken: it averaged a field that does not exist in the usage history (so it always reported "avg 0% usage"), counted every data point twice (per-account + global aggregate), and pointed at a non-existent icon file — which makes Chrome silently drop the notification, so most users never saw it at all. It now reads the right field, counts each point once, uses the real icon, and reports the weekly peak with its day (e.g. "peak 91% on Tuesday"). Same dead-icon fix applied to the SmartQueue "message sent" notification

• Corrección

  Usage percentage could freeze at a stale value for days — most visible on Firefox — because the background usage fetch was failing silently and nothing aged the cache out, so the popup kept showing the last-good number (a permanent "97%" for some users). Two-part fix: the content script now ages the cache out after 2 min and refreshes via a same-origin direct fetch from claude.ai (page cookies always attach, even on Firefox), self-healing a stuck number whenever a claude.ai tab is open; and the popup forces a fresh background fetch + retry when its cache is older than 3 min instead of trusting it

• Corrección

  The "updated X ago" stamp under the usage cards always read "just now", even on data that was days old — the popup read cache.ts / fetchedAt while the background wrote cache.timestamp (two writers, mismatched field names), so it always fell back to the current time. It now reads the correct field and shows days (e.g. "9d 4h"), making stale data obvious instead of looking live. Both cache writers now stamp a unified timestamp + source field

• Nuevo

  The data-freshness stamp under each usage card is now a refresh button — click it to force a fresh fetch. The sync icon spins while refreshing and the whole stamp turns amber when the displayed data is stale, so a stuck percentage is both visible and one click away from recovering

• Corrección

  Removed a no-op Cookie request header the background fetch set "for Firefox" — Cookie is a forbidden fetch header the browser silently strips, so it never did anything; authentication rides on credentials: "include" and, on Firefox, the same-origin content-script path. The background also self-heals a stale lastActiveOrg cookie: on a 403/404 from the usage endpoint it re-derives the active organization from /api/organizations and retries once, recovering users who switched or left an org

• Mejorado

  The background now records the outcome of every usage fetch (last HTTP status, last error, last attempt + last success timestamps under usagemeter_usage_fetch_status), so a failed refresh can be diagnosed — 401/403 means re-login, a network error means offline — instead of the percentage just silently freezing

Todas las versiones