UsageForge 3.8.9

• At set times now sends at each time you set, even while a window is open. That message costs next to nothing and just doesn't start a new window, so a late window never pushes the rest of your day back.
• A set time goes out within 15 minutes of it or not at all (Mac asleep, offline). A failed one is tried again at each check inside those 15 minutes.
• Replaces the 3.8.8 rule; nothing waits for an open window to end any more.

UsageForge 3.8.8

• A set time held back by a window that is already open (for example one you started yourself) now goes out when that window ends only if its own window would finish by your next set time (15 minutes grace). Otherwise it is skipped and the next set time goes out on time. Before, with times 5 hours apart (6, 11, 16, 21), one late window pushed every later time back.
• The next time shown in the panel and menu bar, and the wake times, follow the same rule.

UsageForge 3.8.7

• Hovering an empty hour on the day bar now shows the 5-hour window a click would add: its start and end time, or which window it would overlap.
• The ruler under the bar marks every hour, with a chip on the hour you point at.
• The day bar no longer flickers when the panel refreshes under the pointer.

UsageForge 3.8.6

Fix: a /usage reply without numbers (Anthropic answered 429) no longer stops UsageForge from using Claude Code's saved numbers. Correction to 3.8.4: Claude Code didn't drop its usage report; it leaves it out when the usage endpoint answers 429.

UsageForge 3.8.5

• Claude usage: UsageForge reads the numbers Claude Code saves each time it checks, and asks Claude Code's /usage again at most every 15 minutes (1 minute for the menu bar's Refresh). Asking every 5 minutes made Anthropic's usage endpoint answer 429 (too many requests), which left the numbers stale.
• When Claude's numbers are more than 20 minutes old, the panel and menu bar say how old.

UsageForge 3.8.4

• Claude Code 2.1.299 prints /usage as text only, which left the Claude meters blank. UsageForge now reads that text.
• The background check also runs whenever the Mac wakes or sleeps. With the lid closed, a scheduled wake lasts only seconds, and the 5-minute timer often missed it (the 6:00 PM message waited until the lid opened).
• The wake hold now starts only after a wake UsageForge scheduled.

UsageForge 3.8.3

• A set time held back by an open window now goes out only if that window ends within the set time's own 5 hours. Otherwise it is skipped, so a late window no longer pushes the rest of your day off your set times.
• Codex messages run with --ephemeral where supported, so they leave no session file that looked like an agent at work and kept the Mac awake 10 minutes after a scheduled wake.

UsageForge 3.8.2

Fix: releasing the hold that keeps the Mac awake during a check no longer writes a 'Terminated' line to the log.

UsageForge 3.8.1

After a wake UsageForge scheduled, the Mac goes back to sleep once the messages are out and the 5-hour usage has been re-read, even with the lid open, unless someone has used the Mac since the wake or an agent is working.

UsageForge 3.8.0

Sleep when work is done no longer has hours. Switch it on as you leave: the Mac stays awake while Claude Code or Codex works, sleeps once they've finished and nobody has used it for 10 minutes, then the switch turns itself off. CLI: usageforge sleep on | off.