@withone/cli 2.9.1 → 2.10.0

package/dist/node-check.d.ts

@@ -0,0 +1,36 @@
+/**
+ * Refuses to run on a Node.js that still trusts the compromised eMudhra
+ * intermediate CAs (October 2026, RUSTSEC-2026-0381).
+ *
+ * Eight eMudhra/emSign intermediates were created with 8-bit private keys, so
+ * anyone can compute them and sign a certificate for any domain, including
+ * api.withone.ai. Node.js blocks them inside the TLS handshake from 22.23.4,
+ * 24.22.1 and 26.12.1 (nodejs/node#66871). On any older Node, a network
+ * attacker can intercept the CLI's traffic and the user's API key, and nothing
+ * in userland can block the intermediates the way Node's fix does.
+ *
+ * Built as its own entry so bin/cli.js can run it before loading the rest of
+ * the CLI, and before any connection opens.
+ */
+declare const REQUIRED_NODE = "22.23.4+, 24.22.1+ or 26.12.1+";
+declare const REQUIRED_NODE_RANGE = "^22.23.4 || ^24.22.1 || >=26.12.1";
+/** Set to 1 to run on an unpatched Node anyway, with a warning on every run. */
+declare const ALLOW_UNPATCHED_ENV = "ONE_ALLOW_UNPATCHED_NODE";
+/** True when this Node version rejects chains through the compromised eMudhra intermediates. */
+declare function nodeHasTlsFix(version?: string): boolean;
+/**
+ * The command that updates Node for however it was installed, judged from the
+ * path of the running binary. A line that got the fix stays on its line; any
+ * other moves to the recommended one.
+ */
+declare function upgradeCommand(version?: string, execPath?: string): string;
+declare function unpatchedNodeMessage(version?: string): string;
+/**
+ * Exits with an error on an unpatched Node; returns on a patched one. In agent
+ * mode the error is JSON on stdout with a code agents can act on. With
+ * ONE_ALLOW_UNPATCHED_NODE=1 it warns and returns instead (silently in agent
+ * mode, where stderr would corrupt the JSON for harnesses that merge streams).
+ */
+declare function requirePatchedNode(): void;
+
+export { ALLOW_UNPATCHED_ENV, REQUIRED_NODE, REQUIRED_NODE_RANGE, nodeHasTlsFix, requirePatchedNode, unpatchedNodeMessage, upgradeCommand };

package/dist/node-check.js

@@ -0,0 +1,18 @@
+import {
+  ALLOW_UNPATCHED_ENV,
+  REQUIRED_NODE,
+  REQUIRED_NODE_RANGE,
+  nodeHasTlsFix,
+  requirePatchedNode,
+  unpatchedNodeMessage,
+  upgradeCommand
+} from "./chunk-FYTWXGPJ.js";
+export {
+  ALLOW_UNPATCHED_ENV,
+  REQUIRED_NODE,
+  REQUIRED_NODE_RANGE,
+  nodeHasTlsFix,
+  requirePatchedNode,
+  unpatchedNodeMessage,
+  upgradeCommand
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withone/cli",
-  "version": "2.9.1",
+  "version": "2.10.0",
   "description": "CLI for managing One",
   "type": "module",
   "files": [
@@ -52,6 +52,6 @@
     "url": "https://github.com/withoneai/cli"
   },
   "engines": {
-    "node": ">=18"
+    "node": "^22.23.4 || ^24.22.1 || >=26.12.1"
   }
 }

package/skills/one/SKILL.md

@@ -171,6 +171,8 @@ All segments are validated before any execution. Failed actions don't block othe
 
 All errors return JSON: `{"error": "message"}`. Parse output as JSON and check for the `error` key.
 
+The CLI requires Node.js 22.23.4+, 24.22.1+ or 26.12.1+ (older Node trusts the compromised eMudhra CA certificates). On an older Node every command exits 1 with `"code": "NODE_UPGRADE_REQUIRED"` and an `upgrade` field holding the command for the user's setup. Don't retry: show the user that command and ask them to update Node.js.
+
 ## Important Rules
 
 - Always use `--agent` flag for structured JSON output
@@ -371,6 +373,15 @@ one --agent skills add connect      # from the @withone/connect version the app
 
 It lands in `.agents/skills/one-connect` (and `.claude/skills/one-connect`). The result's `next` array says what to do; the skill covers the button, the two routes, key mode vs token mode, and calling One with the grant. Never ask the user to paste the client secret or connect key into chat.
 
+To create the Connect app itself without the dashboard, install `@withone/connect` in the project (0.19.0 or later; the file imports it from there, not from the CLI), write `one.connect.ts` with `defineConnectApp` from `@withone/connect/config` (name, `redirectUris`, `ask` per tool with `access`: `read-only`, `read-write`, `full-access`, or `custom` with `actions`), then:
+
+```bash
+one --agent connect types      # tool slugs and action names autocomplete in one.connect.ts
+one --agent connect create     # the human approves it in the browser; then writes ONE_CLIENT_ID, ONE_PERMISSION_SET, ONE_REDIRECT_URI to .env
+```
+
+It opens a setup page in the human's browser and waits up to 10 minutes, so run it in the background or with a long timeout; the link is printed to stderr at once, so pass it on if no browser opened. The human reviews the app (or, on a re-run, its new version) and approves it with their dashboard session: an API key never creates or changes a Connect app. For a new app the page also makes `ONE_CLIENT_SECRET` and `ONE_CONNECT_KEY` and shows them once; tell the human to copy them into the env file the result names. The CLI never receives either secret. Run `connect create` again after editing the file to update the same app.
+
 ## Adding New Connections
 
 If the user needs a platform that isn't connected yet, tell them to run: