@cargo-ai/cli 1.0.136 → 1.0.138

package/build/commands/orchestration/action.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"action.d.ts","sourceRoot":"","sources":["../../../src/commands/orchestration/action.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEzC,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,cAAc,CAAC;AA0BxC,eAAO,MAAM,mBAAmB,8BAA8B,CAAC;AAC/D,eAAO,MAAM,eAAe,yCAAyC,CAAC;AAEtE,wBAAgB,sBAAsB,CACpC,MAAM,EAAE,OAAO,EACf,MAAM,EAAE,MAAM,GAAG,EACjB,YAAY,EAAE,CAAC,OAAO,CAAC,EAAE,MAAM,KAAK,GAAG,GACtC,IAAI,CA6UN"}
+{"version":3,"file":"action.d.ts","sourceRoot":"","sources":["../../../src/commands/orchestration/action.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,OAAO,EAAE,MAAM,WAAW,CAAC;AAEzC,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,cAAc,CAAC;AA0BxC,eAAO,MAAM,mBAAmB,8BAA8B,CAAC;AAC/D,eAAO,MAAM,eAAe,yCAAyC,CAAC;AAEtE,wBAAgB,sBAAsB,CACpC,MAAM,EAAE,OAAO,EACf,MAAM,EAAE,MAAM,GAAG,EACjB,YAAY,EAAE,CAAC,OAAO,CAAC,EAAE,MAAM,KAAK,GAAG,GACtC,IAAI,CAkWN"}

package/build/commands/orchestration/action.js

@@ -20,6 +20,11 @@ graph needed. Creates a run and consumes credits.
   - List first: 'cargo-ai orchestration action list enrich'
     Each result includes an 'action' object for execute / execute-batch /
     get-output-schema.
+  - Cargo's presets (Find email, Find phone, Verify email, ...) are read-only
+    tools and agents seeded into every workspace, and list first on equal
+    relevance. A preset can also be addressed by its templateSlug, and then the
+    same action works in every workspace:
+    '{"kind":"tool","templateSlug":"email_waterfall"}'.
   - Inputs go in --data, not in the action. 'config' is optional; omit it.
   - The run is asynchronous: pass --wait-until-finished, or poll it with
     'cargo-ai orchestration run get <uuid>'.
@@ -41,11 +46,19 @@ To debug a node inside an existing workflow instead, use
         .addHelpText("after", `
 Each result includes an 'action' object you can pass to execute, execute-batch,
 or get-output-schema. All query terms must match (AND). Matches on the action
-slug or name rank above integration matches, which rank above description.
+slug or name rank above integration matches, which rank above description. On
+equal relevance a Cargo preset ranks first: presets are the read-only tools and
+agents seeded into every workspace, and a preset tool is the one call that
+tries several providers.
 
 Billed actions carry a 'credits' array — this is where pricing lives, so it is
-the answer to "what does <action> cost". Actions without it cost no credits.
-Each entry is one of three shapes, selected by the 'config' it matches:
+the answer to "what does <action> cost". A connector or native action without
+it costs no credits; a tool or agent without it is priced by the steps it runs,
+so its absence does not mean free. A tool that declares its price carries fixed
+entries for the cheapest and the dearest path through it (a waterfall stops at
+the first provider that answers): it costs between the lowest and the highest.
+
+Each 'credits' entry is one of three shapes, selected by the 'config' it matches:
 
   - fixed:   'cost' credits per call.
   - unit:    'cost' credits per 'unit' consumed, plus 'fixedCost' per call.
@@ -53,11 +66,12 @@ Each entry is one of three shapes, selected by the 'config' it matches:
 
 'fixedCost' is a base charge on top of the metered rate, not an alternative to
 it — a search billed 0.175 fixedCost + 0.025 per item costs 0.2 for one item.
-When several entries are present the price depends on config, and each entry's
-'config.jsonSchema' const/enum is what selects it (an LLM model, a phone-or-
-email toggle).
+On a connector or native action, several entries mean the price depends on
+config, and each entry's 'config.jsonSchema' const/enum is what selects it (an
+LLM model, a phone-or-email toggle).
 
 Examples:
+  $ cargo-ai orchestration action list find email
   $ cargo-ai orchestration action list enrich
   $ cargo-ai orchestration action list --kind tool
   $ cargo-ai orchestration action list send --kind connector --integration-slug slack
@@ -105,7 +119,12 @@ from the action's output schema, marked
 "dryRun", with no provider called and no credits used. An action whose output
 depends on its configuration has no fixed shape to show, and the dry run says so.
 
+A Cargo preset can also be addressed by its templateSlug, which resolves to this
+workspace's copy of the tool or agent, so the same command works in every
+workspace.
+
 Examples:
+  $ cargo-ai orchestration action execute --action '{"kind":"tool","templateSlug":"email_waterfall"}' --data '{"firstName":"Ada","lastName":"Lovelace","companyDomain":"example.com"}' --wait-until-finished
   $ cargo-ai orchestration action execute --action '{"kind":"tool","toolUuid":"550e8400-..."}' --data '{"email":"user@example.com"}'
   $ cargo-ai orchestration action execute --action '{"kind":"connector","integrationSlug":"slack","actionSlug":"postMessage","connectorUuid":"..."}' --data '{"channelId":"C0123456789","format":"markdown","body":"hello"}' --wait-until-finished
   $ cargo-ai orchestration action execute --action '{"kind":"connector","integrationSlug":"aiArk","actionSlug":"enrichCompany"}' --data '{"domain":"example.com"}' --dry-run`)
@@ -143,6 +162,7 @@ Examples:
         .option("--polling-interval <ms>", "Polling interval in milliseconds, used with --wait-until-finished (integer, default: 5000)", "5000")
         .addHelpText("after", `
 Examples:
+  $ cargo-ai orchestration action execute-batch --action '{"kind":"tool","templateSlug":"email_validator"}' --records '[{"email":"a@b.com"},{"email":"c@d.com"}]' --limit 1 --wait-until-finished
   $ cargo-ai orchestration action execute-batch --action '{"kind":"tool","toolUuid":"550e8400-..."}' --records '[{"email":"a@b.com"},{"email":"c@d.com"}]'
   $ cargo-ai orchestration action execute-batch --action '{"kind":"connector","integrationSlug":"slack","actionSlug":"postMessage","connectorUuid":"..."}' --records '[{"channelId":"C0123456789","format":"markdown","body":"hello"}]' --wait-until-finished
   $ cargo-ai orchestration action execute-batch --action '{"kind":"connector","integrationSlug":"findyMail","actionSlug":"findEmail"}' --records '[{"name":"Ada Lovelace","domain":"example.com"},{"linkedinUrl":"https://www.linkedin.com/in/ada"}]' --limit 1 --wait-until-finished`)
@@ -186,6 +206,7 @@ Some actions shape their output from their inputs — a HubSpot object type, a
 Google Sheet. Pass those in --data, exactly as you would to 'action execute'.
 
 Examples:
+  $ cargo-ai orchestration action get-output-schema --action '{"kind":"tool","templateSlug":"phone_waterfall"}'
   $ cargo-ai orchestration action get-output-schema --action '{"kind":"tool","toolUuid":"550e8400-..."}'
   $ cargo-ai orchestration action get-output-schema --action '{"kind":"connector","integrationSlug":"clearbit","actionSlug":"enrichCompany"}'
   $ cargo-ai orchestration action get-output-schema --action '{"kind":"connector","integrationSlug":"hubspot","actionSlug":"findRecords"}' --data '{"objectType":"contacts"}'`)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cargo-ai/cli",
-  "version": "1.0.136",
+  "version": "1.0.138",
   "mcpName": "io.github.getcargohq/cargo",
   "private": false,
   "license": "UNLICENSED",
@@ -74,7 +74,7 @@
   "dependencies": {
     "@ai-sdk/harness": "1.0.144",
     "@ai-sdk/harness-claude-code": "1.0.148",
-    "@cargo-ai/api": "^1.0.102",
+    "@cargo-ai/api": "^1.0.103",
     "@cargo-ai/app-sdk": "^1.0.11",
     "@cargo-ai/cdk": "^1.0.127",
     "@cargo-ai/types": "^1.0.104",