@usepowerplant/cli 0.4.27 → 0.4.29
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 +5 -5
- package/dist/main.js +6641 -4600
- package/dist/menubar/Powerplant.app.zip +0 -0
- package/package.json +5 -4
package/README.md
CHANGED
|
@@ -31,9 +31,9 @@ By default, only sessions in repos your org's sync policy allows (the repos it c
|
|
|
31
31
|
|
|
32
32
|
## Error reporting
|
|
33
33
|
|
|
34
|
-
When the CLI itself hits a bug — a crash or an unexpected error — it sends an error report to [Sentry](https://sentry.io) so we can fix the problem without asking you to dig through logs. This is on by default, and there is no setting to turn it off for free users. Paid users can arrange an opt-out through [support](mailto:support@
|
|
34
|
+
When the CLI itself hits a bug — a crash or an unexpected error — it sends an error report to [Sentry](https://sentry.io) so we can fix the problem without asking you to dig through logs. This is on by default, and there is no setting to turn it off for free users. Paid users can arrange an opt-out through [support](mailto:support@usepowerplant.com). A report contains the error and its stack trace, the CLI version and environment, which enrolled machine and org the background service belongs to, and diagnostic details such as ids and counts. It never contains session transcripts, code, or file contents, and secret-shaped values (tokens, keys, passwords) are removed on your machine before the report is sent. Errors whose fix is printed on screen (like "run `powerplant enroll` first") are not reported at all.
|
|
35
35
|
|
|
36
|
-
If sending error reports is a problem for your machine or org, email [support@
|
|
36
|
+
If sending error reports is a problem for your machine or org, email [support@usepowerplant.com](mailto:support@usepowerplant.com) and we'll work something out.
|
|
37
37
|
|
|
38
38
|
## Day to day
|
|
39
39
|
|
|
@@ -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 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.
|
|
87
|
+
`uninstall` removes the background service and the hooks it added to your coding agents. On a Mac where `init` installed Powerplant's own copy, it also removes that copy, its `~/.local/bin/powerplant` link, and the menu bar app, but never edits your shell startup files. 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
|
|
|
@@ -92,10 +92,10 @@ powerplant uninstall --forget # also delete this machine's stored credentials
|
|
|
92
92
|
- **`status` says the service is installed but not loaded, or a daemon is stalled** — run `powerplant restart`.
|
|
93
93
|
- **An agent's sign-in was cancelled or expired** — run `powerplant connect`; it skips agents that are already signed in and only finishes what's missing.
|
|
94
94
|
- **A deprecation warning prints on every command under Node 20** — it comes from a dependency and is harmless; Node 22 or newer doesn't print it.
|
|
95
|
-
- **None of that fixed it** — run `powerplant doctor` and paste its output into an email to [support@
|
|
95
|
+
- **None of that fixed it** — run `powerplant doctor` and paste its output into an email to [support@usepowerplant.com](mailto:support@usepowerplant.com). It prints a diagnostics summary (status plus the tail of the sync service's log with credentials redacted) and uploads nothing — you choose what to share.
|
|
96
96
|
|
|
97
97
|
The CLI is Powerplant's connector and installer only; agents read Powerplant through its MCP server, never through this command.
|
|
98
98
|
|
|
99
99
|
## About this package
|
|
100
100
|
|
|
101
|
-
Powerplant's source code is private today, so this package carries no repository link — it ships the compiled CLI only. Questions or problems: [support@
|
|
101
|
+
Powerplant's source code is private today, so this package carries no repository link — it ships the compiled CLI only. Questions or problems: [support@usepowerplant.com](mailto:support@usepowerplant.com).
|