gigabuddy 0.3.0 → 0.3.2

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 CHANGED
@@ -1,66 +1,67 @@
1
1
  # gigabuddy
2
2
 
3
- The Gigabuddy CLI. Sign in, and install `@gigabuddy` packages as yourself.
3
+ Command-line sign-in for the [Gigabuddy](https://gigabuddy.com) platform.
4
+ Authenticates your machine and configures npm to install `@gigabuddy`
5
+ packages from the Gigabuddy registry.
6
+
7
+ ## Install
4
8
 
5
9
  ```bash
6
- npm install -g gigabuddy # or just: npx gigabuddy login
10
+ npm install -g gigabuddy
11
+ # or run without installing:
12
+ npx gigabuddy login
13
+ ```
7
14
 
8
- gigabuddy login
15
+ ## Usage
16
+
17
+ ```bash
18
+ gigabuddy setup # put Gigabuddy into Claude Code
19
+ gigabuddy login # sign in + set npm up for @gigabuddy packages
9
20
  npm install @gigabuddy/app-kit
10
21
  ```
11
22
 
12
- That's the whole onboarding — one command. Signing in also sets `npm` up,
13
- because installing `@gigabuddy` packages is what the credential is for.
23
+ `setup` installs the [Gigabuddy plugin](https://github.com/gigabuddy/claude-plugin)
24
+ into Claude Code for you (it runs Claude Code's own `claude plugin` commands;
25
+ if `claude` isn't on your PATH it prints the `/plugin` commands to run
26
+ yourself). `login` opens your browser to sign in (device flow), stores your
27
+ credential, and configures `~/.npmrc` for the `@gigabuddy` registry.
14
28
 
15
29
  ## Commands
16
30
 
17
- | Command | What it does |
18
- | ----------------------- | ---------------------------------------------------------------- |
19
- | `gigabuddy login` | Sign in (device flow opens your browser) and set up `~/.npmrc` |
20
- | `gigabuddy login --npm` | Re-mint just the npm credential, when it expires |
21
- | `gigabuddy status` | Who you're signed in as |
22
- | `gigabuddy logout` | Sign out (`--npm` clears only the npm credential) |
31
+ | Command | Description |
32
+ | ------------------ | -------------------------------------------------------------- |
33
+ | `setup` | Install the Gigabuddy plugin into Claude Code |
34
+ | `login` | Sign in and configure `~/.npmrc` for the `@gigabuddy` registry |
35
+ | `login --npm` | Refresh only the npm registry credential |
36
+ | `status` | Show the signed-in account |
37
+ | `doctor [package]` | Diagnose sign-in, npm config, and registry access |
38
+ | `logout` | Sign out (`--npm` removes only the npm credential) |
23
39
 
24
- Pass `--no-npm` to sign in without touching `~/.npmrc`.
40
+ **Options:** `--no-npm` signs in without modifying `~/.npmrc`. `--staging`
41
+ targets the staging environment; staging credentials are stored separately.
25
42
 
26
- `--staging` targets the staging environment; its credentials are stored
27
- separately, so a staging login never becomes your production one.
43
+ ## Credentials
28
44
 
29
- ## What lands on disk
45
+ `login` writes a refresh token to `~/.gigabuddy/user-credentials.json` (mode
46
+ 0600). Short-lived platform tokens are minted from it on demand.
30
47
 
31
- `login` stores a **refresh token** in `~/.gigabuddy/user-credentials.json`
32
- (0600). Platform tokens are minted from it on demand and live an hour. The
33
- session behind it is deliberately narrow — it identifies you, lets you see what
34
- you can reach, install from the Gigabuddy registry, and run agents you sponsor;
35
- it is not your full account authority.
36
-
37
- `login` also adds two lines to `~/.npmrc` (0600), leaving everything else in
38
- that file exactly where it was:
48
+ It also adds two lines to `~/.npmrc` (0600), leaving the rest of the file
49
+ untouched:
39
50
 
40
51
  ```
41
52
  @gigabuddy:registry=https://npm.gigabuddy.com/
42
53
  //npm.gigabuddy.com/:_authToken=<registry credential>
43
54
  ```
44
55
 
45
- **That credential is registry-scoped.** It can install what you can install and
46
- nothing else on the platform because `.npmrc` is a file that ends up in CI
47
- logs and is readable by every postinstall script that runs on your machine. It
48
- lives 30 days (npm has nowhere to put a token refresh), and it dies with your
49
- session: signing out, or an admin revoking the session, stops installs within
50
- about a minute. Re-run `gigabuddy login --npm` to get a fresh one without
51
- another browser round-trip.
52
-
53
- Which packages you can install is decided per install, against your own access —
54
- the credential only proves who you are.
55
-
56
- ## Scope
56
+ The npm credential is registry-scoped: it authorizes package installs and
57
+ nothing else. It expires after 30 days and is revoked when you sign out;
58
+ refresh it with `gigabuddy login --npm`. Package access is checked per
59
+ install against your account.
57
60
 
58
- This CLI does authentication and local setup, and nothing else. Gigabuddy's
59
- capabilities live behind hosted APIs; this is how you prove who you are to them.
61
+ ## Requirements
60
62
 
61
- Requires Node 20+. No dependencies.
63
+ Node 20 or later. No dependencies.
62
64
 
63
- ---
65
+ ## License
64
66
 
65
- Internal notes for maintainers live in `NOTES.md` in the source repo — they are
66
- deliberately not shipped in this package.
67
+ MIT