@cargo-ai/cli 1.0.74 → 1.0.75

package/build/commands/connection/integration.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"integration.d.ts","sourceRoot":"","sources":["../../../src/commands/connection/integration.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEzC,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,cAAc,CAAC;AAGxC,wBAAgB,2BAA2B,CACzC,MAAM,EAAE,OAAO,EACf,MAAM,EAAE,MAAM,GAAG,GAChB,IAAI,CAuGN"}
+{"version":3,"file":"integration.d.ts","sourceRoot":"","sources":["../../../src/commands/connection/integration.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEzC,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,cAAc,CAAC;AAGxC,wBAAgB,2BAA2B,CACzC,MAAM,EAAE,OAAO,EACf,MAAM,EAAE,MAAM,GAAG,GAChB,IAAI,CAwHN"}

package/build/commands/connection/integration.js

@@ -6,11 +6,12 @@ export function registerIntegrationCommands(parent, getApi) {
     integration
         .command("list")
         .description("List all integrations")
-        .option("--category <engagement|marketing|sales|finance|analytics|freeform|success|support|enrichment|storage|custom>", "Filter by category")
+        .option("--category <category>", "Filter by category (string)")
         .option("--slugs <list>", "Filter by integration slugs (comma-separated strings)")
         .option("--search <search>", "Search by name, case-insensitive (string)")
         .option("--has-actions <bool>", 'Filter by presence of actions (string: "true" or "false")')
         .option("--has-extractors <bool>", 'Filter by presence of extractors (string: "true" or "false")')
+        .option("--summary", "Only slug, name, and category — drops actions/schemas so pickers stay under the palette capture limit")
         .action(async (opts) => {
         const api = getApi();
         const result = await handleApiCall(() => api.connection.integration.list({
@@ -33,6 +34,19 @@ export function registerIntegrationCommands(parent, getApi) {
                     ? false
                     : undefined,
         }));
+        // Full `integration.list` is multi-megabyte (every action schema). The
+        // palette captures at most 2MB; without this trim, JSON truncates and
+        // the picker silently falls back to free text.
+        if (opts.summary === true) {
+            outputJson({
+                integrations: result.integrations.map((integration) => ({
+                    slug: integration.slug,
+                    name: integration.name,
+                    category: integration.category,
+                })),
+            });
+            return;
+        }
         outputJson(result);
     });
     integration

package/build/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { createRequire } from "node:module";
-import { availableCodingAgents, BRAND, canRunPalette, cdkProjectRoot, declareSources, fetchCreditsLeft, fetchWorkspaceName, formatWorkspaceSuffix, isInteractive, printSetupIssues, registerCommands as registerCdkCommands, runPalette, SessionExpiredError, } from "@cargo-ai/cdk/cli";
+import { availableCodingAgents, BRAND, canRunPalette, cdkProjectDir, cdkProjectRoot, declareSources, fetchCreditsLeft, fetchWorkspaceName, formatWorkspaceSuffix, isInteractive, printSetupIssues, registerCommands as registerCdkCommands, runPalette, SessionExpiredError, } from "@cargo-ai/cdk/cli";
 import { Command } from "commander";
 import { AGENT_SKILLS_HINT } from "./agentSkills.js";
 import { createApi } from "./api.js";
@@ -125,10 +125,12 @@ const getApi = () => {
 };
 // Where the palette finds answers for an option that wants an id. Keyed by the
 // flag, because `--model-uuid` asks the same question in all 28 places it
-// appears; these six entries cover the 84 uuid options this CLI declares.
+// appears; the uuid entries cover the 84 uuid options this CLI declares, and
+// the integration-slug entries cover every catalog-slug flag the same way.
 //
-// Nobody knows a uuid. Every one of these replaces a field you would otherwise
-// have to leave the palette to fill.
+// Nobody knows a uuid — and few people remember every integration slug. Every
+// one of these replaces a field you would otherwise have to leave the palette
+// to fill.
 declareSources({
     // A workflow row carries a uuid, two timestamps and a toolUuid — nothing to
     // choose between. The plays and tools that own those workflows carry a name
@@ -173,6 +175,35 @@ declareSources({
     "--segment-uuid": [
         { argv: ["segmentation", "segment", "list"], value: "uuid", label: "name" },
     ],
+    // Integration slugs are the catalog names (`hubspot`, `linkedin`) — same
+    // question for `--integration-slug`, the shorter `--integration` filters,
+    // and span filters keyed on the node. `--summary` is required: the full
+    // list is multi-megabyte and exceeds the palette's capture limit, which
+    // truncates JSON and falls back to a free-text prompt.
+    "--integration-slug": [
+        {
+            argv: ["connection", "integration", "list", "--summary"],
+            value: "slug",
+            label: "name",
+            hint: "slug",
+        },
+    ],
+    "--integration": [
+        {
+            argv: ["connection", "integration", "list", "--summary"],
+            value: "slug",
+            label: "name",
+            hint: "slug",
+        },
+    ],
+    "--node-integration-slug": [
+        {
+            argv: ["connection", "integration", "list", "--summary"],
+            value: "slug",
+            label: "name",
+            hint: "slug",
+        },
+    ],
 });
 const binPath = process.argv[1] === undefined ? "cargo-ai" : process.argv[1];
 // First, so it is the first row of the palette: for someone signed in, this is
@@ -231,11 +262,23 @@ async function openPalette(startPath) {
     // Re-read after each command: signing in or out from inside the palette
     // changes both what the setup line says and which rows are worth pinning.
     // The cwd is re-tested too — a command can create a project in it.
-    const rebuildLayout = () => buildPaletteLayout({
-        signedIn: isSignedIn(),
-        agents,
-        cdkProjectRoot: cdkProjectRoot(process.cwd()),
-    });
+    const rebuildLayout = () => {
+        // Read once: a layout describing two different directories could offer to
+        // deploy one and name the other.
+        const cwd = process.cwd();
+        const root = cdkProjectRoot(cwd);
+        return buildPaletteLayout({
+            signedIn: isSignedIn(),
+            agents,
+            cdkProjectRoot: root,
+            // Resolved from the root, never the cwd. `cdkProjectDir` looks *down* for
+            // `infra/` rather than walking up, and a scaffolded `infra/` carries no
+            // package.json to be recognised by — so asked from inside one it answers
+            // undefined, and `deploy` would fall back to the root it must not use.
+            cdkProjectDir: root === undefined ? undefined : cdkProjectDir(root),
+            cwd,
+        });
+    };
     await runPalette({
         program,
         binPath,

package/build/paletteLayout.d.ts

@@ -4,6 +4,22 @@ export type PaletteLayoutInput = {
     agents: readonly CodingAgent[];
     /** The CDK repo root the palette is standing in, or undefined when none. */
     cdkProjectRoot: string | undefined;
+    /**
+     * The directory holding the CDK project — `infra/` for a scaffolded repo, or
+     * the same as `cdkProjectRoot` for a hand-rolled layout. Commands that load
+     * the resource tree and state (`cdk deploy`) need this, not the repo root.
+     *
+     * Resolve it from `cdkProjectRoot` rather than from `cwd`: `cdkProjectDir`
+     * looks down for `infra/` instead of walking up, so from inside one it
+     * answers undefined.
+     */
+    cdkProjectDir: string | undefined;
+    /**
+     * Where the palette is standing. The project rows are resolved by walking
+     * *up* from here, so this is what says whether they point at the directory
+     * on screen or one somewhere above it.
+     */
+    cwd: string;
 };
 export declare function buildPaletteLayout(input: PaletteLayoutInput): PaletteLayout;
 /**

package/build/paletteLayout.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"paletteLayout.d.ts","sourceRoot":"","sources":["../src/paletteLayout.ts"],"names":[],"mappings":"AAUA,OAAO,KAAK,EAAE,WAAW,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,mBAAmB,CAAC;AAsE/E,MAAM,MAAM,kBAAkB,GAAG;IAC/B,QAAQ,EAAE,OAAO,CAAC;IAClB,MAAM,EAAE,SAAS,WAAW,EAAE,CAAC;IAC/B,4EAA4E;IAC5E,cAAc,EAAE,MAAM,GAAG,SAAS,CAAC;CACpC,CAAC;AAEF,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,kBAAkB,GAAG,aAAa,CAM3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,EAAE,CA+CjE"}
+{"version":3,"file":"paletteLayout.d.ts","sourceRoot":"","sources":["../src/paletteLayout.ts"],"names":[],"mappings":"AAYA,OAAO,KAAK,EAAE,WAAW,EAAE,aAAa,EAAE,SAAS,EAAE,MAAM,mBAAmB,CAAC;AAwE/E,MAAM,MAAM,kBAAkB,GAAG;IAC/B,QAAQ,EAAE,OAAO,CAAC;IAClB,MAAM,EAAE,SAAS,WAAW,EAAE,CAAC;IAC/B,4EAA4E;IAC5E,cAAc,EAAE,MAAM,GAAG,SAAS,CAAC;IACnC;;;;;;;;OAQG;IACH,aAAa,EAAE,MAAM,GAAG,SAAS,CAAC;IAClC;;;;OAIG;IACH,GAAG,EAAE,MAAM,CAAC;CACb,CAAC;AAEF,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,kBAAkB,GAAG,aAAa,CAM3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,EAAE,CA4CjE"}

package/build/paletteLayout.js

@@ -7,16 +7,19 @@
 // most often wants, a coding agent briefed on their workspace, two screens
 // down behind `start`. This is the missing opinion, kept in one place and as
 // data, so it can be read and tested rather than inferred from a menu.
+import { basename, relative, resolve } from "node:path";
 /** Pinned row values. The leading space keeps them out of the command namespace. */
 const SIGN_IN = " sign-in";
 const DEMO = " demo";
 const CODE = " code";
-const ADD_COOKBOOK = " add-cookbook";
+const ADD = " add";
+const DEPLOY = " deploy";
 /**
  * `start` runs most of these; the pinned row is the shortcut to one of them.
- * The exception is "Add a cookbook", which runs `cdk add` directly: it is not
- * a `start` destination, because it needs neither the sign-in step nor a
- * choice of where to carry on — you are already in the project.
+ * The exceptions are "Add" and "Deploy", which run `cdk add` and `cdk deploy`
+ * directly: neither is a `start` destination, because neither needs the sign-in
+ * step nor a choice of where to carry on — you are already in the project. Bare
+ * `cdk add` asks connector vs cookbook, then shows that kind's list.
  */
 const ENTRANCE = "start";
 /**
@@ -95,24 +98,27 @@ export function pinnedRows(input) {
             },
         ];
     }
-    // Inside a CDK project, "Add a cookbook" is more useful than "Set up as
-    // code" — the project already exists. Outside, scaffold one.
-    const cdkRow = input.cdkProjectRoot !== undefined
-        ? {
-            value: ADD_COOKBOOK,
-            label: "Add a cookbook",
-            hint: "install a worked pipeline into this project",
-            // `--dir` because `cdk add` refuses a directory with no
-            // package.json, and the palette is as often open in `infra/` — where
-            // the scaffold's README sends people — as at the root.
-            argv: ["cdk", "add", "--dir", input.cdkProjectRoot],
-        }
-        : {
-            value: CODE,
-            label: "Set up as code",
-            hint: "scaffold a CDK project",
-            argv: [ENTRANCE, "--continue", "code"],
-        };
+    // Inside a CDK project the rows are the loop somebody is actually in — add a
+    // resource, deploy it — and the guided demo is not part of it: it is the tour
+    // for a workspace you have not built yet, and this one is open on screen.
+    // Outside, there is no project to add to or deploy, so offer the tour and the
+    // scaffold instead.
+    const projectRows = input.cdkProjectRoot !== undefined
+        ? cdkRows(input.cdkProjectRoot, input.cdkProjectDir, input.cwd)
+        : [
+            {
+                value: DEMO,
+                label: "Guided demo",
+                hint: "companies, then the people, for your ICP",
+                argv: [ENTRANCE, "--continue", "demo"],
+            },
+            {
+                value: CODE,
+                label: "Set up as code",
+                hint: "scaffold a CDK project",
+                argv: [ENTRANCE, "--continue", "code"],
+            },
+        ];
     return [
         ...input.agents.map((agent) => ({
             value: ` agent:${agent.bin}`,
@@ -120,12 +126,49 @@ export function pinnedRows(input) {
             hint: "briefed on this workspace",
             argv: [ENTRANCE, "--continue", agent.bin],
         })),
+        ...projectRows,
+    ];
+}
+/** The two rows for a palette standing in the CDK project rooted at `root`. */
+function cdkRows(root, projectDir, cwd) {
+    // `cdk deploy` loads the resource tree and `cargo.state.json` from the
+    // directory it runs in, so it needs the CDK project — `infra/` in a
+    // scaffolded repo — where `add` takes the root and resolves that itself.
+    const target = projectDir !== undefined ? projectDir : root;
+    return [
+        {
+            value: ADD,
+            label: "Add",
+            hint: "a connector or a cookbook into this project",
+            // `--dir` because `cdk add` refuses a directory with no package.json,
+            // and the palette is as often open in `infra/` — where the scaffold's
+            // README sends people — as at the root.
+            argv: ["cdk", "add", "--dir", root],
+        },
         {
-            value: DEMO,
-            label: "Guided demo",
-            hint: "companies, then the people, for your ICP",
-            argv: [ENTRANCE, "--continue", "demo"],
+            value: DEPLOY,
+            label: "Deploy",
+            // Name the directory whenever it is not the one on screen. The project is
+            // found by walking *up*, so this row can target a project the cwd gives no
+            // sign of — and it mutates a live workspace, which in a repo holding more
+            // than one project is worth saying out loud before it is picked.
+            hint: resolve(target) === resolve(cwd)
+                ? "this project to your workspace"
+                : `${projectName(target, root)}/ to your workspace`,
+            // No `--yes`: `deploy` shows the plan and asks, which is the point of
+            // reaching it from a menu.
+            argv: ["cdk", "deploy", "--dir", target],
         },
-        cdkRow,
     ];
 }
+/**
+ * A short name for the CDK project directory: where it sits inside the repo
+ * (`infra`), or the repo's own directory name when it *is* the repo root.
+ *
+ * `relative` answers "" for two equal paths — the hand-rolled layout that keeps
+ * its resources at the root — and "" is not a name anybody can read.
+ */
+function projectName(dir, root) {
+    const within = relative(root, dir);
+    return within === "" ? basename(root) : within;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cargo-ai/cli",
-  "version": "1.0.74",
+  "version": "1.0.75",
   "private": false,
   "license": "UNLICENSED",
   "homepage": "https://getcargo.ai",
@@ -66,7 +66,7 @@
   "dependencies": {
     "@cargo-ai/api": "^1.0.71",
     "@cargo-ai/app-sdk": "^1.0.9",
-    "@cargo-ai/cdk": "^1.0.60",
+    "@cargo-ai/cdk": "^1.0.61",
     "@cargo-ai/types": "^1.0.66",
     "@cargo-ai/worker-sdk": "^1.0.17",
     "@modelcontextprotocol/sdk": "1.29.0",