@usezynx/cli 0.1.1 → 0.1.2

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.
Files changed (2) hide show
  1. package/README.md +144 -0
  2. package/package.json +4 -3
package/README.md ADDED
@@ -0,0 +1,144 @@
1
+ # @usezynx/cli
2
+
3
+ The native command-line companion for [**ZynxTerminal**](https://usezynx.com) — an
4
+ AI-native, highly configurable terminal and SSH workspace.
5
+
6
+ `zynx` is a small, fast Rust binary (no Node runtime at execution time). It shares the
7
+ same engine as the ZynxTerminal desktop app, so what you run in the terminal and what you
8
+ script in CI behave identically.
9
+
10
+ > **Platform:** Windows x64 only for now. macOS/Linux builds are planned. Installing on an
11
+ > unsupported platform is blocked cleanly rather than installing something that can't run.
12
+
13
+ ---
14
+
15
+ ## Install
16
+
17
+ ```bash
18
+ # Global install (recommended)
19
+ npm install -g @usezynx/cli
20
+
21
+ # Or run once without installing
22
+ npx @usezynx/cli --version
23
+ ```
24
+
25
+ The install pulls a single prebuilt binary matching your OS/arch (`@usezynx/cli-win32-x64`)
26
+ as an optional dependency — there is **no post-install download step**, so it works behind
27
+ corporate proxies and in offline/air-gapped setups.
28
+
29
+ Verify it:
30
+
31
+ ```bash
32
+ zynx --version
33
+ zynx --help
34
+ ```
35
+
36
+ ---
37
+
38
+ ## Commands
39
+
40
+ ### `zynx run -- <command> [args...]`
41
+
42
+ Run a command inside a native headless pseudo-terminal (ConPTY) and stream its output
43
+ **byte-for-byte** to stdout. The child's **exit code is propagated**, so `zynx run` is safe
44
+ to use in scripts and CI pipelines.
45
+
46
+ ```bash
47
+ # Simple command
48
+ zynx run -- cmd /c echo hello
49
+
50
+ # Run your test suite; exit code is forwarded to the shell
51
+ zynx run -- npm test
52
+
53
+ # PowerShell one-liner
54
+ zynx run -- powershell -NoProfile -Command "Get-Date"
55
+ ```
56
+
57
+ Everything after `--` is passed to the child untouched. Program output goes to **stdout**;
58
+ status and errors go to **stderr**, so the stream stays pipeable:
59
+
60
+ ```bash
61
+ zynx run -- npm run build > build.log
62
+ ```
63
+
64
+ > `--profile <name>` is accepted for forward-compatibility but is not wired up yet; the
65
+ > default system shell is used.
66
+
67
+ ### `zynx config get [key]`
68
+
69
+ Print your ZynxTerminal configuration. With no key, prints the full config as JSON; with a
70
+ key, prints just that value.
71
+
72
+ ```bash
73
+ zynx config get # full config (pretty JSON)
74
+ zynx config get theme # -> "system"
75
+ zynx config get fontSize # -> 16.0
76
+ ```
77
+
78
+ ### `zynx config set <key> <value>`
79
+
80
+ Update a single configuration value. Changes are shared with the desktop app.
81
+
82
+ ```bash
83
+ zynx config set theme dark
84
+ zynx config set fontSize 15
85
+ ```
86
+
87
+ ### `zynx whoami`
88
+
89
+ Show the account you're signed in as. The CLI reads the credential stored by the
90
+ ZynxTerminal desktop app from the Windows Credential Manager and exchanges it for your
91
+ account id.
92
+
93
+ ```bash
94
+ zynx whoami # -> Logged in as: <uid> (or "Not logged in.")
95
+ ```
96
+
97
+ > A standalone `zynx login` is not available yet — sign in through the desktop app first.
98
+ > The terminal is fully usable signed-out; accounts are opt-in.
99
+
100
+ ---
101
+
102
+ ## Global flags
103
+
104
+ | Flag | Description |
105
+ | ----------- | --------------------------------------------------------------------------- |
106
+ | `--json` | Emit machine-readable JSON status/events on **stderr** (for CI/scripting). |
107
+ | `--version` | Print the version. |
108
+ | `--help` | Print help for `zynx` or any subcommand (e.g. `zynx run --help`). |
109
+
110
+ Example:
111
+
112
+ ```bash
113
+ zynx --json run -- npm test
114
+ # stdout: byte-exact test output
115
+ # stderr: {"type":"pty_exit","session":"run","code":0}
116
+ ```
117
+
118
+ ---
119
+
120
+ ## Output contract
121
+
122
+ - **stdout** — the child program's raw output, unmodified. Pipe/redirect it freely.
123
+ - **stderr** — Zynx status messages, prompts, and errors. With `--json`, these become
124
+ structured JSON lines.
125
+ - **exit code** — mirrors the child process, so `&&`, `||`, and CI gates work as expected.
126
+
127
+ ---
128
+
129
+ ## Security
130
+
131
+ - Secrets (API keys, tokens, SSH passphrases) live in the **Windows Credential Manager**,
132
+ never in config files or logs.
133
+ - Log output is passed through a redaction layer that strips keys, tokens, and passwords.
134
+
135
+ ---
136
+
137
+ ## Links
138
+
139
+ - Website: https://usezynx.com
140
+ - Documentation: https://docs.usezynx.com
141
+
142
+ ## License
143
+
144
+ MIT
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@usezynx/cli",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "description": "Native CLI for ZynxTerminal (Windows x64)",
5
5
  "license": "MIT",
6
6
  "os": [
@@ -13,12 +13,13 @@
13
13
  "zynx": "bin/zynx.js"
14
14
  },
15
15
  "files": [
16
- "bin/"
16
+ "bin/",
17
+ "README.md"
17
18
  ],
18
19
  "publishConfig": {
19
20
  "access": "public"
20
21
  },
21
22
  "optionalDependencies": {
22
- "@usezynx/cli-win32-x64": "0.1.1"
23
+ "@usezynx/cli-win32-x64": "0.1.2"
23
24
  }
24
25
  }