@testrigor/testrigor-cli 1.0.1 → 2.0.0

package/README.md

@@ -4,12 +4,35 @@ This is a command line tool for TestRigor. It allows you to run TestRigor tests
 
 ### Installation
 
-1. Install [Node.js](https://nodejs.org/en/download/) (version 18 or higher)
-2. Install TestRigor CLI: `npm install -g testrigor-cli`
+1. Install [Node.js](https://nodejs.org/en/download/) (version 20.19+, 22.12+ or 24+)
+2. Install TestRigor CLI: `npm install -g @testrigor/testrigor-cli`
+3. Check it: `testrigor --version`
+
+> The unscoped `testrigor-cli` package on npm is an old, unmaintained build.
+> Install the scoped `@testrigor/testrigor-cli` package shown above; if you
+> installed the unscoped one, run `npm uninstall -g testrigor-cli` first.
+
+### Authentication
+
+Store your token once, interactively:
+
+```
+testrigor authenticate
+```
+
+For CI or any non-interactive shell, pass it in instead of being prompted:
+
+```
+testrigor authenticate --token YOUR_TOKEN
+echo YOUR_TOKEN | testrigor authenticate
+```
+
+Or skip stored credentials entirely and set `TESTRIGOR_API_KEY`, or pass
+`--token` to each command.
 
 ### Examples
 
-1. Basic  `testrigor test-suite run <test-suite-id> --token <token>`
+1. Basic `testrigor test-suite run <test-suite-id> --token <token>`
 2. With new URL `testrigor test-suite run <test-suite-id> --token <token> --url <url>`
 3. With file upload `testrigor test-suite run <test-suite-id> --token <token> --file-path <path-to-file>`
 4. With branch `testrigor test-suite run <test-suite-id> --token <token> --branch <branch> --commit <commit>`
@@ -47,6 +70,7 @@ testrigor test-suite run <test-suite-id> --token <token> --localhost --local-tes
 ```
 
 The CLI will:
+
 - Detect it's a mobile suite
 - Start the mobile server (Appium) automatically
 - Open a tunnel to TestRigor cloud
@@ -89,15 +113,6 @@ Every push to `master` runs the CircleCI `publish` workflow. It builds the tarba
    This updates the version in `package.json` and in both root entries of `package-lock.json` (`version` and `packages[""].version`). `--no-git-tag-version` stops npm from creating its own commit and `v*` tag. npm also runs the `version` script (`oclif readme && git add README.md`). That script loads the commands from `dist`, which is why you build first. It only rewrites README sections between oclif markers such as `<!-- commands -->
 * [`testrigor authenticate`](#testrigor-authenticate)
 * [`testrigor help [COMMANDS]`](#testrigor-help-commands)
-* [`testrigor plugins`](#testrigor-plugins)
-* [`testrigor plugins:install PLUGIN...`](#testrigor-pluginsinstall-plugin)
-* [`testrigor plugins:inspect PLUGIN...`](#testrigor-pluginsinspect-plugin)
-* [`testrigor plugins:install PLUGIN...`](#testrigor-pluginsinstall-plugin-1)
-* [`testrigor plugins:link PLUGIN`](#testrigor-pluginslink-plugin)
-* [`testrigor plugins:uninstall PLUGIN...`](#testrigor-pluginsuninstall-plugin)
-* [`testrigor plugins:uninstall PLUGIN...`](#testrigor-pluginsuninstall-plugin-1)
-* [`testrigor plugins:uninstall PLUGIN...`](#testrigor-pluginsuninstall-plugin-2)
-* [`testrigor plugins update`](#testrigor-plugins-update)
 * [`testrigor test-suite config`](#testrigor-test-suite-config)
 * [`testrigor test-suite run [TESTSUITEID]`](#testrigor-test-suite-run-testsuiteid)
 * [`testrigor test-suite validate-syntax [TESTSUITEID]`](#testrigor-test-suite-validate-syntax-testsuiteid)
@@ -108,7 +123,10 @@ Set your testRigor authentication token
 
 ```
 USAGE
-  $ testrigor authenticate
+  $ testrigor authenticate [--token <value>]
+
+FLAGS
+  --token=<value>  API authentication token to store, instead of prompting for it
 
 DESCRIPTION
   Set your testRigor authentication token
@@ -118,12 +136,16 @@ EXAMPLES
 
   Prompts for your API authentication token
 
+  $ testrigor authenticate --token YOUR_TOKEN
+
+  Sets the token without prompting (for CI and scripts)
+
   Use 'testrigor test-suite config' to set default test suite ID separately
 
   Config will be stored in ~/.testrigor/testrigor.yml
 ```
 
-_See code: [src/commands/authenticate.ts](https://github.com/TestRigor/testrigor-cli/blob/v1.0.1/src/commands/authenticate.ts)_
+_See code: [src/commands/authenticate.ts](https://github.com/TestRigor/testrigor-cli/blob/v2.0.0/src/commands/authenticate.ts)_
 
 ## `testrigor help [COMMANDS]`
 
@@ -131,10 +153,10 @@ Display help for testrigor.
 
 ```
 USAGE
-  $ testrigor help [COMMANDS] [-n]
+  $ testrigor help [COMMANDS...] [-n]
 
 ARGUMENTS
-  COMMANDS  Command to show help for.
+  [COMMANDS...]  Command to show help for.
 
 FLAGS
   -n, --nested-commands  Include all nested commands in the output.
@@ -145,253 +167,6 @@ DESCRIPTION
 
 _See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v5.2.20/src/commands/help.ts)_
 
-## `testrigor plugins`
-
-List installed plugins.
-
-```
-USAGE
-  $ testrigor plugins [--json] [--core]
-
-FLAGS
-  --core  Show core plugins.
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  List installed plugins.
-
-EXAMPLES
-  $ testrigor plugins
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/index.ts)_
-
-## `testrigor plugins:install PLUGIN...`
-
-Installs a plugin into the CLI.
-
-```
-USAGE
-  $ testrigor plugins:install PLUGIN...
-
-ARGUMENTS
-  PLUGIN  Plugin to install.
-
-FLAGS
-  -f, --force    Run yarn install with force flag.
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Installs a plugin into the CLI.
-  Can be installed from npm or a git url.
-
-  Installation of a user-installed plugin will override a core plugin.
-
-  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
-  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
-  the CLI without the need to patch and update the whole CLI.
-
-
-ALIASES
-  $ testrigor plugins add
-
-EXAMPLES
-  $ testrigor plugins:install myplugin 
-
-  $ testrigor plugins:install https://github.com/someuser/someplugin
-
-  $ testrigor plugins:install someuser/someplugin
-```
-
-## `testrigor plugins:inspect PLUGIN...`
-
-Displays installation properties of a plugin.
-
-```
-USAGE
-  $ testrigor plugins:inspect PLUGIN...
-
-ARGUMENTS
-  PLUGIN  [default: .] Plugin to inspect.
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-GLOBAL FLAGS
-  --json  Format output as json.
-
-DESCRIPTION
-  Displays installation properties of a plugin.
-
-EXAMPLES
-  $ testrigor plugins:inspect myplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/inspect.ts)_
-
-## `testrigor plugins:install PLUGIN...`
-
-Installs a plugin into the CLI.
-
-```
-USAGE
-  $ testrigor plugins:install PLUGIN...
-
-ARGUMENTS
-  PLUGIN  Plugin to install.
-
-FLAGS
-  -f, --force    Run yarn install with force flag.
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Installs a plugin into the CLI.
-  Can be installed from npm or a git url.
-
-  Installation of a user-installed plugin will override a core plugin.
-
-  e.g. If you have a core plugin that has a 'hello' command, installing a user-installed plugin with a 'hello' command
-  will override the core plugin implementation. This is useful if a user needs to update core plugin functionality in
-  the CLI without the need to patch and update the whole CLI.
-
-
-ALIASES
-  $ testrigor plugins add
-
-EXAMPLES
-  $ testrigor plugins:install myplugin 
-
-  $ testrigor plugins:install https://github.com/someuser/someplugin
-
-  $ testrigor plugins:install someuser/someplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/install.ts)_
-
-## `testrigor plugins:link PLUGIN`
-
-Links a plugin into the CLI for development.
-
-```
-USAGE
-  $ testrigor plugins:link PLUGIN
-
-ARGUMENTS
-  PATH  [default: .] path to plugin
-
-FLAGS
-  -h, --help      Show CLI help.
-  -v, --verbose
-  --[no-]install  Install dependencies after linking the plugin.
-
-DESCRIPTION
-  Links a plugin into the CLI for development.
-  Installation of a linked plugin will override a user-installed or core plugin.
-
-  e.g. If you have a user-installed or core plugin that has a 'hello' command, installing a linked plugin with a 'hello'
-  command will override the user-installed or core plugin implementation. This is useful for development work.
-
-
-EXAMPLES
-  $ testrigor plugins:link myplugin
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/link.ts)_
-
-## `testrigor plugins:uninstall PLUGIN...`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ testrigor plugins:uninstall PLUGIN...
-
-ARGUMENTS
-  PLUGIN  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ testrigor plugins unlink
-  $ testrigor plugins remove
-```
-
-## `testrigor plugins:uninstall PLUGIN...`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ testrigor plugins:uninstall PLUGIN...
-
-ARGUMENTS
-  PLUGIN  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ testrigor plugins unlink
-  $ testrigor plugins remove
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/uninstall.ts)_
-
-## `testrigor plugins:uninstall PLUGIN...`
-
-Removes a plugin from the CLI.
-
-```
-USAGE
-  $ testrigor plugins:uninstall PLUGIN...
-
-ARGUMENTS
-  PLUGIN  plugin to uninstall
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Removes a plugin from the CLI.
-
-ALIASES
-  $ testrigor plugins unlink
-  $ testrigor plugins remove
-```
-
-## `testrigor plugins update`
-
-Update installed plugins.
-
-```
-USAGE
-  $ testrigor plugins update [-h] [-v]
-
-FLAGS
-  -h, --help     Show CLI help.
-  -v, --verbose
-
-DESCRIPTION
-  Update installed plugins.
-```
-
-_See code: [@oclif/plugin-plugins](https://github.com/oclif/plugin-plugins/blob/v3.10.1/src/commands/plugins/update.ts)_
-
 ## `testrigor test-suite config`
 
 Configure test suite settings and default test suite ID
@@ -416,7 +191,7 @@ EXAMPLES
   $ testrigor test-suite config --delete
 ```
 
-_See code: [src/commands/test-suite/config.ts](https://github.com/TestRigor/testrigor-cli/blob/v1.0.1/src/commands/test-suite/config.ts)_
+_See code: [src/commands/test-suite/config.ts](https://github.com/TestRigor/testrigor-cli/blob/v2.0.0/src/commands/test-suite/config.ts)_
 
 ## `testrigor test-suite run [TESTSUITEID]`
 
@@ -427,54 +202,54 @@ USAGE
   $ testrigor test-suite run [TESTSUITEID] [--auth-token <value>] [-t <value>] [--min-port <value>] [--max-port
     <value>] [--verbose] [-w] [--branch <value> --commit <value>] [--localhost] [--url <value>]
     [--junit-report-save-path <value>] [--variables-path <value>] [--test-cases-path <value>] [--rules-path <value>]
-    [--settings-path <value>] [--local-test-nodes-path <value>] [--test-case-uuid <value>] [--auto-create-ai-rules]
-    [--explicit-mutations] [--labels <value>] [--excluded-labels <value>] [--base-url-web <value>] [--base-url-api
-    <value>] [--chrome-extension <value> | --file-path <value>] [--xray-execution-key <value>]
+    [--settings-path <value>] [--local-test-nodes-path <value>] [--test-case-uuid <value>...] [--auto-create-ai-rules]
+    [--explicit-mutations] [--labels <value>...] [--excluded-labels <value>...] [--base-url-web <value>] [--base-url-api
+    <value>] [--chrome-extension <value>... | --file-path <value>] [--xray-execution-key <value>]
 
 ARGUMENTS
-  TESTSUITEID  The test suite id (optional if set in config)
+  [TESTSUITEID]  The test suite id (optional if set in config)
 
 FLAGS
-  -w, --async                       Don't wait for the test suite to finish
-  --auto-create-ai-rules            Enable auto create AI based rules
-  --base-url-api=<value>            Base URL for API2 (e.g., https://api2.testrigor.com)
-  --base-url-web=<value>            Base URL for web interface (e.g., https://app.testrigor.com)
-  --branch=<value>                  The branch name
-  --chrome-extension=<value>...     Chrome extension: "name=EXT_NAME file=PATH_TO_CRX"
-  --commit=<value>                  The commit
-  --excluded-labels=<value>...      Not run tests of specific labels
-  --explicit-mutations              In cases where you are always using mutations, such as storing test cases in your
-                                    own repository, and you always send us the set of test cases you have through our
-                                    API you should send "--explicit-mutations"
-  --file-path=<value>               Path to the file stored locally. It will upload the new file to be used. File type
-                                    should be according to the file type accepted for the Test Suite type of testing. If
-                                    the parameter --url is used, this parameter will be ignored.
-  --junit-report-save-path=<value>  JUnit report save path
-  --labels=<value>...               Run tests of specific labels
-  --local-test-nodes-path=<value>   Path to a YAML or JSON file with local test nodes configuration
-  --localhost                       Localhost run (auto-detects web vs mobile)
-  --max-port=<value>                [default: 50000] Max port for tunnel
-  --min-port=<value>                [default: 40000] Min port for tunnel
-  --rules-path=<value>              Rules path
-  --settings-path=<value>           Settings path
-  --test-case-uuid=<value>...       Test case uuid (can be repeated). Requires --url (web) or --file-path (mobile app
-                                    upload).
-  --test-cases-path=<value>         Test cases files
-  --url=<value>                     The url
-  --variables-path=<value>          Variables path
-  --xray-execution-key=<value>      Reuse an existing Xray Cloud Test Execution by key (e.g. XR-123) instead of creating
-                                    a new one. Optional; leave blank to create a new execution.
+  -w, --async                           Don't wait for the test suite to finish
+      --auto-create-ai-rules            Enable auto create AI based rules
+      --base-url-api=<value>            Base URL for API2 (e.g., https://api2.testrigor.com)
+      --base-url-web=<value>            Base URL for web interface (e.g., https://app.testrigor.com)
+      --branch=<value>                  [env: TR_BRANCH] The branch name
+      --chrome-extension=<value>...     Chrome extension: "name=EXT_NAME file=PATH_TO_CRX"
+      --commit=<value>                  [env: TR_COMMIT] The commit
+      --excluded-labels=<value>...      Not run tests of specific labels
+      --explicit-mutations              In cases where you are always using mutations, such as storing test cases in
+                                        your own repository, and you always send us the set of test cases you have
+                                        through our API you should send "--explicit-mutations"
+      --file-path=<value>               Path to the file stored locally. It will upload the new file to be used. File
+                                        type should be according to the file type accepted for the Test Suite type of
+                                        testing. If the parameter --url is used, this parameter will be ignored.
+      --junit-report-save-path=<value>  JUnit report save path
+      --labels=<value>...               Run tests of specific labels
+      --local-test-nodes-path=<value>   Path to a YAML or JSON file with local test nodes configuration
+      --localhost                       Localhost run (auto-detects web vs mobile)
+      --max-port=<value>                [default: 50000] Max port for tunnel
+      --min-port=<value>                [default: 40000] Min port for tunnel
+      --rules-path=<value>              Rules path
+      --settings-path=<value>           Settings path
+      --test-case-uuid=<value>...       Test case uuid (can be repeated). Requires --url (web) or --file-path (mobile
+                                        app upload).
+      --test-cases-path=<value>         Test cases files
+      --url=<value>                     The url
+      --variables-path=<value>          Variables path
+      --xray-execution-key=<value>      Reuse an existing Xray Cloud Test Execution by key (e.g. XR-123) instead of
+                                        creating a new one. Optional; leave blank to create a new execution.
 
 GLOBAL FLAGS
-  -t, --token=<value>   Suite authentication token
-  --auth-token=<value>  Personal authentication token
-  --verbose             Verbose output
+  -t, --token=<value>       Suite authentication token
+      --auth-token=<value>  Personal authentication token
+      --verbose             Verbose output
 
 DESCRIPTION
   Run all tests of a Test Suite
 ```
 
-_See code: [src/commands/test-suite/run.ts](https://github.com/TestRigor/testrigor-cli/blob/v1.0.1/src/commands/test-suite/run.ts)_
+_See code: [src/commands/test-suite/run.ts](https://github.com/TestRigor/testrigor-cli/blob/v2.0.0/src/commands/test-suite/run.ts)_
 
 ## `testrigor test-suite validate-syntax [TESTSUITEID]`
 
@@ -487,7 +262,7 @@ USAGE
     [--explicit-mutations]
 
 ARGUMENTS
-  TESTSUITEID  The test suite id (optional if set in config)
+  [TESTSUITEID]  The test suite id (optional if set in config)
 
 FLAGS
   --base-url-api=<value>     Base URL for API2 (e.g., https://api2.testrigor.com)
@@ -500,9 +275,9 @@ FLAGS
   --test-cases-path=<value>  Test case files to validate (same glob format as `test-suite run --test-cases-path`)
 
 GLOBAL FLAGS
-  -t, --token=<value>   Suite authentication token
-  --auth-token=<value>  Personal authentication token
-  --verbose             Verbose output
+  -t, --token=<value>       Suite authentication token
+      --auth-token=<value>  Personal authentication token
+      --verbose             Verbose output
 
 DESCRIPTION
   Validate step syntax against a test suite's reusable rules, without running the steps
@@ -513,7 +288,7 @@ EXAMPLES
   $ testrigor test-suite validate-syntax <test-suite-id> --test-cases-path "test_cases/**/*.{yaml,txt}"
 ```
 
-_See code: [src/commands/test-suite/validate-syntax.ts](https://github.com/TestRigor/testrigor-cli/blob/v1.0.1/src/commands/test-suite/validate-syntax.ts)_
+_See code: [src/commands/test-suite/validate-syntax.ts](https://github.com/TestRigor/testrigor-cli/blob/v2.0.0/src/commands/test-suite/validate-syntax.ts)_
 <!-- commandsstop -->`, so this README currently stays unchanged.
 3. Check that the diff only touches the version fields, then build and test from the lockfile:
 

package/dist/commands/authenticate.d.ts

@@ -2,5 +2,19 @@ import { Command } from "@oclif/core";
 export default class Authenticate extends Command {
     static description: string;
     static examples: string[];
+    static flags: {
+        token: import("@oclif/core/lib/interfaces").OptionFlag<string | undefined, import("@oclif/core/lib/interfaces/parser").CustomOptions>;
+    };
     run(): Promise<void>;
+    /**
+     * Where the token comes from, in order: the --token flag, an interactive
+     * hidden prompt, or piped stdin.
+     *
+     * The hidden prompt is only usable on a TTY. Without one, @oclif/core falls
+     * back to `sh -c 'read -s ...'`, which fails on any system where /bin/sh is
+     * dash (the Debian and Ubuntu default) with "read: Illegal option -s" and
+     * then silently skips the setup.
+     */
+    private resolveToken;
+    private readStdin;
 }

package/dist/commands/authenticate.js

@@ -3,25 +3,19 @@ Object.defineProperty(exports, "__esModule", { value: true });
 const core_1 = require("@oclif/core");
 const core_2 = require("@oclif/core");
 const config_1 = require("../util/config");
+// Time to wait for a token on a piped stdin before giving up. Stdin that is
+// neither a TTY nor a closed/redirected stream would otherwise hang forever.
+const STDIN_TIMEOUT_MS = 5000;
 class Authenticate extends core_2.Command {
     async run() {
+        const { flags } = await this.parse(Authenticate);
+        // readConfig reports parse problems itself and falls back to an empty
+        // config, so it needs no wrapping here.
+        const config = await (0, config_1.readConfig)();
+        // Resolved outside the try below so that "no terminal to prompt on" is
+        // reported as itself, not as a failure to save the configuration.
+        const token = await this.resolveToken(flags.token, !!config.authToken);
         try {
-            // Load existing config (readConfig handles parse errors gracefully)
-            const config = await (0, config_1.readConfig)();
-            // Handle authentication token
-            let tokenPromptText;
-            if (config.authToken) {
-                tokenPromptText =
-                    "Enter your testRigor API token (press enter to remove)";
-            }
-            else {
-                tokenPromptText =
-                    "Enter your testRigor API token (press enter to skip)";
-            }
-            const token = await core_1.ux.prompt(tokenPromptText, {
-                type: "hide",
-                required: false,
-            });
             if (!token || token.trim() === "") {
                 if (config.authToken) {
                     delete config.authToken;
@@ -31,29 +25,96 @@ class Authenticate extends core_2.Command {
                 else {
                     core_1.ux.info("Authentication token setup skipped");
                 }
+                return;
+            }
+            config.authToken = token.trim();
+            await (0, config_1.writeConfig)(config);
+            core_1.ux.info("Authentication token successfully saved");
+            if (config.defaultTestSuiteId) {
+                core_1.ux.info("You can now use 'testrigor run' to run your default test suite");
             }
             else {
-                config.authToken = token.trim();
-                await (0, config_1.writeConfig)(config);
-                core_1.ux.info("Authentication token successfully saved");
-                if (config.defaultTestSuiteId) {
-                    core_1.ux.info("You can now use 'testrigor run' to run your default test suite");
-                }
-                else {
-                    core_1.ux.info("Use 'testrigor test-suite config --default TEST_SUITE_ID' to set your default test suite ID, then use 'testrigor run'");
-                }
+                core_1.ux.info("Use 'testrigor test-suite config --default TEST_SUITE_ID' to set your default test suite ID, then use 'testrigor run'");
             }
         }
         catch (error) {
             core_1.ux.error(`Failed to save configuration: ${error instanceof Error ? error.message : String(error)}`);
         }
     }
+    /**
+     * Where the token comes from, in order: the --token flag, an interactive
+     * hidden prompt, or piped stdin.
+     *
+     * The hidden prompt is only usable on a TTY. Without one, @oclif/core falls
+     * back to `sh -c 'read -s ...'`, which fails on any system where /bin/sh is
+     * dash (the Debian and Ubuntu default) with "read: Illegal option -s" and
+     * then silently skips the setup.
+     */
+    async resolveToken(flagToken, hasExistingToken) {
+        if (flagToken !== undefined) {
+            return flagToken;
+        }
+        if (process.stdin.isTTY) {
+            return core_1.ux.prompt(hasExistingToken
+                ? "Enter your testRigor API token (press enter to remove)"
+                : "Enter your testRigor API token (press enter to skip)", { type: "hide", required: false });
+        }
+        const piped = await this.readStdin();
+        if (piped) {
+            return piped;
+        }
+        this.error("No interactive terminal available to prompt for a token.\n" +
+            "Provide it another way:\n" +
+            "  testrigor authenticate --token YOUR_TOKEN\n" +
+            "  echo YOUR_TOKEN | testrigor authenticate\n" +
+            "Or skip this command and set the TESTRIGOR_API_KEY environment variable instead.");
+    }
+    readStdin() {
+        return new Promise((resolve) => {
+            let data = "";
+            // resolve() past the first call is a no-op, so no "settled" guard is
+            // needed for whichever of the timeout or the stream gets there first.
+            const cleanup = () => {
+                process.stdin.removeAllListeners("data");
+                process.stdin.pause();
+            };
+            const timer = setTimeout(() => {
+                cleanup();
+                resolve("");
+            }, STDIN_TIMEOUT_MS);
+            const finish = () => {
+                clearTimeout(timer);
+                cleanup();
+                resolve(data.trim());
+            };
+            process.stdin.setEncoding("utf8");
+            process.stdin.on("data", (chunk) => {
+                data += chunk;
+                // A token is a single line; stop as soon as one arrives.
+                const newlineIndex = data.indexOf("\n");
+                if (newlineIndex !== -1) {
+                    data = data.slice(0, newlineIndex);
+                    finish();
+                }
+            });
+            process.stdin.once("end", finish);
+            process.stdin.once("error", finish);
+            process.stdin.resume();
+        });
+    }
 }
 Authenticate.description = "Set your testRigor authentication token";
 Authenticate.examples = [
     "testrigor authenticate",
     "Prompts for your API authentication token",
+    "testrigor authenticate --token YOUR_TOKEN",
+    "Sets the token without prompting (for CI and scripts)",
     "Use 'testrigor test-suite config' to set default test suite ID separately",
     "Config will be stored in ~/.testrigor/testrigor.yml",
 ];
+Authenticate.flags = {
+    token: core_2.Flags.string({
+        description: "API authentication token to store, instead of prompting for it",
+    }),
+};
 exports.default = Authenticate;