kenso 0.1.8 → 0.1.11
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 +7 -3
- package/dist/kenso.js +3 -3
- package/dist/operations.json +1 -1
- package/docs/auth.md +6 -2
- package/docs/reference.md +456 -299
- package/package.json +2 -2
package/docs/auth.md
CHANGED
|
@@ -27,9 +27,13 @@ kenso auth login
|
|
|
27
27
|
kenso auth login --no-browser --device-name "build box"
|
|
28
28
|
```
|
|
29
29
|
|
|
30
|
-
Browser login is
|
|
30
|
+
Browser login is available to every workspace. The CLI prints a link and a code on stderr. You open the link, sign in to app.ken.so, check that the code matches the one in your terminal, pick the workspace to start in and approve. The CLI then saves a new API key to the profile and prints:
|
|
31
31
|
|
|
32
|
-
|
|
32
|
+
```json
|
|
33
|
+
{"profile":"default","email":"you@acme.io","workspaceId":"1234","keyExpiresAt":"2027-02-02T06:26:59Z"}
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
The key is the same kind you create in the app. It is named `Kenso CLI - <device name>` (`--device-name`, else `kenso-cli on <hostname>`), lasts 90 days, and shows in your API key list at Settings > Integrations > API keys, where you can revoke it. The CLI opens the browser itself only when no coding agent is detected and the machine has a display. An agent prints the link and asks you to open it. The login expires after 10 minutes (`login_expired`, exit 3), and a denied login exits 3 with `access_denied`. If the API answers that browser login is off (`browser_login_unavailable`, exit 3, `"next":"kenso auth login --with-key"`), log in with an API key as above.
|
|
33
37
|
|
|
34
38
|
## CI, scripts and agents: use the environment
|
|
35
39
|
|