Claude Code Tray (unofficial): baixar versions anteriors

## What's new in v1.8.0

One new notification, plus a window that fits smaller screens.

### 🔴 A warning before a limit runs out

The icon has always turned red when your pace would use up a window before it resets. That only helps if you happen to look at the tray. Now a **red toast says it once**, titled *On pace to run out*. It tells you how long until the window runs out at this pace and when it resets.

• **Once per window, per reset.** The 5-hour session and the weekly window each get at most one warning per cycle. It does not repeat every poll, and restarting the tray mid-cycle does not send it again.
• **The same verdict as the icon.** The toast and the red bar use the same pace line, so you never get a toast without the red icon, or a red icon without the toast.
• **Quiet when it would be noise.** No warning in the first tenth of a window, when a pace has nothing behind it yet. No warning for a window that has already hit its limit either, because the icon already says it is blocked.
• **On by default**, under **Settings → Notifications → On pace to run out**. Unlike the reset toasts, this one is plain red, with no confetti.

### 🖥️ Fits smaller screens

• **The window fits screens shorter than 960 pixels**, down to 720p. On a short screen it now opens sized and centred to the work area instead of running off the bottom of the screen.
• **The Statistics charts size to the window.** The pace and throughput charts grow with a tall window and shrink with a short one, down to a minimum height. Below that the page scrolls, so the axis labels are never clipped.

### 🔬 Under the hood

Nothing here changes what the app does. It changes what can ship broken.

• **The UI checks drive the real window.** The 3,004-line interaction harness is gone. Every claim it made is now a case run by [winwright](https://github.com/alegauss/winwright)：keyboard input under the tray's own message loop, the right-click menu, the profile switch, the linking plan, the session rows and what each control announces to a screen reader.
• **Previews are drawn by the app, not copied off the screen**, so nothing on top of the window can end up in a screenshot, and a popup can be photographed at all.
• **The local release script says it did not submit to winget**, and how to submit it, instead of looking like it had.

### 🌐 The site

The site at [alegauss.github.io/claude-tray](https://alegauss.github.io/claude-tray/) now uses the shared alegauss design system, in the same clay colours. Once it is redeployed, Google Analytics loads only if you allow it. The sponsor block uses Viglet's new logos and product names.

**Install or update:** `winget install alegauss.ClaudeCodeTray`, or download `ClaudeTray-Setup.exe` below. Installed copies offer the update from the tray menu.

---

Unofficial community project, not affiliated with, endorsed by, or sponsored by Anthropic.

## What's new in v1.7.2

The biggest release since profiles arrived — **33 commits** — and one theme：**two Claude Code profiles, made one setup.**

### 🔗 One setup across profiles

A fresh profile starts genuinely empty：no user `CLAUDE.md`, no settings, no skills, plugins or project history. That isolation is the point when the two accounts are two jobs. It is in the way when they are one person changing subscription — and the fix by hand is a dozen `mklink` commands in an order where the wrong one loses a folder.

**Settings → Claude Code → One setup across profiles** now picks which profile keeps its files and shows you, folder by folder, what sharing them would mean:

• **merged** — `projects`, `file-history` and the things you wrote yourself (`skills`, `agents`, `commands`, `output-styles`) are unioned first, so neither side loses anything, and each row says how many folders would be copied over. `history.jsonl` is merged line by line, ordered on each line's timestamp.
• **adopted** — `plugins` and your `CLAUDE.md` are taken whole from the profile that keeps its files. A plugin records where it was installed, so merging those entry by entry would leave half of them pointing at a folder that is no longer there.
• **not offered** — `settings.json` *could* be merged, and that is exactly why it isn't：the union would widen the other account's permission allowlist, which is your call. **So it shows you what you are deciding** — how many rules would arrive on each side, which lists they land in, and the first few by name. Rules arriving in `deny` are counted apart, because those take capability *away* and folding them in would make the safe half look like the risky one. Hooks are listed per event with a count each side, because a hook is a command line that runs and no total answers that.
• **never** — `.claude.json` and `.credentials.json`. Your sign-in and the file that makes this a separate account are not part of "one setup", and no button here will touch them.

**And it says what it has no opinion about.** The list above is a list of opinions, so the plan closes by naming everything else sitting at the top level of either folder — not because those are safe to share and not because they are not, but because nothing here has a view. Per-machine caches and snapshots are counted rather than named.

**The button writes a script; nothing else happens.** Claude Code Tray has no way to write into a configuration folder and isn't growing one — so **Write script…** saves a PowerShell file where you point it and opens the folder. Read it, then run it. Even then a bare run only *prints* what it would do：it takes a second run with `-Apply` to change anything, it never asks for administrator rights, and it never deletes — every original is renamed beside its link so you can put it back. If the plan needs a file symlink and Windows has no Developer Mode, it says so **before** it moves anything rather than half-way through.

**One consequence, stated before you decide.** Sharing `projects` is most of the point — and it also means both profiles report the same "last turn", so **Follow the active profile** can no longer tell which of them you are in and stops moving the icon between that pair. The script's header says so, in those two profiles' names, before you run it.

### 🧭 Auto-follow knows when it cannot help

• **It no longer flips between two profiles that share one folder.** A junction can put two config directories behind one `projects` tree, and then the newest write is the same fact twice — evidence about neither of them. Both are taken out of the running, so the icon stays where you put it instead of being pushed back and forth by whichever was scanned second.
• **And the setting says so.** When every profile it could follow reads the same project history as another one, **Follow the active profile**'s own description tells you it can do nothing right now, rather than leaving you a switch that looks on and never moves the icon.