@kontourai/station-cli 0.7.0 → 0.8.0-nightly.2482.39124399487
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 +23 -1
- package/dist/station.mjs +457 -306
- package/package.json +12 -10
package/README.md
CHANGED
|
@@ -80,6 +80,14 @@ station agents list
|
|
|
80
80
|
station chat my-agent 'what changed today?'
|
|
81
81
|
```
|
|
82
82
|
|
|
83
|
+
Chat assigns a fresh turn key before sending. Use `--json` to retain
|
|
84
|
+
`clientTurnId` and `conversationId` in success, pending, or failure output, or
|
|
85
|
+
choose a key before sending with `--client-turn-id=<key>`. Reuse that key only
|
|
86
|
+
for a deliberate retry of the same operation; keep the original conversation
|
|
87
|
+
flag for a continuation. Inspect uncertain outcomes first. The CLI never
|
|
88
|
+
resends automatically. See [chat identity and retry](../../docs/reference/cli.md#chat)
|
|
89
|
+
for the error format and new-chat conversation binding.
|
|
90
|
+
|
|
83
91
|
From a Station checkout, local setup installs its durable per-user service and
|
|
84
92
|
then selects the conventional `kontour` Station:
|
|
85
93
|
|
|
@@ -205,9 +213,23 @@ The published CLI drives Stations that are already running — see `station stat
|
|
|
205
213
|
|
|
206
214
|
**Selected local operations are available in the published CLI.** `open`,
|
|
207
215
|
`doctor`, `environment show`, `environment credential show`, `environment offer`,
|
|
208
|
-
`environment access list|approve|deny|devices|scope`, and `service status|start|stop` support
|
|
216
|
+
`environment access list|approve|deny|devices|scope|revoke|remove`, `environment operator passkeys`, and `service status|start|stop` support
|
|
209
217
|
an existing local installation. Local authorization validates the selected
|
|
210
218
|
owner-only home and the loopback listener; it does not create a missing home.
|
|
219
|
+
Bare host-approval commands prefer the live listener in the selected local home
|
|
220
|
+
before project or saved-default Stations; explicit targets keep their precedence.
|
|
221
|
+
`environment offer` creates a single-use invitation with Standard access. Choose
|
|
222
|
+
ordinary Device-use permissions; protected management and consent permissions
|
|
223
|
+
require a separate operator promotion after pairing. Choose
|
|
224
|
+
`--scope` to change that access, `--require-approval` to review the recipient first,
|
|
225
|
+
or `--browser-url=<web-origin>` to print a link for the web UI.
|
|
226
|
+
For a saved paired Station, `environment access devices|scope|revoke|remove`
|
|
227
|
+
use its paired credential and work remotely when the operator explicitly grants
|
|
228
|
+
`access:devices`. This is separate from using full access. Only the operator can
|
|
229
|
+
grant or remove this administrative scope; legacy `access:manage` does not
|
|
230
|
+
qualify. See [device administration](../../docs/reference/cli.md#environment) for
|
|
231
|
+
setup, revocation and mixed-version limits.
|
|
232
|
+
|
|
211
233
|
Service start/stop controls an existing OS service rather than building or
|
|
212
234
|
installing a backend. See the [availability table](../../docs/reference/cli.md)
|
|
213
235
|
for the full boundary and prerequisites.
|