kylon-cli 0.7.11-next.1473 → 0.7.11

package/README.md

@@ -42,17 +42,13 @@ The CLI is also published to npm as
 [`kylon-cli`](https://www.npmjs.com/package/kylon-cli). The Web UI provides
 two distinct copy-paste entry points:
 
-- **Settings → Developer tools → Kylon CLI** (also reached from the avatar
-  menu's **Install Kylon CLI**) offers two ways in. **Install in terminal**
-  shows the hosted install one-liner above for the visitor's OS; installing
-  chains straight into the browser sign-in, and on an installed machine
-  `kylon login` with no flags does the same and lets the browser approval page
-  choose the workspace. Below it, **No browser on this computer?** mints a
-  one-time setup-token command (`npx --yes kylon-cli@<tag> auth login
-  --setup-token …`) for a terminal nobody can approve from. **Install with AI**
-  gives a prompt to paste into a coding agent: it checks `kylon status`,
-  installs with `KYLON_INSTALL_NO_LOGIN=1`, signs in with
-  `kylon login --workspace <id>`, and then discovers and uses
+- **Settings → Developer tools → Kylon CLI** shows the hosted install
+  one-liner above; installing chains straight into the browser sign-in, and
+  on an installed machine `kylon login` with no flags does the same and lets
+  the browser approval page choose the workspace. An **Advanced** expander
+  keeps the setup-token and `npx --yes kylon-cli@<tag> auth login` fallbacks
+  for machines that cannot run the script. Its **Use with Your Agents**
+  prompt teaches Claude Code, Codex, Grok Build, Hermes, or OpenClaw to discover and use
   `kylon workspace` commands without assuming a provider-specific interface.
 - **An external agent's Profile** shows
   `npx --yes kylon-cli@<version> agent link --url '<one-time link>'`. Custom
@@ -375,7 +371,7 @@ agent work to finish, installs the managed bundle under `~/.kylon/bin`, and
 restarts onto it. The server never requests `--force` automatically.
 
 The owner can change the setting under **Settings → Developer tools → Kylon
-CLI → Devices** (open the computer's row), or from that computer:
+CLI → Authorized devices**, or from that computer:
 
 ```bash
 kylon gateway auto-update status
@@ -684,8 +680,8 @@ Two consequences worth knowing:
 ### Sign in for workspace commands
 
 For a person using `kylon workspace ...` from their own terminal, open the
-workspace's **Settings → Kylon CLI** section (or the avatar menu's **Install
-Kylon CLI**) and copy the install command, or run:
+workspace's **Settings → Kylon CLI** section, expand it, and copy its setup
+command, or run:
 
 ```bash
 npx --yes kylon-cli@latest auth login --workspace <WORKSPACE_ID>
@@ -767,11 +763,10 @@ recently authorized entry. If Kylon cannot confirm revocation, it keeps the loca
 credential so you can retry. `kylon auth logout --local-only` deliberately skips
 the remote revocation. This logout is deliberately credential-only: it does not
 disconnect the local agent runtime or change connected agents. If that installation
-still runs external agents, it remains listed under **Devices** so its
+still runs external agents, it remains listed as an **Authorized device** so its
 runtime access can still be removed without signing the CLI in again.
 
-You can instead remove a device from **Settings → Kylon CLI → Devices** (open
-its row, then **Remove device**).
+You can instead remove an **Authorized device** from **Settings → Kylon CLI**.
 After warning about the impact, that workspace-scoped action revokes any active
 installation credential, removes the local runtime access associated with the
 same installation, and disconnects every external agent using it. The device's

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.7.11-next.1473",
-  "fingerprint": "c566becb0780ccc44f7b6d5cc685ad468081fdc47cc88a28c38e4cd543ddf5c8",
-  "source_commit": "fecda88d2cdb3fd2cffd171cf49e4c21dec44e52"
+  "version": "0.7.11",
+  "fingerprint": "272005ed15275b3dd048b722672524d783dc1e8c29a33366caac27f913d30f23",
+  "source_commit": "024dc0094a9e5bde2559d4c8ea3cb07fd9b33dc8"
 }