kylon-cli 0.7.10 → 0.7.11-next.1468

package/README.md

@@ -42,13 +42,17 @@ 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** 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
+- **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
   `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
@@ -371,7 +375,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 → Authorized devices**, or from that computer:
+CLI → Devices** (open the computer's row), or from that computer:
 
 ```bash
 kylon gateway auto-update status
@@ -680,8 +684,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, expand it, and copy its setup
-command, or run:
+workspace's **Settings → Kylon CLI** section (or the avatar menu's **Install
+Kylon CLI**) and copy the install command, or run:
 
 ```bash
 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
 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 as an **Authorized device** so its
+still runs external agents, it remains listed under **Devices** so its
 runtime access can still be removed without signing the CLI in again.
 
-You can instead remove an **Authorized device** from **Settings → Kylon CLI**.
+You can instead remove a device from **Settings → Kylon CLI → Devices** (open
+its row, then **Remove device**).
 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
@@ -841,6 +846,9 @@ instead of waiting out inactivity timeouts and heartbeat intervals.
   a readiness probe or assignment. Provider authentication and model selection
   remain in Grok's local configuration.
 - `hermes` — Hermes over ACP, using `hermes-acp` or `hermes acp`.
+- `antigravity` — Antigravity CLI over ACP, through the Antigravity ACP server
+  that `kylon provider install antigravity` installs. See
+  [Antigravity CLI](#antigravity-cli).
 - `openclaw` — OpenClaw CLI using `openclaw agent --message <prompt> --json`.
   A message too large for the command line is delivered as a file via
   `--message-file <path>` instead (requires OpenClaw 2026.6.11 or newer; the
@@ -936,7 +944,8 @@ back to another saved identity.
   or arbitrary error text. Identity and workspace attribution come from server
   authentication, not client fields.
 - **Anonymous** (status (`status`/`auth status`, `gateway status`), `diagnose`,
-  the upgrade commands (`upgrade`, `provider update`, `gateway service`)): the
+  the upgrade and install commands (`upgrade`, `provider update`,
+  `provider install`, `gateway service`)): the
   same URL without a credential, command outcomes only, with an even narrower
   metadata allowlist. The setup commands (`auth login`, `agent link`, `connect`,
   `onboard`) report anonymously only when they fail, with the setup session id
@@ -1290,6 +1299,30 @@ new production CLI build must be published. Service deployment alone leaves
   a fresh CLI-only PR from the current `main`, merge it, and dispatch stable
   on that commit, keeping `main` still until the CLI is published.
 
+- **Run the stable preflight before every stable dispatch.** A stable run
+  needs about an hour and a human approval before it reaches the gates that
+  most often fail, so check them first, read-only:
+
+  ```bash
+  node scripts/ci/cli-stable-preflight.mjs --mac-host p2compat@autodeploy-bj
+  ```
+
+  It takes the current `main` head (or `--sha <main sha>`) and prints one
+  pass/fail row per gate: the merged main PR behind that commit, the newest
+  production deploy and every changed file since it that is not CLI-only, the
+  merged PR's latest `preview-deploy.yml` run (completed, successful, and
+  merged onto `main`'s exact tree), the package version against npm `@latest`,
+  any stable `cli-publish.yml` run still queued or running, the
+  `p2-external-compat` macOS runner (online and idle; reading runners needs repo
+  admin), and, over SSH with `--mac-host`, the harness `active-run` lock. The
+  harness never steals that lock, so a held or stale one fails the row; recover
+  a stale lock through `external-agent-compat-harness.yml` `recovery_run`,
+  never by deleting it. The preflight dispatches, reruns and deletes nothing,
+  and exits non-zero when any row fails. It cannot see qualification failures,
+  Windows host state, or macOS privacy (TCC) denials for the runner service.
+  On the `publish_cli=true` and `release:cli` paths the production row passes
+  only after that Deploy completes; check the other rows before requesting it.
+
 Do not `npm publish` ad hoc: use the stable workflow and its OIDC provenance.
 Pushing a version tag alone does not publish.
 
@@ -1351,21 +1384,36 @@ request `external-agent:full`. Stable CLI publication always runs fresh full
 provider/platform qualification after the service deployment, independently
 of these cheap checks.
 
-### Gemini CLI
-
-Install stable Gemini CLI 0.58.0 or newer with
-`npm install -g @google/gemini-cli@latest`, then run `gemini` interactively to
-configure persistent Google sign-in or a securely stored API key. Select Gemini
-CLI in Kylon and run its Connect command. Kylon launches the installed
-`gemini --acp` through the shared ACP executor; the launch cannot be overridden
-with `agent configure`. Older installs receive an upgrade remedy. A successful
-handshake reports authentication as unverified until a real turn succeeds.
-
-Session loading, workspace MCP tools, streamed text/tool activity and
-cancellation use ACP. Kylon does not populate Gemini's global skill directories
-or forward arbitrary Google credential variables from the daemon environment.
-The model/effort picker, provider update command and Gemini quota display are
-not available for this provider.
+### Antigravity CLI
+
+Kylon runs Antigravity CLI through the Antigravity ACP server, a separate
+download that each Kylon CLI release pins and verifies:
+
+1. Install the server with `kylon provider install antigravity` (`--json` for
+   one machine-readable result). It downloads the pinned release, checks its
+   sha256 against the pin and, on macOS and Windows, the executables'
+   signature from Google, and unpacks it into
+   `~/.kylon/providers/antigravity-acp/<version>/`. Run again, it verifies the
+   existing install without downloading. Run it with the installed `kylon`
+   (`~/.kylon/bin/kylon` if it is not on your PATH), not through `npx`: it
+   removes server releases older than the one its own version pins, so a newer
+   copy would remove the one the running service starts. `kylon gateway service repair`
+   installs it as well when an Antigravity CLI agent on this computer has no
+   server, or when Kylon's copy no longer matches what it installed.
+2. Sign in once with `agy`, Antigravity CLI itself, which the server download
+   does not include. If `agy` is missing, `kylon provider install antigravity`
+   prints its installer. The server reuses that sign-in, and a turn it refuses
+   for want of one fails with the instruction to run `agy` once.
+3. Link the agent with the command Kylon gives you,
+   `kylon agent link --url "<link>"`. `--url` is required, and the provider
+   comes from the link: `kylon agent link --url "<link>" --provider antigravity`
+   restates it, and an agent's link refuses any other provider.
+
+The launch is built in: `agent configure` cannot override it. An Antigravity
+CLI agent runs only where the computer's running Kylon CLI reports Antigravity
+CLI support, so a link to a computer whose service still runs an older Kylon
+CLI is refused with `EXTERNAL_AGENT_CLI_PROVIDER_UNSUPPORTED` and leaves the
+link unused. Upgrade with `kylon upgrade`, then run the same setup again.
 
 
 Project-aware onboarding in CLI 0.6.0 requires an API and browser supporting

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.7.10",
-  "fingerprint": "55ea4526a571d7bf6bfe5208f7afbc9a906d2bf9c6e0c7bcb9f8dbb2b061e562",
-  "source_commit": "463880e40a8deef3aed33e447509f52710bd021e"
+  "version": "0.7.11-next.1468",
+  "fingerprint": "031d702c2b1a3b48e9cbf881bf32f0286ba236164e13ec0a37414e57534e2788",
+  "source_commit": "54a4b165ddc17f682f5c42615d8ab2f4d50dc4fe"
 }