We all want Mac laptops that can run for days on a single charge and never need their batteries serviced. Sadly, we’re always going to be disappointed. Battery and power management technologies continually improve, but those improvements are matched by more powerful processors and smaller designs with less room for battery cells. And, because physics is a harsh mistress, current lithium-ion batteries are always going to age chemically, so they hold less of a charge over time.
In the just-released macOS 10.15.5 Catalina, Apple has introduced a new battery health management feature that promises to increase the effective lifespan of the batteries in recent Mac laptops. It does this by monitoring the battery’s temperature and charging patterns and, in all likelihood, reducing the maximum level to which it will charge the battery.
You see the problem. While battery health management can extend your battery’s overall lifespan, it will likely also reduce your everyday runtime before you need to charge. It’s too soon to know the full extent of this tradeoff, and we suspect that it may be impossible to determine, given that everyone uses their Macs differently.
It’s worth noting that this battery health management feature appears only for those running macOS 10.15.5 or later, and only then if the Mac in question is a laptop with Thunderbolt 3 ports. In essence, then, it’s available only on MacBook Pro models introduced in 2016 or later, and MacBook Air models introduced in 2018 and later. (The Thunderbolt 3 port requirement is merely a shorthand way for Apple to indicate “recent Mac laptops.”)
So, if you have a supported laptop and you’re running macOS 10.15.5, what should you do? We see three scenarios:
- Favor lifespan: If you seldom run your laptop’s battery down to the electronic fumes because it’s easy for you to plug in whenever you need to charge, leave battery health management enabled. That will preserve the battery’s overall lifespan to the extent possible.
- Favor runtime: For those who need to eke every last bit of power from their batteries, disable battery health management. You might have to replace the battery sooner, but you’ll get more runtime in everyday usage.
- Switch as needed: Many people need the longest possible runtime only occasionally, such as on long flights with no under-seat power. In such situations, switch battery health management off for the flight and back on when you return to normal usage patterns.
Switching is easy, but Apple buries it deeply enough that it’s clear that the company doesn’t think most users should be disabling it regularly. Open System Preferences > Energy Saver, click the Battery Health button at the bottom, and in the dialog that appears, uncheck Battery Health Management and click OK. You’ll be prompted to make sure you know what you’re doing; click Turn Off to finish the job.
One final note. The reduced maximum capacity with battery health management enabled may have an undesirable side effect—a recommendation from the Battery Status menu’s health indicator that you need to replace your battery. To check your battery’s health, hold the Option key down and click the Battery Status icon on the menu bar. At the top of the menu, next to Condition, you’ll see either Normal or Service Recommended. (In previous versions of macOS, it could have said Replace Soon, Replace Now, or Service Battery.)
Regardless of the term, anything but Normal indicates that your battery is holding less of a charge than when it was new. If you see that message and you aren’t getting enough runtime for your needs, get the battery evaluated at an Apple-authorized service provider or Apple Store.
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.04 · Low AI Influence
Summary
Apple has introduced a new battery health management feature in macOS 10.15.5 Catalina, which promises to increase the effective lifespan of recent Mac laptops' batteries by monitoring temperature and charging patterns. However, this may reduce everyday runtime before needing to charge.
Related Posts
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.
Introducing ABM Warranty for macOS
If you manage Apple devices at scale, you already know that **Apple Business Manager (ABM)** provides warranty data — but in practice, it’s extremely limited. It doesn’t provide workflow-friendly insights, it doesn’t surface actionable coverage states, and it doesn’t help you wrangle the ever-growing complexity of **AppleCare+ renewals** across hundreds or thousands of devices. This lack of comprehensive information can lead to missed renewal deadlines, unnecessary costs, and a higher risk of device downtime due to expired warranties.
