CLACOROO
EN IT
Download

Quota notifications

CLACOROO can show system notifications when one of your Claude quotas (Session, Weekly, Weekly Sonnet) crosses a threshold. The result: you get a desktop alert before you’re cut off mid-session, instead of discovering it when a request fails.

Notifications work whether you’re signed in to claude.ai or using an API key — the source is the same quota the Dashboard displays.

Overview

The Notifications panel lives in Settings, below the API key panel. It has:

  • A master toggle to enable / disable quota notifications entirely
  • A row per threshold (80% warning, 95% critical, 100% reached) each one independently toggleable
  • A Test notification button to verify your OS actually delivers them
  • A Data refresh frequency selector to choose how often the Dashboard data is re-checked (see below)
  • A short note explaining that notifications are rate-limited (one notification per threshold every 12h, to avoid spam)

What it shows

Thresholds

By default, CLACOROO watches three thresholds per quota:

ThresholdMeaning
80%Warning — you’ve used four-fifths of the quota
95%Critical — almost out, plan accordingly
100%Reached — the quota is exhausted; requests will be limited until reset

When a threshold is crossed for a quota, CLACOROO fires one system notification per quota+threshold combination, then waits 12 hours before firing the same one again — so a Weekly bar bouncing around 80% doesn’t spam you.

Check cadence (configurable)

How often CLACOROO refreshes its data is up to you. The Notifications panel has a Data refresh frequency setting: pick an interval from 30 seconds up to 60 minutes, or Manual to refresh only when you press the Refresh button. The first refresh runs as soon as the app opens.

This same frequency drives all the live Dashboard data, not just the quotas:

  • the quota bars (Session, Weekly, Weekly Sonnet);
  • the context estimate (plugins’ always-on / on-invoke tokens);
  • the statistics and KPIs (plugins, skills, agents, MCP, hooks…);
  • Plugins by weight (context window);
  • Claude Code usage (sessions, messages, tokens, estimated API value, streaks, favorite model…) and per-project data.

One setting, no separate cadences to keep in sync.

  • Short intervals keep everything fresher but use the API more; long intervals (or Manual) use it less.
  • The chosen frequency applies immediately, without restarting the app.
  • If the app is closed, no checks fire — system notifications are tied to running apps on every platform.

If you see the “Updates paused — the API is rate-limiting requests” note, Anthropic’s API is rate-limiting: CLACOROO backs off on its own and resumes later. To avoid it, increase the refresh interval (e.g. from 30 s to 5 min): fewer requests, lower chance of rate-limiting.

”Last update” badge

In the center of the Dashboard header there’s a “Last update” badge: a live minutes-and-seconds counter (e.g. 1m 23s) telling you how recent the data is, followed by the active mode — “Auto every 30 s” (or whatever interval you picked) or “Manual”. It covers the whole Dashboard, not just the quotas.

  • In Auto mode the counter resets exactly on each refresh.
  • Pressing Refresh (top right) refreshes everything and resets the counter to zero (it forces a real fetch, not the cache).
  • In the Account panel the same info appears as a discreet line under the quota bars.

”Test notification”

A button to send one immediate notification right now. Useful to:

  • Verify your operating system grants the permission
  • Check that “Do Not Disturb” or focus mode isn’t filtering the app out
  • See what the notification actually looks like on your machine

The test notification has a clear “test” label, so you’ll never confuse it with a real one.

Common tasks

How to enable notifications

  1. Open Settings → Notifications
  2. Toggle the master switch on
  3. (Optional) Toggle individual thresholds off if you only care about, say, 95% and 100% but not 80%
  4. Click Test notification — if you see it, you’re done

How to test notifications

  1. Click Test notification in the Notifications panel
  2. Look for a system notification with the CLACOROO icon
  3. Also check your Notification Center in case “Do Not Disturb” hid it
  4. The in-app toast always fires (“Notification sent — if you don’t see it, check permissions”) so you know the click worked

How to disable notifications temporarily

Use your operating system’s “Do Not Disturb” / focus mode instead of toggling CLACOROO off. That way you don’t forget to turn the warnings back on tomorrow.

Tips & shortcuts

  • The notifications use system-level alerts (macOS Notification Center, Windows Action Center, Linux desktop notifications) — they survive across app restarts
  • The 12-hour cooldown per threshold is per-quota: hitting 80% on Session doesn’t suppress an 80% notification on Weekly
  • The Dashboard’s quota bars and these notifications share the same source — if the Dashboard shows 82%, a notification would fire if you crossed 80% since the last check
  • In-app toast confirmation: after clicking “Test notification”, the in-app toast always fires regardless of whether the system notification appears. This tells you the click registered.

Edge cases & errors

  • “Test notification” succeeds in-app but I don’t see a notification. Most likely your OS is suppressing it:
    • Do Not Disturb / Focus mode is on — open the Notification Center and look for a queued one
    • Notifications permission denied — macOS: System Settings → Notifications → CLACOROO → Allow Notifications. Windows: Settings → System → Notifications → CLACOROO. Linux: depends on your desktop environment.
    • Banner style is Brief on macOS — the notification flashes and goes to Notification Center; it’s there, you just blinked
  • I’m getting too many notifications. Lower thresholds (disable 80%) or rely only on 100%. Or use OS Do Not Disturb during focus blocks.
  • I’m getting no notifications even though I crossed a threshold. Check the master toggle and the individual threshold toggles. If both are on, click Test notification — if the test fails, it’s an OS permission issue (see above).
  • Notifications are still showing my old email / old plan. Quotas notifications use the current account info, not cached values; if old info appears, restart the app to clear any stale state.
  • Claude account — same quota source, but always visible in the panel
  • API key — quotas with the API are reported the same way
  • Dashboard — see live percentages without waiting for a notification
  • Stats — the long-form view of how you got to those percentages