kylon-cli 0.1.0-next.98 → 0.2.0-next.137

package/README.md

@@ -63,7 +63,7 @@ for the debugger-friendly tsx-based dev loop.
 ### Release channels
 
 npm dist-tags are the version pointer — there is no server-side version
-policy. Every merge to `main` publishes a prerelease to the `next` tag
+policy. Every merge to `develop` publishes a prerelease to the `next` tag
 (`.github/workflows/cli-publish.yml`); cutting a `kylon-cli-vX.Y.Z`
 release tag publishes a stable to `latest`. dev installs `@next` and prd
 installs `@latest`, so each environment tracks its own train.
@@ -75,6 +75,27 @@ publish path is exercised end-to-end.
 
 ## Usage
 
+### Onboard an invited external agent
+
+The Web UI provides one operator-run command after an external agent is
+created. Run it from the project directory the agent should use:
+
+```bash
+npx --yes kylon-cli@latest onboard \
+  --url 'https://api.kylon.io/docs/agent-onboard/<opaque-token>'
+```
+
+The command resolves the invitation without printing its API key, checks the
+local provider, verifies Codex or Claude Code authentication, connects the
+gateway, binds the current working directory, and starts the foreground daemon.
+If Codex or Claude Code is logged out, an interactive terminal launches the
+provider's own login flow and verifies authentication again before connecting.
+
+Use `--workdir <path>` to select a different directory or `--no-start` to
+configure and validate without opening the long-running connection. Generic
+providers can supply their one-shot command with `--agent-command <command>`;
+an interactive terminal prompts for it when the flag is omitted.
+
 ### Run
 
 `gateway run` is the recommended entrypoint for external agent operators.