@usepowerplant/cli 0.4.7 → 0.4.9

package/README.md

@@ -17,13 +17,17 @@ powerplant init
 re-run at any time — finished steps are skipped with a note:
 
 1. **Enroll this machine.** Your browser opens so you can approve the
-   machine into your org. The machine's credential is stored in the macOS
-   keychain; on other platforms, in a file only your user can read.
+   machine into your org. On macOS, the credential is encrypted in a local
+   file with its key in Keychain; other platforms use a file only your user
+   can read. See [credential storage and reset](../../README.md#quick-staging-reset).
 2. **Install the background service.** The sync service watches your local
    coding-agent sessions (Claude Code, Codex, and Cursor) and uploads the
    ones in scope. If recent sessions name repositories under a macOS-protected
-   location such as Documents, init lists the location and asks before reading
-   Git metadata there; declining leaves those sessions local. The service
+   location such as Documents, init lists the location and asks once before
+   reading Git metadata there; declining leaves those sessions local, and a
+   yes covers locations that appear later (init still explains before macOS
+   asks). A location macOS refused is re-checked on every init until you
+   enable it in System Settings. The service
    starts on login and keeps itself running. On macOS, init also installs
    the Powerplant menu bar app from this package into `~/Applications` and
    launches it; the app registers itself to start at login (turn that off
@@ -86,7 +90,7 @@ powerplant status     # what the sync service is doing (add --json for tools)
 powerplant doctor     # a diagnostics summary to paste into a support email
 powerplant pause      # stop background uploads without uninstalling
 powerplant resume     # start again — a catch-up pass covers the pause
-powerplant restart    # restart the background service
+powerplant restart    # restart background sync using this CLI installation
 powerplant connect    # connect agents installed after setup, or re-sign-in
 powerplant disconnect # remove the Powerplant MCP (and its sign-in) from your agents
 powerplant sync       # run one upload pass now, in the foreground
@@ -131,9 +135,11 @@ then restarts itself onto it. The choice is per machine and only an
 explicit yes counts: a machine set up before the question existed stays
 off until someone turns it on. `powerplant status` and `powerplant doctor`
 report the current choice, and `powerplant update --automatic on` or
-`--automatic off`, or the menu bar's More menu, change it. A release that
-fails to install is not retried by itself; the menu bar shows the failure
-with a retry and the update log, and the next release clears it.
+`--automatic off`, or the menu bar's More menu, change it. Turning it on
+(there, or at init's question) makes the sync check within seconds, so a
+release already out installs now rather than at the next hourly check. A
+release that fails to install is not retried by itself; the menu bar shows
+the failure with a retry and the update log, and the next release clears it.
 
 Powerplant also publishes the oldest version it still supports. When yours
 is older, `powerplant status`, `powerplant doctor`, the menu bar app, and