0.2.195.2 MB
Apache-2.0
strict
core26
Battery charge threshold manager for laptops
Charge Stop manages your laptop's battery charge threshold — the percentage
above which charging stops. Keeping it below 100% extends battery lifespan
for laptops that spend most of their time plugged in.
## Quick start (CLI)
The command-line tool is the primary way to use Charge Stop:
$ charge-stop # show the current threshold
$ charge-stop 65 # stop charging at 65%
$ charge-stop history day # render battery activity as a chart
Run
Plug-in, unplug, and charge cycles are rendered as color-coded terminal
charts for the current day (default), week (
(
$ charge-stop history
## How it works
A root daemon (
and persists the setting so it survives reboots and suspend. Firmware on
many laptops resets the threshold across these events, but the daemon
re-applies the persisted value automatically (including after resume).
The CLI talks to the daemon over a UNIX domain socket using a small REST API:
## Snap interfaces (strict confinement)
The daemon uses the
attributes. Connect it manually before use:
$ sudo snap connect charge-stop:power-control
above which charging stops. Keeping it below 100% extends battery lifespan
for laptops that spend most of their time plugged in.
## Quick start (CLI)
The command-line tool is the primary way to use Charge Stop:
$ charge-stop # show the current threshold
$ charge-stop 65 # stop charging at 65%
$ charge-stop history day # render battery activity as a chart
Run
charge-stop history to see how your laptop has been used over time.Plug-in, unplug, and charge cycles are rendered as color-coded terminal
charts for the current day (default), week (
history week), or month(
history month). Try it:$ charge-stop history
## How it works
A root daemon (
charge-stopd) manages the sysfs battery attribute directlyand persists the setting so it survives reboots and suspend. Firmware on
many laptops resets the threshold across these events, but the daemon
re-applies the persisted value automatically (including after resume).
The CLI talks to the daemon over a UNIX domain socket using a small REST API:
- GET /v1/threshold report the current threshold
- POST /v1/threshold set and persist the threshold
- POST /v1/restore re-apply the persisted threshold
- GET /v1/events retrieve battery event history
## Snap interfaces (strict confinement)
The daemon uses the
power-control interface to manage sysfs batteryattributes. Connect it manually before use:
$ sudo snap connect charge-stop:power-control
Update History
0.2.0 (7) → 0.2.1 (9)25 Aug 2026, 16:00 UTC
0.1.0 (4) → 0.2.0 (7)25 Aug 2026, 09:45 UTC
0+git1.874d76e (1) → 0.1.0 (4)14 Aug 2026, 09:00 UTC
0+git1.874d76e (1)14 Aug 2026, 08:45 UTC
14 Aug 2026, 08:19 UTC
25 Aug 2026, 15:37 UTC
14 Aug 2026, 08:45 UTC