@tryarcanist/cli 0.1.420 → 0.1.421
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 +8 -4
- package/dist/index.js +67 -59
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,19 +2,23 @@
|
|
|
2
2
|
|
|
3
3
|
Command-line interface for [Arcanist](https://www.tryarcanist.com): follow session output and manage environments from your terminal or automation.
|
|
4
4
|
|
|
5
|
-
##
|
|
5
|
+
## Set up
|
|
6
6
|
|
|
7
7
|
```bash
|
|
8
|
-
|
|
8
|
+
npx --yes @tryarcanist/cli@latest setup
|
|
9
9
|
```
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Run this from your repository with Node.js 22 or newer. It installs the CLI globally, verifies the installed command, and starts sign-in and repository setup. Approve access when asked and follow the returned command. After setup, use `arcanist review` to review your committed changes.
|
|
12
|
+
|
|
13
|
+
Setup uses npm's configured global prefix and installs the same version that `npx` ran. An existing installation of that version is reused. If installation fails or the global bin directory is missing from `PATH`, setup stops with recovery instructions before starting onboarding. It does not change your shell profile or request elevated privileges.
|
|
14
|
+
|
|
15
|
+
To install without onboarding, use `npm install -g @tryarcanist/cli`. Existing installations can continue with `arcanist onboard`.
|
|
12
16
|
|
|
13
17
|
## Onboard through your coding agent
|
|
14
18
|
|
|
15
19
|
Give your agent this prompt from a repository checkout:
|
|
16
20
|
|
|
17
|
-
>
|
|
21
|
+
> Run `npx --yes @tryarcanist/cli@latest setup --json` from this repository. It installs the CLI and starts onboarding. Follow its next actions until this repository is ready and its first pull request review is verified. Open approval links for me when needed; run the terminal commands yourself. Keep me updated when something changes. Use `arcanist help onboard --json` for the full flow.
|
|
18
22
|
|
|
19
23
|
No Arcanist account or manually copied token is needed beforehand. New users approve sign-in in the browser by typing the code the CLI shows; repository owners approve GitHub App installation when it is missing. Existing write-scoped CLI logins are reused. A browser-approved replacement supersedes a rejected or read-only project token for the same API; the project file stays unchanged. Explicit token overrides remain authoritative and must be replaced or unset if invalid. The agent checks the same command while approval is pending and continues automatically after approval. Approval links carry a challenge, never the CLI token; the verifier and approved token stay in private files under `~/.arcanist`.
|
|
20
24
|
|