kylon-cli 0.4.4-next.809 → 0.5.0-next.810

package/README.md

@@ -98,12 +98,34 @@ The installer hands `kylon onboard` the controlling terminal for its one local
 question; on a machine without one (CI, a headless box) it passes `--yes` and
 the browser confirmation is the only gate.
 
-Which agent it builds from is decided first, and never by guessing twice:
-`--provider claude-code|codex` decides outright; otherwise, when only one of
-the two has anything on this machine, that one is used; when both do, you are
-asked. A run that cannot ask — `--yes`, `--json`, or the hosted installer's
-non-TTY pipe — uses Claude Code, which is what the command has always meant, and
-says so when it passed over Codex.
+All detected providers are selected by default. When both Claude Code and
+Codex are present, the interactive selector starts with both checked; deselect
+either one by number, then press Enter. At least one must remain selected.
+Non-interactive runs (`--yes`, `--json`, or a headless installer) also select
+all detected providers. Use `--provider claude-code|codex|all` to override
+selection explicitly, including when detection finds no context.
+`--main-provider claude-code|codex` designates the main agent and must name a
+selected provider; otherwise the first selected provider is main. When neither
+provider is detected and there is no override, Claude Code remains the fallback.
+
+The browser shows the selected agent count, lets you deselect either provider,
+choose the main agent, and edit each agent's name, avatar and imports separately.
+Both agents join the selected Rooms. Same-named imported skills from different
+providers are stored separately, with provider-prefixed workspace slugs.
+`--agent-name` is for single-provider runs; team names are edited in the browser.
+
+```bash
+kylon onboard --yes --provider all --main-provider codex
+kylon onboard --yes --json --provider claude-code --no-start
+```
+
+Codex global memory remains opt-in through `--include-memory`, including when
+both providers are selected. Each provider must pass its own authentication
+check. If only one connection succeeds after workspace creation, the CLI keeps
+that connection and its recovery record. Run `kylon onboard` again to connect
+only the remaining agent to the same workspace; it does not create another
+workspace or restart completed connections. The shared runtime starts once
+all selected connections are saved (unless `--no-start` is set).
 
 It detects, offline and read-only, the project (the nearest `.git` ancestor,
 named from its `origin` repository when available and otherwise from its
@@ -159,9 +181,9 @@ and symlinks are never uploaded. Its terminal summary shows the semantic
 project name and its source separately from the physical checkout root. It then
 asks once (Enter confirms) and opens your browser: you sign in or sign up,
 review the proposal, rename or untick anything, and press one button. The
-workspace, its Rooms, the agent, its persona, its skills, and its memory are
-created there; the terminal then connects this computer's agent and starts the
-local runtime. Nothing durable exists until you press that button — an
+workspace, its Rooms, and each selected agent with its own persona, skills and
+memory are created there; the terminal then connects the selected agents on
+this computer and starts the local runtime. Nothing durable exists until you press that button — an
 abandoned run leaves only expiring server-side state.
 
 It never attaches to an existing workspace. For that, use `kylon login` and

package/dist/kylon-bundle.manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.4.4-next.809",
-  "fingerprint": "63238b13572e54b7768f52c7cbf3bf9e8edbc232929cb7e4721a0dafdceff83b",
-  "source_commit": "644d31251e30c0c5c1925baf596cd4176a281761"
+  "version": "0.5.0-next.810",
+  "fingerprint": "2835d5b91ae9fe73cbc9bbb1169dd6e21f6160a5504aa96aad11a8d2f9f6823d",
+  "source_commit": "ecd4539daf8a6adb6d4f1c40b043ae58bc7644b0"
 }