@withone/cli 2.10.0 → 2.11.0

package/README.md

@@ -529,14 +529,14 @@ Commit `.agents/skills/one-connect` and the agent links so your team's agents sh
 
 ### `one connect`
 
-Create and update a [One Connect](https://www.npmjs.com/package/@withone/connect) app from `one.connect.ts`, typed by `defineConnectApp` from `@withone/connect/config` (0.19.0 or later).
+Create and update a [One Connect](https://www.npmjs.com/package/@withone/connect) app from `one.connect.ts`, typed by `defineConnectApp` from `@withone/connect/config` (0.20.0 or later).
 
 ```bash
 one connect types     # writes one-connect-env.d.ts: tool slugs and action names autocomplete
 one connect create    # approve the app in the browser; re-run to review and apply changes
 ```
 
-`one connect create` opens a setup page in your signed-in browser, where you review the app (or, on a re-run, its new version) and approve it; nothing is created or changed with your API key. A new app's client secret and connect key are made there and shown once, so they never pass through the terminal. Once you approve, the CLI writes `ONE_CLIENT_ID`, `ONE_PERMISSION_SET` and `ONE_REDIRECT_URI` to `.env.local` (or `.env`). Each tool in `ask` takes `access`: `read-only`, `read-write`, `full-access`, or `custom` with `actions`, named as `one connect types` wrote them or by id from `one actions find <platform> "<what it does>" --no-knowledge`. Options: `--config <file>`, `--env-file <file>`, `--no-open`. Install `@withone/connect` (0.19.0 or later) in the project first. A `.ts` config needs Node 22.18 or later; on older Node use `one.connect.mjs`.
+`one connect create` opens a setup page in your signed-in browser, where you review the app (or, on a re-run, its new version) and approve it; nothing is created or changed with your API key. A new app's client secret and connect key are made there and shown once, so they never pass through the terminal. Once you approve, the CLI writes `ONE_CLIENT_ID`, `ONE_REDIRECT_URI` and, for a list of tools, `ONE_PERMISSION_SET` to `.env.local` (or `.env`). `ask` is required: either the tools, where each takes `access` (`read-only`, `read-write`, `full-access`, or `custom` with `actions`, named as `one connect types` wrote them or by id from `one actions find <platform> "<what it does>" --no-knowledge`), or `"everything"`, where users see every connection they have and can connect any other app. An app switched to `"everything"` loses its ask, and the CLI removes `ONE_PERMISSION_SET` from the env file. Options: `--config <file>`, `--env-file <file>`, `--no-open`. Install `@withone/connect` (0.20.0 or later) in the project first. A `.ts` config needs Node 22.18 or later; on older Node use `one.connect.mjs`.
 
 ### `one guide [topic]`
 

package/dist/index.js

@@ -6015,6 +6015,9 @@ import zlib from "zlib";
 import { pathToFileURL } from "url";
 var CONFIG_FILES = ["one.connect.ts", "one.connect.mts", "one.connect.mjs", "one.connect.js"];
 var TYPES_FILE = "one-connect-env.d.ts";
+function askedTools(config2) {
+  return config2.ask === "everything" ? [] : Object.entries(config2.ask ?? {});
+}
 var ACCESS_METHODS = {
   "read-only": ["GET"],
   "read-write": ["GET", "POST", "PUT", "PATCH"],
@@ -6077,7 +6080,18 @@ function validateConfig(value) {
       if (!HEX_COLOR.test(String(v.branding[key] ?? ""))) errors.push(`\`branding.${key}\` must be a #RRGGBB colour.`);
     }
   }
-  for (const [tool, ask] of Object.entries(v.ask ?? {})) {
+  const asked = v.ask;
+  if (asked === void 0) {
+    errors.push('`ask` is required: name the tools the app asks for, or write `ask: "everything"`.');
+  } else if (typeof asked === "string") {
+    if (asked !== "everything") errors.push(`\`ask\` is "${asked}"; it must be a map of tools or "everything".`);
+  } else if (!asked || typeof asked !== "object" || Array.isArray(asked)) {
+    errors.push('`ask` must be a map of tools or "everything".');
+  } else if (Object.keys(asked).length === 0) {
+    errors.push('`ask` names no tools. Name at least one, or write `ask: "everything"`.');
+  }
+  const tools = asked && typeof asked === "object" && !Array.isArray(asked) ? Object.entries(asked) : [];
+  for (const [tool, ask] of tools) {
     const access = ask?.access;
     if (access === "custom") {
       const actions2 = ask.actions;
@@ -6134,7 +6148,11 @@ function clientFields(config2) {
   return fields;
 }
 function buildHandoff(config2, rules) {
-  return { v: 1, app: clientFields(config2), ask: rules.length > 0 ? rules : null };
+  return {
+    v: 2,
+    app: clientFields(config2),
+    ask: config2.ask === "everything" ? { kind: "everything" } : { kind: "tools", rules }
+  };
 }
 function encodeHandoff(handoff) {
   return zlib.deflateRawSync(Buffer.from(JSON.stringify(handoff), "utf8"), { level: 9 }).toString("base64url");
@@ -6165,6 +6183,10 @@ function upsertEnv(text5, values) {
   return `${next}${separator}${appended.join("\n")}
 `;
 }
+function removeEnvKeys(text5, keys) {
+  return keys.reduce((next, key) => next.replace(new RegExp(`^${key}=.*(?:\r?
+|$)`, "m"), ""), text5);
+}
 function renderTypes(tools, actionsByTool) {
   const literal = (value) => JSON.stringify(value);
   const union = (values) => values.length > 0 ? values.map(literal).join(" | ") : "never";
@@ -6214,7 +6236,7 @@ function message(error2) {
   return error2 instanceof Error ? error2.message : String(error2);
 }
 async function buildRules(api, config2) {
-  const asked = Object.entries(config2.ask ?? {});
+  const asked = askedTools(config2);
   if (asked.length === 0) return [];
   const platforms = await api.listPlatforms();
   const idBySlug = new Map(platforms.map((p9) => [p9.platform, p9.id]));
@@ -6302,19 +6324,21 @@ async function connectCreateCommand(options) {
     if (outcome.kind === "cancelled") error("Cancelled in the browser. Nothing was changed.");
     if (outcome.kind === "failed") error(`The setup page reported: ${outcome.reason}`);
     const created = outcome.outcome === "created";
+    const asksForEverything = config2.ask === "everything";
     fs6.writeFileSync(
       envFile,
-      upsertEnv(envText, {
+      upsertEnv(asksForEverything ? removeEnvKeys(envText, ["ONE_PERMISSION_SET"]) : envText, {
         ONE_CLIENT_ID: outcome.clientId,
         ONE_REDIRECT_URI: config2.redirectUris[0],
-        ...outcome.permissionSetId ? { ONE_PERMISSION_SET: outcome.permissionSetId } : {},
+        ...!asksForEverything && outcome.permissionSetId ? { ONE_PERMISSION_SET: outcome.permissionSetId } : {},
         ...created ? { ONE_CLIENT_SECRET: null, ONE_CONNECT_KEY: null } : {}
       })
     );
     const result = {
       outcome: outcome.outcome,
       clientId: outcome.clientId,
-      permissionSetId: outcome.permissionSetId,
+      permissionSetId: asksForEverything ? null : outcome.permissionSetId,
+      asksForEverything,
       redirectUris: config2.redirectUris,
       envFile: path6.relative(cwd, envFile) || envFile
     };
@@ -6327,7 +6351,8 @@ async function connectCreateCommand(options) {
     );
     console.log();
     console.log(`  ${pc10.dim("Client ID:")}       ${outcome.clientId}`);
-    if (outcome.permissionSetId) console.log(`  ${pc10.dim("Permission set:")}  ${outcome.permissionSetId}`);
+    if (asksForEverything) console.log(`  ${pc10.dim("Asks for:")}        everything the user has connected`);
+    else if (outcome.permissionSetId) console.log(`  ${pc10.dim("Permission set:")}  ${outcome.permissionSetId}`);
     console.log(`  ${pc10.dim("Wrote")}            ${result.envFile}`);
     if (created) {
       console.log(`  ${pc10.dim("The two secrets came from the browser page, never through here.")}`);
@@ -6349,7 +6374,7 @@ async function connectTypesCommand(options) {
   try {
     const file = findConfigFile(cwd, options.config);
     const config2 = file ? validateConfig(await loadConfigFile(file)) : null;
-    const tools = Object.keys(config2 && "config" in config2 ? config2.config.ask ?? {} : {});
+    const tools = config2 && "config" in config2 ? askedTools(config2.config).map(([slug]) => slug) : [];
     const platforms = await api.listPlatforms();
     const known = new Set(platforms.map((p9) => p9.platform));
     const actionsByTool = {};
@@ -11380,7 +11405,7 @@ one --agent relay deliveries --endpoint-id <id>                 # Check delivery
 - Use \`actions find\` (and \`actions load\` for more) to learn both the incoming payload shape AND the destination API shape before building templates
 
 ### One Connect apps \u2014 created from \`one.connect.ts\`
-\`one connect create\` reads \`one.connect.ts\`, typed by \`defineConnectApp\` from \`@withone/connect/config\` (install \`@withone/connect\` 0.19.0 or later in the project first), and opens a setup page where the human reviews the app (or, once .env holds its \`ONE_CLIENT_ID\`, its new version) and approves it with their dashboard session; an API key never creates or changes a Connect app. A new app's client secret and connect key are made and shown there once; the CLI never receives them. It waits up to 10 minutes, then writes \`ONE_CLIENT_ID\`, \`ONE_PERMISSION_SET\` and \`ONE_REDIRECT_URI\` to the env file. \`one connect types\` writes \`one-connect-env.d.ts\` so tool slugs and action names autocomplete. Each tool's \`access\` is \`read-only\`, \`read-write\`, \`full-access\`, or \`custom\` with \`actions\` (names, or ids from \`actions find\`).
+\`one connect create\` reads \`one.connect.ts\`, typed by \`defineConnectApp\` from \`@withone/connect/config\` (install \`@withone/connect\` 0.20.0 or later in the project first), and opens a setup page where the human reviews the app (or, once .env holds its \`ONE_CLIENT_ID\`, its new version) and approves it with their dashboard session; an API key never creates or changes a Connect app. A new app's client secret and connect key are made and shown there once; the CLI never receives them. It waits up to 10 minutes, then writes \`ONE_CLIENT_ID\`, \`ONE_REDIRECT_URI\` and, for a list of tools, \`ONE_PERMISSION_SET\` to the env file. \`one connect types\` writes \`one-connect-env.d.ts\` so tool slugs and action names autocomplete. \`ask\` is required: the tools, each with \`access\` \`read-only\`, \`read-write\`, \`full-access\`, or \`custom\` with \`actions\` (names, or ids from \`actions find\`), or \`"everything"\`, which asks for every connection the user has and removes \`ONE_PERMISSION_SET\` from the env file.
 
 ### 4. Memory + Sync \u2014 Unified store with hybrid FTS + semantic search
 One ships a local memory store (a real Postgres process bootstrapped on demand via the bundled \`embedded-postgres\` plugin, with a \`postgres\` plugin for remote/self-hosted) that backs both user-authored notes (\`one mem add\`) and synced platform data (\`one sync run\`). Auto-initializes on first use \u2014 no separate install step. Run \`one guide memory\` and \`one guide sync\` for the full references.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@withone/cli",
-  "version": "2.10.0",
+  "version": "2.11.0",
   "description": "CLI for managing One",
   "type": "module",
   "files": [

package/skills/one/SKILL.md

@@ -377,10 +377,10 @@ To create the Connect app itself without the dashboard, install `@withone/connec
 
 ```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
+one --agent connect create     # the human approves it in the browser; then writes ONE_CLIENT_ID, ONE_REDIRECT_URI and (for a list of tools) ONE_PERMISSION_SET 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.
+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. `ask` is required: the tools the app asks for, or `"everything"` (users see every connection they have and can connect any other app; the CLI then removes `ONE_PERMISSION_SET` from the env file).
 
 ## Adding New Connections