@cargo-ai/cli 1.0.115 → 1.0.117

package/README.md

@@ -69,7 +69,7 @@ cargo-ai login --token <your-api-token>
 
 `--email`, `--oauth` and `--agentid` all create the account if it does not exist yet, so there is no separate sign-up command.
 
-`--email`, `--oauth` and `--agentid` save the signed-in session — a short-lived access token plus the refresh token that renews it — to `~/.config/cargo-ai/credentials.json` (file mode `0600`). The CLI renews it in the background as it expires, so you stay signed in and no API token is created per machine. `--token` saves the API token you supplied instead. The same file backs `cargo-cdk`, so one login serves both.
+`--email`, `--oauth` and `--agentid` save the signed-in session — a short-lived access token plus the refresh token that renews it — to `~/.config/cargo-ai/credentials.json` (file mode `0600`). The CLI renews it in the background as it expires, so you stay signed in and no API token is created per machine. `--token` saves the API token you supplied instead. The same file backs `cargo-ai project`, so one login serves both.
 
 `cargo-ai logout` revokes the session at the identity provider, so signing out is final. A token you supplied yourself with `--token` is only forgotten locally, since it may be in use elsewhere; pass `--keep-token` to force that behaviour for a session too. If a credentials file cannot be deleted — a read-only config directory, or one owned by another user — `logout` fails and names the file rather than reporting a sign-out the next command would contradict.
 
@@ -245,7 +245,7 @@ Other release verbs (`list`, `get <uuid>`, `get-deployed`, `get-draft`, `update-
 
 ## Agent Skills
 
-[Cargo Skills](https://github.com/getcargohq/cargo-skills) teaches AI coding agents (Claude Code, Codex, Cursor, Windsurf, GitHub Copilot, Hermes Agent, etc.) how to use this CLI — seventeen skills covering lead sourcing, enrichment, email verification, lead scoring, CRM sync, buying-signal monitoring, orchestration, storage, and workspace-as-code.
+[Cargo Skills](https://github.com/getcargohq/cargo-skills) teaches AI coding agents (Claude Code, Codex, Cursor, Windsurf, GitHub Copilot, Hermes Agent, etc.) how to use this CLI — seventeen skills covering lead sourcing, enrichment, email verification, lead scoring, CRM sync, buying-signal monitoring, orchestration, storage, and projects (GTM as Code).
 
 **Let your agent install everything.** Paste this into Claude Code, Codex, or Cursor and it handles the CLI, sign-in, and skills for its own platform:
 

package/build/commands/ask/harness/instructions.js

@@ -1,4 +1,4 @@
-import { cdkProjectRoot } from "@cargo-ai/cdk/cli";
+import { findProjectDir } from "@cargo-ai/cdk/cli";
 import { buildReleaseInstructionAppendix } from "./release.js";
 const LOCAL_WORKING_COPY_INSTRUCTIONS = `You are working in the user's local working copy, not a sandbox. Prefer plan over deploy.
 
@@ -7,13 +7,13 @@ The user confirms each Bash, Write, Edit and NotebookEdit call, and can only ans
 When you need a multiple-choice answer, call AskUserQuestion. This session presents the options in the terminal and returns the user's answers as the tool result. Do not wait for a Claude Code question picker.
 
 Prefer minimal, focused diffs; match the existing code style; run the project's own checks when they exist. End each task with a short summary of what changed and how it was validated.`;
-const CDK_RAILS_INSTRUCTIONS = `This directory is a Cargo CDK project.
-- Never edit cargo.state.json, cargo.state.lock, or .cargo-ai/ by hand — they are generated. Repoint this project's deploy state with \`cargo-cdk state bind\`.
-- Validate your changes before declaring them done: run \`npx tsc --noEmit\` and \`npx cargo-cdk plan\` (plan only reads — it changes nothing).
-- Never run \`cargo-cdk deploy\`, \`destroy\`, \`import\`, or \`rollback\` unless the user explicitly asked.`;
+const CDK_RAILS_INSTRUCTIONS = `This directory is a Cargo project.
+- Never edit cargo.state.json, cargo.state.lock, or .cargo-ai/ by hand — they are generated. Repoint this project's deploy state with \`cargo-ai project state bind\`.
+- Validate your changes before declaring them done: run \`npx tsc --noEmit\` and \`cargo-ai project plan\` (plan only reads — it changes nothing).
+- Never run \`cargo-ai project deploy\`, \`destroy\`, \`import\`, or \`rollback\` unless the user explicitly asked.`;
 const LOCAL_CDK_RAILS_SKILL = {
-    name: "cdk-rails",
-    description: "Rails for working on a Cargo CDK project on this machine.",
+    name: "project-rails",
+    description: "Rails for working on a Cargo project on this machine.",
     content: CDK_RAILS_INSTRUCTIONS,
 };
 /**
@@ -21,7 +21,7 @@ const LOCAL_CDK_RAILS_SKILL = {
  * Exported for tests.
  */
 export function localHarnessInstructions(dir, release) {
-    const rails = cdkProjectRoot(dir) !== undefined
+    const rails = findProjectDir(dir) !== undefined
         ? `${LOCAL_WORKING_COPY_INSTRUCTIONS}\n\n${CDK_RAILS_INSTRUCTIONS}`
         : LOCAL_WORKING_COPY_INSTRUCTIONS;
     if (release === undefined) {
@@ -36,7 +36,7 @@ export function localHarnessInstructions(dir, release) {
 }
 /** Exported for tests. */
 export function localHarnessSkills(dir) {
-    if (cdkProjectRoot(dir) !== undefined) {
+    if (findProjectDir(dir) !== undefined) {
         return [LOCAL_CDK_RAILS_SKILL];
     }
     return [];

package/build/commands/mailboxManagement/mailbox.js

@@ -59,7 +59,7 @@ Examples:
       --first-name Cargo --last-name Outreach --folder-uuid 660e8400-...
 
 The mailbox starts pending until the provider issues credentials. Prefer
-defineMailbox in a CDK repo for the inbox itself; this command is the
+defineMailbox in a project for the inbox itself; this command is the
 imperative counterpart.`)
         .action(async (opts) => {
         const api = getApi();

package/build/commands/start/brief.js

@@ -77,7 +77,7 @@ function opening(project) {
     return [
         "Work with the user on the Cargo workspace declared in this repo.",
         "",
-        "This is a Cargo CDK project: the workspace — connectors, models, plays,",
+        "This is a Cargo project: the workspace — connectors, models, plays,",
         "tools and agents — is defined in files under `infra/` and applied with",
         "`npm run deploy`. Read what is declared before changing anything; the",
         "repo, not the workspace, is the source of truth.",
@@ -94,7 +94,7 @@ function firstMove(project) {
     if (project.kind === "none") {
         return [
             "3. Ask what they are trying to do before building anything. If they are",
-            "   not sure, `npx @cargo-ai/cdk cookbook list` is the menu of worked",
+            "   not sure, `cargo-ai project cookbook list` is the menu of worked",
             "   pipelines, and `cargo-ai orchestration action list <query>` is the",
             "   catalog of individual actions.",
         ];

package/build/commands/start/index.js

@@ -15,7 +15,7 @@
 // or a docs snippet, and every step leaves a valid machine behind: cancel after
 // signing in and you are signed in.
 import { spawnSync } from "node:child_process";
-import { askText, availableCodingAgents, cdkProjectRoot, COMPANY_CONTEXT_PATH, hasCompanyContext, installedCookbooks, isInteractive, launchBriefed, requireAnswer, selectOne, skillsInstalledFor, } from "@cargo-ai/cdk/cli";
+import { askText, availableCodingAgents, COMPANY_CONTEXT_PATH, findProjectDir, hasCompanyContext, installedCookbooks, isInteractive, launchBriefed, requireAnswer, selectOne, skillsInstalledFor, } from "@cargo-ai/cdk/cli";
 import { AGENT_SKILLS_NEXT_STEP } from "../../agentSkills.js";
 import { isSignedIn } from "../../setupIssues.js";
 import { parseBooleanOption } from "../../utils/booleanOption.js";
@@ -35,7 +35,7 @@ const EMAIL = "email";
  * Exported for tests; `go` is the only production caller.
  */
 export function resolveProjectContext(cwd) {
-    const root = cdkProjectRoot(cwd);
+    const root = findProjectDir(cwd);
     if (root === undefined) {
         return { kind: "none" };
     }

package/build/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { createRequire } from "node:module";
-import { availableCodingAgents, BRAND, canRunPalette, cdkProjectRoot, creditsLeftOf, declareSources, fetchSubscription, fetchWorkspaceName, formatWorkspaceSuffix, isInteractive, isUnpaidPlan, printSetupIssues, registerCommands as registerCdkCommands, runPalette, SessionExpiredError, } from "@cargo-ai/cdk/cli";
+import { availableCodingAgents, BRAND, canRunPalette, creditsLeftOf, declareSources, fetchSubscription, fetchWorkspaceName, findProjectDir, formatWorkspaceSuffix, isInteractive, isUnpaidPlan, 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";
@@ -51,7 +51,7 @@ program
     .addHelpText("after", `
 Agent skills:
   Teach your coding agent this CLI — skills covering sourcing, enrichment,
-  orchestration, storage, connectors, workspace-as-code (CDK), diagnostics and alerts.
+  orchestration, storage, connectors, projects (GTM as Code), diagnostics and alerts.
     Any agent (skills.sh):  npx skills add getcargohq/cargo-skills
     Claude Code:            /plugin marketplace add getcargohq/cargo-skills
     Codex:                  codex plugin marketplace add getcargohq/cargo-skills
@@ -290,11 +290,11 @@ async function openPalette(startPath) {
         // 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);
+        const root = findProjectDir(cwd);
         return buildPaletteLayout({
             signedIn: isSignedIn(),
             agents,
-            cdkProjectRoot: root,
+            projectDir: root,
             cwd,
             unpaidPlan,
         });

package/build/paletteLayout.d.ts

@@ -2,8 +2,8 @@ import { type CodingAgent, type PaletteLayout, type PinnedRow } from "@cargo-ai/
 export type PaletteLayoutInput = {
     signedIn: boolean;
     agents: readonly CodingAgent[];
-    /** The CDK repo root the palette is standing in, or undefined when none. */
-    cdkProjectRoot: string | undefined;
+    /** The project (`cargo.json`) folder the palette is in, or undefined when none. */
+    projectDir: 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

package/build/paletteLayout.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"paletteLayout.d.ts","sourceRoot":"","sources":["../src/paletteLayout.ts"],"names":[],"mappings":"AAYA,OAAO,EAEL,KAAK,WAAW,EAChB,KAAK,aAAa,EAClB,KAAK,SAAS,EACf,MAAM,mBAAmB,CAAC;AA+E3B,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;;;;OAIG;IACH,GAAG,EAAE,MAAM,CAAC;IACZ;;;OAGG;IACH,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB,CAAC;AAEF,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,kBAAkB,GAAG,aAAa,CAS3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,EAAE,CA+DjE"}
+{"version":3,"file":"paletteLayout.d.ts","sourceRoot":"","sources":["../src/paletteLayout.ts"],"names":[],"mappings":"AAYA,OAAO,EAEL,KAAK,WAAW,EAChB,KAAK,aAAa,EAClB,KAAK,SAAS,EACf,MAAM,mBAAmB,CAAC;AA+E3B,MAAM,MAAM,kBAAkB,GAAG;IAC/B,QAAQ,EAAE,OAAO,CAAC;IAClB,MAAM,EAAE,SAAS,WAAW,EAAE,CAAC;IAC/B,mFAAmF;IACnF,UAAU,EAAE,MAAM,GAAG,SAAS,CAAC;IAC/B;;;;OAIG;IACH,GAAG,EAAE,MAAM,CAAC;IACZ;;;OAGG;IACH,UAAU,CAAC,EAAE,OAAO,CAAC;CACtB,CAAC;AAEF,wBAAgB,kBAAkB,CAAC,KAAK,EAAE,kBAAkB,GAAG,aAAa,CAS3E;AAED;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,KAAK,EAAE,kBAAkB,GAAG,SAAS,EAAE,CA+DjE"}

package/build/paletteLayout.js

@@ -113,8 +113,8 @@ export function pinnedRows(input) {
     // 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.cwd)
+    const projectRows = input.projectDir !== undefined
+        ? cdkRows(input.projectDir, input.cwd)
         : [
             {
                 value: DEMO,
@@ -163,9 +163,8 @@ function cdkRows(root, cwd) {
             value: ADD,
             label: "Add",
             hint: "a connector or a cookbook into this project",
-            // `--dir` because `project 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.
+            // `--dir` pins the project the palette found, so the command adds to
+            // the one on screen whichever folder of it the palette is open in.
             argv: ["project", "add", "--dir", root],
         },
         {

package/build/utils/cdkState.d.ts

@@ -17,21 +17,18 @@ export declare function importModuleDefault(file: string, subject: string): Prom
 /**
  * The CDK project directory a `--file` module belongs to — the directory `cdk
  * plan` and `cdk deploy` run in, which is what a harness agent's inferred
- * `rootDirectory` is measured from. Walk up to the repo, then back down to the
- * project (`infra/` in a scaffolded repo); a file in no recognisable project
- * answers its own directory.
- *
- * Deliberately NOT the nearest cargo.state.json. That file's position is
- * incidental — a repo deployed before `cdk deploy` ran from the project has one
- * at the repo root — so measuring from it would report no `rootDirectory` and
- * clone the repo root, while the deployed agent clones `infra/`.
+ * `rootDirectory` is measured from: the resources of the nearest `cargo.json`
+ * above the file, else above the cwd (a scratch file run from inside a
+ * project). With neither, the command stops, as `cdk plan` does: building from
+ * the file's own folder instead would load part of the project and bind the
+ * agent to a folder the deployed one does not clone, with nothing said.
  */
 export declare function cdkProjectDirFor(file: string): string;
 /**
  * Deep-resolve every `@cargo-ai/cdk` handle token in `value` to its real uuid
- * using the nearest cargo.state.json (searched from `file`'s directory upward,
- * then the cwd). `subject` names the thing under test in error messages (e.g. a
- * workflow or agent slug). A value with no tokens (literal-uuid refs, or a pure
+ * using the deploy state of the project `file` belongs to (`cdkProjectDirFor`).
+ * `subject` names the thing under test in error messages (e.g. a workflow or
+ * agent slug). A value with no tokens (literal-uuid refs, or a pure
  * body) is returned unchanged — no state needed. Fails with an actionable error
  * when state is missing or a referenced resource isn't deployed yet.
  */

package/build/utils/cdkState.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cdkState.d.ts","sourceRoot":"","sources":["../../src/utils/cdkState.ts"],"names":[],"mappings":"AAoBA,wBAAgB,oBAAoB,CAAC,GAAG,EAAE;IAAE,OAAO,CAAC,EAAE,OAAO,CAAA;CAAE,GAAG,OAAO,CASxE;AAED;;;;;;;;GAQG;AACH,wBAAsB,mBAAmB,CACvC,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CAAC;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,aAAa,EAAE,OAAO,CAAA;CAAE,CAAC,CAyBtD;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAOrD;AAaD;;;;;;;GAOG;AACH,wBAAgB,sBAAsB,CACpC,KAAK,EAAE,OAAO,EACd,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CA2CT"}
+{"version":3,"file":"cdkState.d.ts","sourceRoot":"","sources":["../../src/utils/cdkState.ts"],"names":[],"mappings":"AAoBA,wBAAgB,oBAAoB,CAAC,GAAG,EAAE;IAAE,OAAO,CAAC,EAAE,OAAO,CAAA;CAAE,GAAG,OAAO,CASxE;AAED;;;;;;;;GAQG;AACH,wBAAsB,mBAAmB,CACvC,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CAAC;IAAE,OAAO,EAAE,MAAM,CAAC;IAAC,aAAa,EAAE,OAAO,CAAA;CAAE,CAAC,CAyBtD;AAED;;;;;;;;GAQG;AACH,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAgBrD;AAED;;;;;;;GAOG;AACH,wBAAgB,sBAAsB,CACpC,KAAK,EAAE,OAAO,EACd,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CAkCT"}

package/build/utils/cdkState.js

@@ -5,10 +5,10 @@
 // `@cargo-ai/cdk` handle tokens the module references to their real uuids from
 // this project's deploy state — without deploying the module itself.
 import { existsSync } from "node:fs";
-import { dirname, isAbsolute, join, resolve } from "node:path";
+import { dirname, isAbsolute, resolve } from "node:path";
 import { pathToFileURL } from "node:url";
 import { dependenciesOf, readStateOffline, resolveTokens } from "@cargo-ai/cdk";
-import { cdkProjectDir, cdkProjectRoot } from "@cargo-ai/cdk/cli";
+import { cdkResourceDir, missingProjectFile } from "@cargo-ai/cdk/cli";
 import { ExitCodes, failWith } from "../commands/runHandler.js";
 // Peel the extra interop layer tsx adds when a TS source is transpiled to CJS:
 // the ESM namespace's `default` is then the CJS `module.exports`
@@ -53,41 +53,30 @@ export async function importModuleDefault(file, subject) {
 /**
  * The CDK project directory a `--file` module belongs to — the directory `cdk
  * plan` and `cdk deploy` run in, which is what a harness agent's inferred
- * `rootDirectory` is measured from. Walk up to the repo, then back down to the
- * project (`infra/` in a scaffolded repo); a file in no recognisable project
- * answers its own directory.
- *
- * Deliberately NOT the nearest cargo.state.json. That file's position is
- * incidental — a repo deployed before `cdk deploy` ran from the project has one
- * at the repo root — so measuring from it would report no `rootDirectory` and
- * clone the repo root, while the deployed agent clones `infra/`.
+ * `rootDirectory` is measured from: the resources of the nearest `cargo.json`
+ * above the file, else above the cwd (a scratch file run from inside a
+ * project). With neither, the command stops, as `cdk plan` does: building from
+ * the file's own folder instead would load part of the project and bind the
+ * agent to a folder the deployed one does not clone, with nothing said.
  */
 export function cdkProjectDirFor(file) {
     const absPath = isAbsolute(file) ? file : resolve(process.cwd(), file);
-    const fileDir = dirname(absPath);
-    const repoRoot = cdkProjectRoot(fileDir);
-    if (repoRoot === undefined)
-        return fileDir;
-    const project = cdkProjectDir(repoRoot);
-    return project === undefined ? repoRoot : project;
-}
-// Walk up from `startDir` looking for a directory that holds cargo.state.json.
-function findStateRoot(startDir) {
-    let dir = startDir;
-    for (;;) {
-        if (existsSync(join(dir, "cargo.state.json")))
-            return dir;
-        const parent = dirname(dir);
-        if (parent === dir)
-            return undefined;
-        dir = parent;
+    const fileProject = cdkResourceDir(dirname(absPath));
+    const project = fileProject !== undefined ? fileProject : cdkResourceDir(process.cwd());
+    if (project === undefined) {
+        const missing = missingProjectFile(dirname(absPath));
+        failWith(missing.message, {
+            code: ExitCodes.InvalidUsage,
+            extra: { run: missing.run },
+        });
     }
+    return project;
 }
 /**
  * Deep-resolve every `@cargo-ai/cdk` handle token in `value` to its real uuid
- * using the nearest cargo.state.json (searched from `file`'s directory upward,
- * then the cwd). `subject` names the thing under test in error messages (e.g. a
- * workflow or agent slug). A value with no tokens (literal-uuid refs, or a pure
+ * using the deploy state of the project `file` belongs to (`cdkProjectDirFor`).
+ * `subject` names the thing under test in error messages (e.g. a workflow or
+ * agent slug). A value with no tokens (literal-uuid refs, or a pure
  * body) is returned unchanged — no state needed. Fails with an actionable error
  * when state is missing or a referenced resource isn't deployed yet.
  */
@@ -95,20 +84,15 @@ export function resolveTokensFromState(value, file, subject) {
     const deps = dependenciesOf(value);
     if (deps.size === 0)
         return value;
-    const absPath = isAbsolute(file) ? file : resolve(process.cwd(), file);
-    const stateRoot = findStateRoot(dirname(absPath)) ?? findStateRoot(process.cwd());
-    if (stateRoot === undefined) {
-        failWith(`${subject} references ${String(deps.size)} deployed resource(s) ` +
-            `(${[...deps].join(", ")}), but no cargo.state.json was found near ` +
-            `${absPath} or the current directory. Deploy the resources first with ` +
-            "`cargo-ai project deploy`, or reference them by literal uuid " +
-            "(toolRef / agentRef / connectorRef).", { code: ExitCodes.NotFound });
-    }
+    // The project's own state file, beside its cargo.json, rather than the
+    // nearest cargo.state.json: in a repository of several projects that could
+    // be another project's.
+    const project = cdkProjectDirFor(file);
     // A project whose state lives in the workspace has a pointer here, not a
     // resource map, so the cache the last plan or deploy left behind is what
     // answers this offline. Resolving a handle is a read of what is already
     // deployed — worth a stale answer, not worth a round trip on every run.
-    const state = readStateOffline(stateRoot);
+    const state = readStateOffline(project);
     const outputs = new Map();
     if (state !== undefined) {
         for (const [id, entry] of Object.entries(state.resources)) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cargo-ai/cli",
-  "version": "1.0.115",
+  "version": "1.0.117",
   "mcpName": "io.github.getcargohq/cargo",
   "private": false,
   "license": "UNLICENSED",
@@ -74,12 +74,12 @@
   "dependencies": {
     "@ai-sdk/harness": "^1.0.144",
     "@ai-sdk/harness-claude-code": "^1.0.148",
-    "@cargo-ai/api": "^1.0.95",
+    "@cargo-ai/api": "^1.0.96",
     "@cargo-ai/app-sdk": "^1.0.11",
-    "@cargo-ai/cdk": "^1.0.111",
+    "@cargo-ai/cdk": "^1.0.113",
     "@cargo-ai/types": "^1.0.96",
     "@cargo-ai/utils": "^1.0.32",
-    "@cargo-ai/worker-sdk": "^1.0.20",
+    "@cargo-ai/worker-sdk": "^1.0.21",
     "@modelcontextprotocol/sdk": "^1.31.0",
     "ai": "^7.0.133",
     "ai-sdk-sandbox-local": "^0.1.2",