kylon-cli 0.7.10-next.1462 → 0.7.11-next.1468

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
@@ -42,13 +42,17 @@ The CLI is also published to npm as
42
42
  [`kylon-cli`](https://www.npmjs.com/package/kylon-cli). The Web UI provides
43
43
  two distinct copy-paste entry points:
44
44
 
45
- - **Settings → Developer tools → Kylon CLI** shows the hosted install
46
- one-liner above; installing chains straight into the browser sign-in, and
47
- on an installed machine `kylon login` with no flags does the same and lets
48
- the browser approval page choose the workspace. An **Advanced** expander
49
- keeps the setup-token and `npx --yes kylon-cli@<tag> auth login` fallbacks
50
- for machines that cannot run the script. Its **Use with Your Agents**
51
- prompt teaches Claude Code, Codex, Grok Build, Hermes, or OpenClaw to discover and use
45
+ - **Settings → Developer tools → Kylon CLI** (also reached from the avatar
46
+ menu's **Install Kylon CLI**) offers two ways in. **Install in terminal**
47
+ shows the hosted install one-liner above for the visitor's OS; installing
48
+ chains straight into the browser sign-in, and on an installed machine
49
+ `kylon login` with no flags does the same and lets the browser approval page
50
+ choose the workspace. Below it, **No browser on this computer?** mints a
51
+ one-time setup-token command (`npx --yes kylon-cli@<tag> auth login
52
+ --setup-token …`) for a terminal nobody can approve from. **Install with AI**
53
+ gives a prompt to paste into a coding agent: it checks `kylon status`,
54
+ installs with `KYLON_INSTALL_NO_LOGIN=1`, signs in with
55
+ `kylon login --workspace <id>`, and then discovers and uses
52
56
  `kylon workspace` commands without assuming a provider-specific interface.
53
57
  - **An external agent's Profile** shows
54
58
  `npx --yes kylon-cli@<version> agent link --url '<one-time link>'`. Custom
@@ -371,7 +375,7 @@ agent work to finish, installs the managed bundle under `~/.kylon/bin`, and
371
375
  restarts onto it. The server never requests `--force` automatically.
372
376
 
373
377
  The owner can change the setting under **Settings → Developer tools → Kylon
374
- CLI → Authorized devices**, or from that computer:
378
+ CLI → Devices** (open the computer's row), or from that computer:
375
379
 
376
380
  ```bash
377
381
  kylon gateway auto-update status
@@ -680,8 +684,8 @@ Two consequences worth knowing:
680
684
  ### Sign in for workspace commands
681
685
 
682
686
  For a person using `kylon workspace ...` from their own terminal, open the
683
- workspace's **Settings → Kylon CLI** section, expand it, and copy its setup
684
- command, or run:
687
+ workspace's **Settings → Kylon CLI** section (or the avatar menu's **Install
688
+ Kylon CLI**) and copy the install command, or run:
685
689
 
686
690
  ```bash
687
691
  npx --yes kylon-cli@latest auth login --workspace <WORKSPACE_ID>
@@ -763,10 +767,11 @@ recently authorized entry. If Kylon cannot confirm revocation, it keeps the loca
763
767
  credential so you can retry. `kylon auth logout --local-only` deliberately skips
764
768
  the remote revocation. This logout is deliberately credential-only: it does not
765
769
  disconnect the local agent runtime or change connected agents. If that installation
766
- still runs external agents, it remains listed as an **Authorized device** so its
770
+ still runs external agents, it remains listed under **Devices** so its
767
771
  runtime access can still be removed without signing the CLI in again.
768
772
 
769
- You can instead remove an **Authorized device** from **Settings → Kylon CLI**.
773
+ You can instead remove a device from **Settings → Kylon CLI → Devices** (open
774
+ its row, then **Remove device**).
770
775
  After warning about the impact, that workspace-scoped action revokes any active
771
776
  installation credential, removes the local runtime access associated with the
772
777
  same installation, and disconnects every external agent using it. The device's
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "0.7.10-next.1462",
3
- "fingerprint": "adec961347fcf70e5df6ec59ae1f07110e7532e588b4ee082c5506a167096e0f",
4
- "source_commit": "f1805e01f7c10c043961cc4fd9294408cfb7cccb"
2
+ "version": "0.7.11-next.1468",
3
+ "fingerprint": "031d702c2b1a3b48e9cbf881bf32f0286ba236164e13ec0a37414e57534e2788",
4
+ "source_commit": "54a4b165ddc17f682f5c42615d8ab2f4d50dc4fe"
5
5
  }