Skip to content

Releases

Claude Usage Tray 1.0.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 21:37

Changed

  • Released the current Claude and Codex usage tray as version 1.0.0. Functionality is unchanged
    from 0.9.0.

Claude Usage Tray 0.9.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 17:45

Fixed

  • Status-page group headings no longer appear as disrupted components in the popup.

Claude Usage Tray 0.8.1-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Nov 20:19
c998bcb

Fixed

  • Status-page group headings no longer appear as disrupted components in the popup.
  • API and setup-download tests await asynchronous operations; download progress assertions no longer race background callbacks.

Claude Usage Tray 0.8.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 21:38
4e9e8f7

Everything since 0.7.3, gathered for anyone updating from it. The two beta sections that follow are
the same changes as they reached the beta ring.

Added

  • Codex usage alongside Claude. Signing in to the Codex CLI automatically adds rounded-square
    5-hour and 7-day tray badges and a Codex section in the shared popup, including monthly spend
    control when available. Each provider keeps its own freshness and fetch outcome. Without Codex on
    the machine nothing changes: no extra badges, no empty rows.
  • Independent Codex settings and notifications. A Codex tab controls its badges and notification
    level, with codexDisplayMode and codexNotifications keys for settings-file users.
  • OpenAI status follows Codex. Monitoring starts once Codex data exists unless explicitly
    disabled, and OpenAI outages mark only Codex badges. Claude outages continue to mark Claude.

Fixed

  • Weekly-only Codex limits appear under 7-day. Window durations determine the label and pace
    calculation, so a weekly limit supplied as the primary window does not appear as 5-hour.

Claude Usage Tray 0.7.5-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Oct 10:22

Fixed

  • Weekly-only Codex limits appear under 7-day. Window durations now determine the label and
    pace calculation, so a weekly limit supplied as the primary window no longer appears as 5-hour.

Claude Usage Tray 0.7.4-beta.1

Pre-release

Choose a tag to compare

@github-actions github-actions released this 28 Oct 22:58

Added

  • Codex usage alongside Claude. Signing in to the Codex CLI automatically adds rounded-square
    5-hour and 7-day tray badges and a Codex section in the shared popup, including monthly spend
    control when available. Each provider keeps its own freshness and fetch outcome.
  • Independent Codex settings and notifications. A Codex tab controls its badges and notification
    level, with codexDisplayMode and codexNotifications keys for settings-file users.
  • OpenAI status follows Codex. Monitoring starts once Codex data exists unless explicitly
    disabled, and OpenAI outages mark only Codex badges. Claude outages continue to mark Claude.

Claude Usage Tray 0.7.3

Choose a tag to compare

@github-actions github-actions released this 11 Sep 16:18

Everything below since 0.7.2, gathered for anyone updating from it. The four 0.7.3-beta sections
that follow are the same changes as they reached the beta ring.

Added

  • Usage for Claude Desktop users. The tray reads the Claude Desktop app's own usage history when
    Claude Code's data is missing or stale, so a machine that only uses the desktop app shows its
    5-hour and 7-day percentages instead of a permanent —. The 5-hour reset is inferred from that
    history, so pace colours, the elapsed marker and resets in … work there too; inferred times are
    marked with a tilde and never raise a notification. State your weekly reset under Settings →
    General → Claude Desktop
    (e.g. Thu 03:00) and the 7-day window paces against it.

  • Desktop notifications. A Windows toast when a usage limit turns red — whichever rule coloured
    it — and one each way when a watched status page goes down or recovers, in the page's own words.
    Exactly one toast per red period, none at launch into an already-red state, and none for a settings
    edit. Toasts land in Action Center and follow Focus Assist; clicking one opens the popup. All of it
    is on by default and switchable under Settings → Status → Notifications.

  • OpenAI status as an optional second source. For anyone running Codex next to Claude Code, the
    popup can show status.openai.com's banner under Claude's, in the page's own words. Off by default;
    tick Watch OpenAI status. An OpenAI disruption appears in the popup and the tooltip but never
    marks the tray icon — the badge still means "Claude is degraded, which is why your numbers may
    have stopped moving." Each page is polled on its own schedule, so one timing out cannot delay or
    blank the other.

  • Watched components, for both pages. A comma-separated filter per source decides which of a
    page's components you care about (OpenAI lists 25, most irrelevant to a Codex user). A disruption
    affecting only unwatched components shows greyed and marked outside your watched components, and
    no longer marks the tray icon; one the page cannot attribute to any component is always shown in
    full. An empty filter — the Claude default — watches everything, so nothing changes unless you
    narrow the list yourself.

  • A tabbed Settings dialog. The sections are grouped into General, Appearance, Status
    and About, so the window is as tall as its largest group rather than the sum of all of them.
    Nothing moved out of the dialog and nothing changed what it does.

  • Clickable page lists. Under each components filter, every name the page currently reports is a
    link that adds itself to the box — no more retyping a component name to exclude the rest.

  • New settings keys: desktopStalenessHours (default 3, an hours-scale cutoff because the desktop
    app records usage only while you work in it), weeklyResetAnchor, usageNotifications, and
    statusSources with enabled, components and notify per page. File-only:
    desktopHistoryPathOverride. An existing settings file keeps today's behaviour and gains the new
    keys on its next save.

Changed

  • When there is no usage data at all, the popup and tooltip say what is missing — .claude.json
    absent, present without a usage block, no credentials file for the live fetch, or an empty desktop
    history — instead of always suggesting you run Claude Code.

  • Popup incident and component rows, the status headers and the tooltip's status suffix are built by
    the same rules for both pages. When the tooltip runs long, the usage text is what gets shortened,
    so the · Claude: … suffix that explains a warning badge always survives.

  • The installed size grows by about 24 MB (the Windows SDK projection that toasts need). Velopack
    deltas mean you download it once. The supported Windows floor is now Windows 10 2004 (build 19041).

Fixed

  • A window with no known reset says no reset time on a desktop snapshot, instead of leaving a
    silent blank where the reset would be.

Claude Usage Tray 0.7.3-beta.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 10 Sep 17:05

Added

  • Claude Desktop history: the 5-hour reset is now inferred from the sample series, so pace colours,
    the elapsed marker and resets in … work on a desktop-only machine. Estimates are marked with a
    tilde and never raise a notification.
  • weeklyResetAnchor setting and a Claude Desktop settings group: state your weekly reset
    (e.g. Thu 03:00) and the 7-day window paces against it.

Fixed

  • A window with no known reset now says no reset time on a desktop snapshot, instead of leaving a
    silent blank where the reset would be.

Claude Usage Tray 0.7.3-beta.3

Pre-release

Choose a tag to compare

@github-actions github-actions released this 06 Sep 05:35

Added

  • Desktop notifications. A Windows toast when a usage limit turns red — whichever rule coloured
    it — and one each way when a watched status page goes down or recovers, in the page's own words.
    Exactly one toast per red period, none at launch into an already-red state, none for a settings
    edit, and a recovery toast that never claims a page is healthy while it still reports a disruption
    outside your watched components. Toasts land in Action Center and follow Focus Assist; clicking one
    opens the popup. New Notifications group in Settings, plus usageNotifications and a per-source
    notify key in settings.json, all on by default.

Changed

  • The installed size grows by about 24 MB (the Windows SDK projection that toasts need). Velopack
    deltas mean you download it once. The supported Windows floor is now Windows 10 2004 (build 19041).

Claude Usage Tray 0.7.3-beta.2

Pre-release

Choose a tag to compare

@github-actions github-actions released this 05 Sep 16:55

Added

  • OpenAI status as an optional second source. For anyone running Codex next to Claude Code, the
    popup can now show status.openai.com's banner under Claude's, in the page's own words. It is off
    by default; tick Watch OpenAI status in Settings to turn it on. An OpenAI disruption appears in
    the popup and the tooltip but never marks the tray icon — the badge still means "Claude is
    degraded, which is why your numbers may have stopped moving." Each page is polled on its own
    schedule, so one page timing out cannot delay or blank the other.
  • Watched components. OpenAI's page lists 25 components, most of them irrelevant to a Codex user,
    so the new setting comes with a comma-separated component filter (default codex, responses, login, vs code extension, matched as case-insensitive substrings). A disruption that only affects
    unwatched components shows a grey banner marked outside your watched components and adds nothing
    to the tooltip; one the page cannot attribute to any component is always shown in full. The
    filter never hides the badge.
  • statusSources in settings.json, one entry per page with enabled and components. The
    claude entry accepts a filter too, as an advanced file-only setting that narrows the popup rows
    and the tooltip but not the badge. An existing settings file keeps today's behaviour and gains
    the key on its next save.

Changed

  • Popup incident and component rows, the status headers, and the tooltip's status suffix are now
    built by the same rules for both pages. When the tooltip runs long, the usage text is what gets
    shortened, so the · Claude: … suffix that explains a warning badge always survives.