@kontourai/station-cli 0.6.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,273 @@
+# @kontourai/station-cli
+
+Station is Kontour's local-first agent workspace: you direct agent work, and
+the gate verdicts, evidence, and trust state stay in the same context as the
+work. A Station is the process that holds all of that — on your laptop, a home
+server, or another machine on your tailnet.
+
+This package is the **client** CLI for those Stations. It is a terminal front end
+for Stations that are already running: chat with agents, read and interrupt
+sessions, drive projects, tasks, skills, and every other Station
+surface, over HTTP. It does not run a Station itself — see
+[What this CLI does not do](#what-this-cli-does-not-do).
+
+## Availability
+
+The `npx`/`npm install -g` forms below work once `@kontourai/station-cli` is
+live on the npm registry (station#4536; check with `npm view
+@kontourai/station-cli`) — until then they 404, and `./station` from a
+Station checkout, further down this section, is the way to run the CLI.
+
+Run the CLI with `npx`, pinned to the channel dist-tag matching the Station
+you are operating — `nightly` for a Station Nightly host, `latest` for a
+stable one:
+
+```bash
+npx @kontourai/station-cli@latest --help
+npx @kontourai/station-cli@nightly --help
+```
+
+`npx` resolves and caches that exact published version per invocation, so the
+channel tag is the whole story: no separate install/upgrade step, and no
+ambiguity about which build is running. For latency-sensitive or scripted use,
+an explicit global install pins one version instead of resolving on every
+call: `npm install -g @kontourai/station-cli@<tag>`.
+
+**Inside a Station checkout**, `./station` runs that tree's own build directly
+— this is the local-invocation path when the registry isn't the point (working
+on the CLI itself, or a channel tag you don't want to depend on):
+
+```bash
+./station <command> [args]
+```
+
+It refuses to run against a stale build rather than silently executing old
+code — see [the CLI reference](https://github.com/kontourai/station/blob/main/docs/reference/cli.md#invocation)
+for the freshness gate and the three-tier invocation story (`npx` / `./station`
+/ the `station-dev` global dev shim).
+
+Every invocation reports where it came from: `station --version` prints the
+CLI version, its build channel, and the source revision the artifact was built
+from, so a wrong-binary mistake is visible instead of guessed at.
+
+## Sixty seconds to a working setup
+
+Choose a Station you can reach. Setup saves it on this device, performs pairing
+when needed, and deliberately selects the default Station.
+
+```bash
+npx @kontourai/station-cli@latest setup existing box-b https://box-b.tailnet.ts.net --pair
+# or use Kontour's hosted Station
+npx @kontourai/station-cli@latest setup hosted
+```
+
+The CLI registers a device request and waits. An operator approves it **on the
+host** (`station environment access approve <request-id>` there). When they do,
+the CLI stores the issued bearer credential in the operating-system keyring and
+saves only its reference with the Station entry. That Station becomes the
+default only after pairing succeeds.
+
+That is the whole point of pairing: from then on, nothing needs a flag.
+
+```bash
+station agents list
+station chat my-agent 'what changed today?'
+```
+
+From a Station checkout, local setup installs its durable per-user service and
+then selects the conventional `kontour` Station:
+
+```bash
+./station setup local
+```
+
+## Saved Stations
+
+These are the Stations this device can reach. Forgetting one only removes its
+local entry and credential reference; it does not stop or delete the Station.
+They are separate from the Environment where an Agent executes and the engine
+that runs it.
+
+```text
+station stations list
+station stations show <name>
+station stations add <name> <endpoint> [--pair] [--default] [--force]
+station stations edit <name> <endpoint> [--pair] [--default] [--force]
+station stations pair <name> [--force]
+station stations use <name>
+station stations forget <name>
+station stations project show|use <name>|clear
+station stations export
+station target [--station=<name>|--api-base=<url>]
+```
+
+```console
+$ station stations list
+  NAME     ENDPOINT                        CREDENTIAL
+* box-b    https://box-b.tailnet.ts.net    available
+  kontour  http://127.0.0.1:<channel-port> not-configured
+
+* = default Station.
+```
+
+Every command that talks to a Station resolves its target in this order:
+
+| | Source | Example |
+|---|---|---|
+| 1 | `--api-base=<origin>` | one direct bootstrap/diagnostic request |
+| 2 | `--station=<name>` | `station chat --station=box-b` |
+| 3 | `STATION_TARGET` | `STATION_TARGET=kontour station agents list` |
+| 4 | Project Station selection | owner-controlled mapping set by `station stations project use` |
+| 5 | Explicit default Station | set by setup or `station stations use` |
+| 6 | Active local Station | owner-safe local service record |
+| 7 | Loopback fallback | the selected channel's runtime-resolver server port (or `STATION_PORT`) |
+
+## Guided triage
+
+`station triage [--context-only] [--agent=codex|claude] [--problem=<text>] [--search-issues]` writes a bounded,
+owner-only diagnostic hand-off under `$STATION_ROOT/cache/triage/<uuid>`.
+It contains redacted schema-v1 JSON, a readable summary, and Station's
+versioned read-only playbook. With an existing credential it uses the
+authenticated diagnostics-bundle seam, retaining only bounded allowlisted app,
+doctor, and log-tail facts; it never persists bearer values or bundle config.
+It never reads local-grant or pairing secrets, databases, arbitrary environment
+data, or full logs.
+
+Use `--context-only` when you want artifacts without agent probing or launch;
+the same read-only source and authenticated remote facts are still collected.
+Otherwise Station starts only Codex with approval disabled, its read-only
+sandbox, an ephemeral session, and user config ignored, or Claude in safe plan
+mode with only Read/Glob/Grep tools, using argv arrays and a run-local prompt
+file. With both available,
+select one explicitly. No available agent still
+leaves portable artifacts successfully. The bundled CLI does not inspect the
+local host filesystem or run the source-only doctor report.
+Problem text stays local unless `--search-issues` (or the equivalent TTY
+confirmation) explicitly authorizes a fixed, read-only Station issue search.
+Successful agent output is bounded and re-redacted into local `diagnosis.md`
+and `issue-draft.md`; triage has no GitHub write or repair operation.
+
+The versioned store lives at `$STATION_ROOT/config/profiles.json` (default
+`~/.station/config/profiles.json`) and is shared with native Desktop. It
+never contains bearer material. A missing or unavailable OS credential store
+fails closed; Station does not create a plaintext fallback. `station target`
+shows the selected Station, endpoint, Environment association, credential
+state, reachability, and applicable local-service state without starting or
+substituting another Station.
+
+Use `--pair` while adding or editing, or `station stations pair <name>`, to
+authenticate a named Station through host approval. Plain add/edit intentionally
+creates or updates only endpoint metadata and reports that no credential is
+configured. Pairing does not replace an existing endpoint binding unless the
+edit action or `--force` explicitly authorizes it.
+
+Project selection is explicit and secret-free. `station stations project use`
+records the canonical invoked directory and selected Station in the
+owner-controlled shared store; repository files cannot redirect the target.
+The selection names a saved Station and never embeds an endpoint or credential.
+
+Requests give up after 30 seconds. Override with
+`STATION_REQUEST_TIMEOUT_MS=<ms>`, or `0` to disable the deadline. Streams —
+chat and session turns, orchestration and approval event streams, live
+monitoring, knowledge reindexing — are deliberately exempt, because they are
+open-ended by design.
+
+## What this CLI does not do
+
+**It does not run a Station.** These verbs act on a Station *repository
+checkout* — building the app, starting or upgrading it, installing OS
+services, putting the launcher on PATH:
+
+`build` · `doctor` · `fresh` · `link` · `service` · `shortcut` · `start` ·
+`upgrade`
+
+They are not part of the published CLI. Run them from the root of a Station
+checkout with its own launcher, which is where they have always lived:
+
+```console
+$ station start
+Error: `station start` runs against a Station repository checkout, so it is not part of the published CLI.
+Run it from the root of a Station checkout with the bundled launcher:
+    ./station start
+The published CLI drives Stations that are already running — see `station stations`, `station setup hosted`, and `--api-base`.
+```
+
+**Some `environment` verbs are host-local.** Identity, credential, and
+device-approval commands read secrets that only exist on the machine running
+the Station, so they answer from the host's own `./station` and nowhere else:
+`environment show`, `environment credential`, `environment reset`, and
+`environment offer`, and `environment access list|approve|deny`.
+
+```console
+$ station environment show
+Error: Environment security commands require the Station repository launcher (./station).
+```
+
+`station environment access request` is the exception, and the one you want
+here: it is the *requester* side of pairing, and it is a pure client.
+
+The packaged CLI never starts, stops, builds, installs, or otherwise manages a
+Station backend implicitly. A bare invocation (including `--inline`,
+`--service`, and `--temp-home`) explains how to pair with an existing host or
+how to use `./station` from a checkout. Host-side pairing offers and approvals
+remain in that host's UI/checkout; the packaged client only requests access.
+
+`station --version` reports immutable bundle metadata: the CLI version, its
+build channel, and the source revision stamped when that artifact was built.
+It does not inspect a nearby checkout or a backend build manifest. Local source
+builds report the `development` channel (and a dirty revision when applicable),
+independent of `STATION_CHANNEL`.
+
+The package test packs one exact tarball, records its SHA-256, then installs
+that same tarball into an isolated consumer with `npm install --ignore-scripts`.
+This proves dependency resolution without claiming publication or
+native-keyring behavior. Windows and physical native-keyring verification are
+**NOT_VERIFIED** until exercised on those platforms.
+
+`station --help` prints the same boundary in its closing note, so the printed
+command list never claims a verb this CLI cannot run.
+
+## Requirements
+
+- **Node 24** (`engines: 24.x`). The CLI is a bundle, not a binary; it needs a
+  host Node.
+- **A reachable Station.** Everything this CLI does, apart from managing
+  its own saved Stations and config, is an HTTP call to a Station server. With no
+  Station saved, commands use a running local desktop Station when available,
+then fall back to the selected channel's runtime-resolver loopback origin.
+
+Transport failures name the Station that was targeted *and where that address
+came from*, so a wrong-target mistake never looks like a broken Station:
+
+```console
+$ station agents list
+Error: Can't resolve the host in https://box-b.tailnet.ts.net (default Station "box-b"). Check the address or inspect it with `station target --station=box-b`.
+```
+
+## Getting the full reference
+
+```bash
+station --help                 # grouped, one line per command
+station <command> --help       # actions and flags for one command
+station --version
+```
+
+`--help` is recognised at any depth, and per-command help carries the flag
+detail. Unknown input is always a failure, never a help request: the CLI exits
+non-zero and names the nearest real command or action.
+
+The full prose reference — every verb, every flag, and the complete tier
+table — ships with the Station repository as `docs/reference/cli.md`.
+
+## Related packages
+
+- [`@kontourai/station-sdk`](https://www.npmjs.com/package/@kontourai/station-sdk)
+  — build a Station plugin: UI components, hooks, and typed host API access.
+- [`@kontourai/station-shared`](https://www.npmjs.com/package/@kontourai/station-shared)
+  — `buildPlugin`, manifest parsing, and the other runtime helpers.
+- [`@kontourai/station-contracts`](https://www.npmjs.com/package/@kontourai/station-contracts)
+  — the TypeScript contracts those packages are typed against.
+
+## License
+
+Apache-2.0, the same licence as the rest of the `@kontourai/station-*` family.