DevThrottle v2.32.0

v2.32.0 - October 27, 2026

A machine left on a full account now tells you at once, the login you replace by hand is kept as a spare, and sessions stopped on a usage limit carry on by themselves after a switch. Factory pages lead with why each factory exists and what it needs from you, and there is one factory email a day.

Highlights

• A machine stuck on a full account is loud: when an account reaches its limit and a machine on it has no sign-in for any account with room, you get one email, one push notification and one banner line naming the machine, the account it is stuck on and the account it needs. Nothing more is sent while it stays stuck, and the alarm closes by itself when the machine moves off the account or the account resets. It stays quiet while DevThrottle is already signing the machine in for you, and speaks up if that sign-in gets no answer.
• An early warning at 80%: when the account in use passes 80% of either its five-hour or its weekly limit, and a machine on it could not switch to an account with room, you are warned before it runs out. One machine gets one alert: the warning gives way to the stuck-machine alarm if the account then fills up.
• A login you replace is kept as a spare: cc-devthrottle license sign-in <email> --make-active signs in a new account and keeps the one it replaces as a spare, instead of overwriting it. A /login typed inside a Claude Code session is covered too: the Director keeps a copy of the active sign-in and moves it to a spare when another account takes its place. If the replaced login cannot be kept, the sign-in is refused with the reason and nothing is changed.
• Sessions stopped on a usage limit carry on: after a switch to an account that has been checked and has room, the Director sends one "continue" to each Claude Code session whose last turn ended on a usage-limit reply. Each limit reply is answered once, and a session you have typed into since is left alone.
• The approver check works, and says why when it does not: the Director's checks that an approver account can approve sign-ins failed every time since 19 October. They now run, leave any browser profile another session is driving untouched, and a failed check shows its reason on the machine's readiness line on the Licenses page. An account a machine needs that no approver can approve now raises one alarm with the one thing to do.
• A factory page answers your questions in order: the Overview opens with the Boss's why, goal and limits, then open problems and failures, "What we are doing now" (the newest document the Boss wrote), "Needs you" (which says "Nothing today." when nothing waits), and every seat with when it runs and how its last run ended. The drawing moves to the Floor tab, linked from the end of the Overview. Each factory's page also shows why it exists under its name, and a goal number nobody has posted says "Not measured", never 0.
• One factory email a day, at 08:00: it lists everything the factories are waiting on you for, each linked to its item, and one line for every factory saying what it did in the last 24 hours. The 16:00 and midnight emails are gone; a new problem shows first in the next morning's email.
• Scheduled factory runs never stop on a permission question: a session a schedule or trigger starts in a factory loads no ask or deny rules, while keeping the folder's instructions, skills, servers, hooks, environment and output style.

Also in this release

• A later run can read your answers to a dev report: cc-dev-reports answers shows each question with the option you chose, your comment and the time, and whether a run has acted on it. Answers to a report whose session has ended are now saved instead of refused.
• The recording bars in the Cockpit and the phone app now move like the Director's: a real nine-band display calibrated to normal speech, so a working microphone no longer looks dead. Every microphone meter, including Test microphone, Test transcription and the phone recorder, reads on the same scale. The dictation dialog's Pause button now has a name a screen reader can say.
• The hosted service is deployed more safely: a new version must start and answer health checks before it goes live, a deploy refuses to run onto a site that is already down, and a version that never comes up is rolled back to the last good one automatically.
• A boss.md heading is recognised with or without "The", in any case, so "## Why" and "## Goal" no longer show "not set yet".
• Test fixes: the Mac setup tests no longer touch the machine's own installed launcher, and the license tests no longer depend on the day they run.