HaloBattery

Battery levels in the Windows tray - from mice, keyboards, headsets and controllers to health trackers and smart home devices.

Runs with mockssource: GitHubPythonMITcommit 73e229cbee2e

Python, MIT licensed. The project labels itself: 2 4ghz, battery monitor, bluetooth, charging, health trackers, peripherals, smart home and system tray.

HaloBattery runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 1961 tests pass on Linux with Python 3.12.3, 22 Windows-only tests correctly skipped. The app loads and runs its --probe smoke scan cleanly. The only fixes needed were creating a .py copy of the .pyw entry point for Linux's import machinery and updating the test sandbox to allow Unix domain socket connections (used by X11 for pystray integration).

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
1
last tested
stars
767
forks
90
open issues
113
watchers
0
size
23 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing HaloBattery, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • _sandbox.install_guards() replaced socket.socket.connect to block ALL connections including local Unix domain sockets used by X11, causing pystray's Xorg backend import to fail5 minutes
  • Python import system on Linux does not recognize .pyw as a source suffix, so spec_from_file_location() returned None for halo_battery.pyw in 6 test files, cascading into ~34 import errors3 minutes
  • 3 test_startup_imports subprocess tests failed because the child process also hit the X11 sandbox guard via pystray import1 minute
Install time
18 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
python -m unittest discover -s tests exited 0, 1961 passed, 22 skipped (all Windows-only); python halo_battery.py --probe exited 0 with 'Nothing found' (expected, no HID devices in container)
Model tokens used
89,597
Exact commit tested
73e229cbee2e
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Errors encountered & fixed:**
1. **`.pyw` not recognized on Linux** — Python's import machinery only recognizes `.py` in `SOURCE_…
2. **X11 socket blocked by sandbox** — `_sandbox.install_guards()` indiscriminately blocked ALL `so…
3. **Subprocess test failures** — Same X11/sandbox conflict affected the 3 `test_startup_imports.py…
2026-11-16T07:35:05.994544Z ERROR codex_core::session: failed to record rollout items: thread 01a1e…
tokens used
89,597
Everything is verified and passing. Here's the final result:
**Errors encountered & fixed:**
1. **`.pyw` not recognized on Linux** — Python's import machinery only recognizes `.py` in `SOURCE_…
2. **X11 socket blocked by sandbox** — `_sandbox.install_guards()` indiscriminately blocked ALL `so…
3. **Subprocess test failures** — Same X11/sandbox conflict affected the 3 `test_startup_imports.py…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 18 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.08

Topics (from GitHub)

2-4ghzbattery-monitorbluetoothcharginghealth-trackersperipheralssmart-homesystem-traywindowswireless

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/HaloBattery.svg)](https://argusic.com/subject/halobattery)

Questions

Does HaloBattery run?
HaloBattery runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test HaloBattery?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 73e229cbee2e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test HaloBattery?
The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does HaloBattery take to install?
18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does HaloBattery need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing HaloBattery?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for HaloBattery?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion