@asiyst/cli 1.1.1 → 1.1.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.
Files changed (4) hide show
  1. package/README.md +4 -2
  2. package/dist/index.js +966 -263
  3. package/dist/index.js.map +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -23,13 +23,15 @@ asiyst avatar import --avatar-id A7K9M2QX4P
23
23
  asiyst disconnect
24
24
  ```
25
25
 
26
- The connection flow asks for the 24-character Asiyst User ID and masks the API key while you enter it. The API verifies that the account, key, and selected project belong together. Avatar import uses the stored account, project, and key and requires a separate 10-character Avatar ID.
26
+ The connection flow asks for the 16-character Asiyst User ID, 24-character Project ID, and 32-character API key. The API verifies that the account, key, and selected project belong together. Avatar import uses the stored account, project, and key and requires a separate 10-character Avatar ID.
27
27
 
28
28
  Avatar import calls the authenticated CLI project import operation and sends `userId`, `projectId`, and `avatarId` as identifiers; the API key is sent only through authentication headers. The server remains responsible for ownership, project access, avatar existence, active-project checks, and duplicate detection.
29
29
 
30
+ After the server accepts the import, the CLI detects the framework, installs `@asiyst/sdk` with the project package manager when needed, and creates or updates the managed `src/components/AsiystAssistant.tsx`/`.jsx` component. It adds that component to a detected Next.js or React/Vite entry point without putting the secret API key in website code. Use `asiyst avatar import --dry-run` to inspect the files and configuration before making changes. If an existing integration uses a different project or avatar, the CLI asks before replacing it; it never creates numbered duplicate components.
31
+
30
32
  Interactive startup performs a lightweight npm version check. If a newer release exists, the CLI only displays a notification. It never installs or restarts automatically; run `update` and confirm to install it. Global installations are updated in place. For npx invocations, the latest package is downloaded and verified for that invocation without changing the website project.
31
33
 
32
- The CLI checks `GET /health`, verifies API keys via `POST /auth/api-key/verify` on `https://nqhxpgsjofzqudyqkqib.supabase.co/functions/v1/api`, and securely stores credentials. Passwords, AI provider keys, Supabase keys, and private API credentials are never requested, placed in URLs, or logged.
34
+ The CLI checks `GET /health` and verifies the complete connection relationship through `POST /verify/user`, `POST /verify/project`, `POST /verify/api-key`, and `POST /verify/avatar` on `https://nqhxpgsjofzqudyqkqib.supabase.co/functions/v1/api`. It creates an import session with `POST /import-session` before importing an avatar. Passwords, AI provider keys, Supabase keys, and private API credentials are never placed in URLs or logged.
33
35
 
34
36
  Production API defaults to `https://nqhxpgsjofzqudyqkqib.supabase.co/functions/v1/api`.
35
37