You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built application will be located at `build/ChargeControl.app`.
82
+
3. Move `build/ChargeControl.app` to `/Applications`.
63
83
64
-
### 2. Install to Applications
84
+
---
65
85
66
-
For the background daemon to work reliably with macOS security policies (`SMAppService`), it is recommended to move the app to your `/Applications` folder:
86
+
## 🛡️ Security & Permissions
67
87
68
-
```bash
69
-
cp -R build/ChargeControl.app /Applications/
70
-
```
88
+
Because ChargeControl is currently distributed independently and interacts with low-level system hardware (SMC), you will likely encounter macOS security warnings.
89
+
90
+
### 1. "Unidentified Developer" Warning
91
+
When you first try to open the app, macOS may block it because it isn't signed with an Apple Developer Certificate.
92
+
-**The Fix:** Don't just double-click it. **Right-click (or Control-click)** the app icon and select **Open**. This will present a dialog with an "Open" button that isn't usually there, allowing you to bypass the check.
93
+
94
+
### 2. Administrator Password
95
+
Once opened, the app needs to install a background helper daemon (`ChargeControlDaemon`) to talk to your battery hardware.
96
+
-**The Fix:** You will be prompted for your **Administrator Password**. This is required for the app to enforce your battery limits while your Mac is asleep or on the lock screen.
71
97
72
-
### 3. Install the CLI (Optional)
98
+
### 3. Background Items
99
+
You may see a system notification that "ChargeControl" has added a background item. This is normal and necessary for the daemon to stay active.
100
+
101
+
---
102
+
103
+
## ⌨️ Installing the CLI (Optional)
104
+
105
+
The `cc` command-line tool allows you to control the app from the terminal.
106
+
- If you installed via **Homebrew** or the **One-Liner**, the CLI is already installed!
107
+
- If you installed via the **DMG** or built from source, you can symlink it manually:
73
108
74
-
To use the CLI from anywhere, symlink the binary to your path:
0 commit comments