Feature · 統計
Your battery week,summarized like a person would.
Time unplugged, charge sessions, average discharge depth, the hottest stretch, the rescues that landed in time, folded into weekly and monthly recaps you can read in twenty seconds.
Why it matters
The live percentage answers “what now”. It never answers “is this normal for me”. Recaps show the pattern (the travel week, the month a sync client ran wild) while there's still time to change it.
What a recap contains
Every week and month, Sensei folds the raw history into a short recap: how long you ran unplugged, how many charge sessions you started, your average depth of discharge, the hottest stretch, and the closest call you had. It reads like a summary a person would write, not a table.
Why summaries beat live numbers
A live percentage answers “what now”. It can’t answer “is this normal for me”. Recaps make patterns visible: the week you were on the road, the month a sync client quietly ran all day, the stretch where your average discharge depth crept from 40% to 70%, the kind of drift that capacity reflects only months later.
Rescues
When you plug in within thirty minutes of a critical warning, Sensei records a rescue and can stitch a small shareable receipt for it. It’s a light touch, but it turns a near-miss into something you can actually count over a month, and it pairs with warning presets, since the presets decide how much warning you got in the first place.
Frequently asked.
- Where does the data come from?
- Entirely from the local history Battery Sensei records on your own Mac. No account, no sync, no telemetry: the recaps are computed on-device from your own samples.
- How long until the first recap?
- The weekly recap needs a few days of samples to say anything meaningful; the monthly one fills in as the month progresses. Sensei shows what it has rather than an empty shell.
- Can I share a recap?
- Yes. Recaps and rescue receipts render as small cards you can save or send. Nothing is uploaded; you create the image and decide where it goes.