kylon-cli 0.2.2-next.286 → 0.2.2-next.289
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 +19 -1
- package/dist/kylon-bundle.mjs +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -35,6 +35,22 @@ The dist-tag tracks the environment: production uses `@latest`, dev uses
|
|
|
35
35
|
Requirements: Node.js 22.15.0+ (npm ships with Node). Linux / macOS only
|
|
36
36
|
(Windows operators should use WSL).
|
|
37
37
|
|
|
38
|
+
### One managed `kylon` for humans and agents
|
|
39
|
+
|
|
40
|
+
Both bootstrap commands (`connect` and `auth login`) pin the CLI under
|
|
41
|
+
`~/.kylon/bin`: the exact bundle the daemon and its agents execute, exposed as
|
|
42
|
+
the `kylon` command. After the bootstrap they offer to add that directory to
|
|
43
|
+
your shell PATH (a marker-wrapped `. "$HOME/.kylon/env"` line in your shell rc,
|
|
44
|
+
or a fish `conf.d` drop-in; decline with `--no-modify-path`). From then on the
|
|
45
|
+
human terminal, the agents, and the daemon all run the same file — one
|
|
46
|
+
artifact, one version, one upgrade.
|
|
47
|
+
|
|
48
|
+
A leftover npm-global or npx-cached copy stays harmless: when it starts and
|
|
49
|
+
finds a strictly newer pinned install, it defers to it automatically
|
|
50
|
+
(installer commands — `connect`, `gateway …` — always run as invoked, so a
|
|
51
|
+
fresh `npx` can still install itself over an older pinned copy; set
|
|
52
|
+
`KYLON_PINNED_TRAMPOLINE=0` to disable the deferral).
|
|
53
|
+
|
|
38
54
|
### Upgrading a gateway host
|
|
39
55
|
|
|
40
56
|
```bash
|
|
@@ -96,7 +112,9 @@ request but never receives the credential. The CLI proves possession of its PKCE
|
|
|
96
112
|
verifier while polling Kylon over HTTPS, receives the credential directly from
|
|
97
113
|
the API, and saves it in the versioned credential collection at
|
|
98
114
|
`~/.kylon/workspace-auth.json` with mode `0600`. No loopback listener, incoming
|
|
99
|
-
port, or browser request to localhost is used.
|
|
115
|
+
port, or browser request to localhost is used. On success the CLI also pins
|
|
116
|
+
itself under `~/.kylon/bin` and offers to put that directory on your PATH, so
|
|
117
|
+
subsequent commands are plain `kylon workspace ...` with no npx.
|
|
100
118
|
The collection keeps credentials separately by server and workspace, and
|
|
101
119
|
`--scope-workspace` selects the matching entry.
|
|
102
120
|
|