@usepowerplant/cli 0.4.22 → 0.4.24
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -3
- package/dist/cli.js +143 -100545
- package/dist/main.js +103992 -0
- package/dist/menubar/Powerplant.app.zip +0 -0
- package/package.json +4 -3
- package/dist/hooks/powerplant-cloud-capture.mjs +0 -747
- package/dist/hooks/powerplant-codex-transcript.mjs +0 -103
- package/dist/hooks/powerplant-cursor-transcript.mjs +0 -115
- package/dist/hooks/powerplant-session-lifecycle.mjs +0 -99
package/README.md
CHANGED
|
@@ -19,11 +19,11 @@ powerplant init
|
|
|
19
19
|
|
|
20
20
|
`powerplant init` is one setup pass with three steps, and it is safe to re-run at any time — finished steps are skipped with a note:
|
|
21
21
|
|
|
22
|
-
1. **Enroll this machine.** Your browser opens so you can approve the machine into your org. On macOS, the credential is encrypted in a local file with its key in Keychain;
|
|
22
|
+
1. **Enroll this machine.** Your browser opens so you can approve the machine into your org. On macOS and Windows, the credential is encrypted in a local file, with its key in Keychain on macOS and protected by Windows DPAPI on Windows; Linux uses a file only your user can read.
|
|
23
23
|
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 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 from its More menu), and the background service keeps it on the same version as the CLI after every update.
|
|
24
24
|
3. **Add MCP to your agents.** Init lists the agents it found — Claude Code, Codex, and Cursor — as checked boxes. They all start selected; use the arrow keys and Space to turn off any you want to skip, then press Enter (`--yes`, or running without a terminal, adds MCP to everything without asking). Each selected agent is pointed at the Powerplant MCP server and signed in: for Claude Code and Codex the sign-in opens a browser window; for Cursor, the Cursor app opens so you can approve the Powerplant server and sign in there. This is how your agents read the team's sessions, review rooms, and search. If you skip or cancel a sign-in, nothing breaks: finish later with `powerplant connect` (add `--client claude|codex|cursor` for just those — repeatable). Each agent's own sign-in output prints as it runs. Connect supports Claude Code 2.1.186, Codex 0.134.0, and Cursor 3.4 or newer; an older installation is reported with an update hint and, when the machine holds another copy of the same agent, that copy is tried instead.
|
|
25
25
|
|
|
26
|
-
The background service
|
|
26
|
+
The background service runs on macOS (launchd) and Windows (a Task Scheduler task that starts at sign-in and needs no administrator). On other platforms, init still enrolls the machine and adds MCP to your agents, and points you at running `powerplant sync` after coding instead.
|
|
27
27
|
|
|
28
28
|
## What gets uploaded
|
|
29
29
|
|
|
@@ -84,7 +84,7 @@ powerplant uninstall # remove the background service
|
|
|
84
84
|
powerplant uninstall --forget # also delete this machine's stored credentials
|
|
85
85
|
```
|
|
86
86
|
|
|
87
|
-
`uninstall` removes the background service
|
|
87
|
+
`uninstall` removes the background service and the hooks it added to your coding agents. Your coding agents keep their Powerplant MCP connection until you run `powerplant disconnect` (and uninstall reminds you when that's the case). Disconnecting is local to this machine: the access you granted the agents stays on your Powerplant account until you revoke it from your Profile page in the web app.
|
|
88
88
|
|
|
89
89
|
## Troubleshooting
|
|
90
90
|
|