BatteryControl 1.3.4
Development on BatteryControl has stopped. This release is the same source code as 1.3.3 —
the version bump and the status notice in the README are the only changes — and it's the
last planned release. The repo stays up and the project isn't going anywhere.
Why
BatteryControl was written because macOS had no way to hold a charge below 80%. macOS 26
now ships Apple's own Charge Limit (System Settings → Battery, 80–100%), and on the
author's Mac that covers what this app was for. The app has been uninstalled, and there's
no active development on it anymore. If someone needs support on it, that's the kind of
thing that could bring development back — but don't plan on it.
What 1.3.4 contains
- The status notice in the README, plus maintenance notes in SECURITY.md and
CONTRIBUTING.md. No code changes. - The version bump itself, so the last planned release is a real, labeled artifact.
An honest note about this build
The binaries were recompiled with Xcode 26.3 on macOS 26, and the full test suite passes
(308/308) with clean Debug and Release builds. But the app is no longer installed on the
author's machine, so nothing in this release was re-validated against real battery
hardware. What was physically tested is exactly what the README's compatibility section
has always said: one M3 MacBook Air (Mac15,13) on macOS 15.8, with write/readback
evidence recorded. Everything else remains capability-tested with per-write verification.
What still holds
- Security reports still go through
private vulnerability reporting
and will be read. With no planned releases, a fix can't be promised — but a serious
report is also the most likely thing to bring the project back for one more fix. - Issues and pull requests may sit unanswered.
- Forks are welcome (MIT). If you take it further, keep the rules in CONTRIBUTING.md:
runtime capability detection, readback verification on every write, and honest state
reporting. They're what keep an SMC-writing tool from lying to you.
If you're using it
- On macOS 26.4+, Apple's built-in Charge Limit is the supported way to cap at 80–100%.
- Below 80%, this release still works as documented on hardware with a recognized
firmware signature — with the same caveats the compatibility section has always stated.
Read it before trusting any build with your battery.
Downloads
| File | Contents |
|---|---|
BatteryControl-1.3.4.pkg |
App + CLI + embedded daemon |
BatteryControlCLI-1.3.4.pkg |
Just the CLI, no daemon |
BatteryControl-1.3.4.zip |
The app + CLI as a zip |
SHA256SUMS |
Hashes of all three (shasum -a 256 -c SHA256SUMS) |
The installers are unsigned and not notarized; Gatekeeper may ask you to approve the app
on first launch. Only download from the
releases page of this repository —
check SHA256SUMS if you want certainty about what you got.