@salesforce/plugin-agent 1.24.14-demo.8 → 1.24.14-nga.0

package/oclif.manifest.json

@@ -248,7 +248,7 @@
     "agent:preview": {
       "aliases": [],
       "args": {},
-      "description": "Use this command to have a natural language conversation with an active agent in your org, as if you were an actual user. The interface is simple: in the \"Start typing...\" prompt, enter a statement, question, or command; when you're done, enter Return. Your utterance is posted on the right along with a timestamp. The agent then responds on the left. To exit the conversation, hit ESC or Control+C.\n\nThis command is useful to test if the agent responds to your utterances as you expect. For example, you can test that the agent uses a particular topic when asked a question, and then whether it invokes the correct action associated with that topic. This command is the CLI-equivalent of the Conversation Preview panel in your org's Agent Builder UI.\n\nWhen the session concludes, the command asks if you want to save the API responses and chat transcripts. By default, the files are saved to the \"./temp/agent-preview\" directory. Specify a new default directory by setting the environment variable \"SF_AGENT_PREVIEW_OUTPUT_DIR\" to the directory. Or you can pass the directory to the --output-dir flag.\n\nFind the agent's API name in its Agent Details page of your org's Agentforce Studio UI in Setup. If your agent is currently deactivated, use the \"agent activate\" CLI command to activate it.\n\nIMPORTANT: Before you use this command, you must complete a number of configuration steps in your org and your DX project. The examples in this help assume you've completed the steps. See \"Preview an Agent\" in the \"Agentforce Developer Guide\" for complete documentation: https://developer.salesforce.com/docs/einstein/genai/guide/agent-dx-preview.html.",
+      "description": "Use this command to have a natural language conversation with an active agent in your org, as if you were an actual user. The interface is simple: in the \"Start typing...\" prompt, enter a statement, question, or command; when you're done, enter Return. Your utterance is posted on the right along with a timestamp. The agent then responds on the left. To exit the conversation, hit ESC or Control+C.\n\nThis command is useful to test if the agent responds to your utterances as you expect. For example, you can test that the agent uses a particular topic when asked a question, and then whether it invokes the correct action associated with that topic. This command is the CLI-equivalent of the Conversation Preview panel in your org's Agent Builder UI.\n\nWhen the session concludes, the command asks if you want to save the API responses and chat transcripts. By default, the files are saved to the \"./temp/agent-preview\" directory. Specify a new default directory by setting the environment variable \"SF_AGENT_PREVIEW_OUTPUT_DIR\" to the directory. Or you can pass the directory to the --output-dir flag.\n\nFind the agent's API name in its Agent Details page of your org's Agentforce Studio UI in Setup. If your agent is currently deactivated, use the \"agent activate\" CLI command to activate it.\n\nIMPORTANT: Before you use this command, you must complete a number of configuration steps in your org and your DX project. For example, you must first create the link to a client connected app using the \"org login web --client-app\" CLI command to then get the value of the --client-app flag of this command. The examples in this help assume you've completed the steps. See \"Preview an Agent\" in the \"Agentforce Developer Guide\" for complete documentation: https://developer.salesforce.com/docs/einstein/genai/guide/agent-dx-preview.html.",
       "examples": [
         "Interact with an agent with API name Resort_Manager in the org with alias \"my-org\" and the linked \"agent-app\" connected app:\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager --target-org my-org --client-app agent-app",
         "Same as the preceding example, but this time save the conversation transcripts to the \"./transcripts/my-preview\" directory rather than the default \"./temp/agent-preview\":\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager --target-org my-org --client-app agent-app --output-dir transcripts/my-preview"
@@ -285,7 +285,7 @@
             "target-org"
           ],
           "name": "client-app",
-          "summary": "Name of the linked client app to use for the agent connection. You must have previously created this link with \"org login web --client-app\". Run \"org display\" to see the available linked client apps.",
+          "summary": "Name of the linked client app to use for the agent connection.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -300,7 +300,7 @@
         },
         "authoring-bundle": {
           "name": "authoring-bundle",
-          "summary": "Preview an ephemeral agent by specifying the API name of the Authoring Bundle metadata",
+          "summary": "Preview a next-gen agent by specifying the API name of the authoring bundle metadata component that implements it.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -319,6 +319,12 @@
           "summary": "Enable Apex debug logging during the agent preview conversation.",
           "allowNo": false,
           "type": "boolean"
+        },
+        "use-live-actions": {
+          "name": "use-live-actions",
+          "summary": "Use real actions in the org; if not specified, preview uses AI to mock actions.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
@@ -540,10 +546,10 @@
     "agent:generate:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Generates an authoring bundle containing Agent and its meta.xml file from an agent specification file.",
+      "description": "Authoring bundles are metadata types that represent the next-gen Salesforce agents. Their exact metadata name is AiAuthoringBundle and they consist of a standard \"\\*-meta.xml\" metadata file and an agent file (with extension \".agent\") that fully describes the next-gen agent. Use this command to generate an authoring bundle based on an agent spec YAML file, which you create with the \"agent create agent-spec\" command.\n\nBy default, authoring bundles are generated in the force-app/main/default/aiAuthoringBundles/<api-name> directory. Use the --output-dir to generate them elsewhere.",
       "examples": [
-        "Generate an authoring bundle from a specification file:\n<%= config.bin %> <%= command.id %> --spec-file path/to/spec.yaml --name \"My Authoring Bundle\"",
-        "Generate an authoring bundle with a custom output directory:\n<%= config.bin %> <%= command.id %> --spec-file path/to/spec.yaml --name \"My Authoring Bundle\" --output-dir path/to/output"
+        "Generate an authoring bundle from the \"specs/agentSpec.yaml\" agent spec YAML file and give it the label \"My Authoring Bundle\":\n<%= config.bin %> <%= command.id %> --spec-file specs/agentSpec.yaml --name \"My Authoring Bundle\"",
+        "Same as previous example, but generate the files in the other-package-dir/main/default/aiAuthoringBundles directory:\n<%= config.bin %> <%= command.id %> --spec-file specs/agentSpec.yaml --name \"My Authoring Bundle\" --output-dir other-package-dir/main/default/aiAuthoringBundles"
       ],
       "flags": {
         "json": {
@@ -573,7 +579,7 @@
         },
         "api-name": {
           "name": "api-name",
-          "summary": "API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name must not exist in the org.",
+          "summary": "API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name can't exist in the org.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -588,7 +594,7 @@
         "spec": {
           "char": "f",
           "name": "spec",
-          "summary": "Path to the agent specification file.",
+          "summary": "Path to the agent spec YAML file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -596,7 +602,7 @@
         "output-dir": {
           "char": "d",
           "name": "output-dir",
-          "summary": "Directory where the authoring bundle files will be generated.",
+          "summary": "Directory where the authoring bundle files are generated.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -617,7 +623,7 @@
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an authoring bundle from an agent specification.",
+      "summary": "Generate a local authoring bundle from an existing agent spec YAML file.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "FLAGGABLE_PROMPTS": {
@@ -626,11 +632,11 @@
           "required": true
         },
         "api-name": {
-          "message": "API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name must not exist in the org.",
+          "message": "API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name can't exist in the org.",
           "promptMessage": "API name of the new authoring bundle"
         },
         "spec": {
-          "message": "Path to the agent specification file.",
+          "message": "Path to the agent spec YAML file.",
           "required": true
         }
       },
@@ -799,9 +805,9 @@
     "agent:publish:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Publishes an Agent Authoring Bundle by compiling the .agent file and creating a new agent in your org.",
+      "description": "When you publish an authoring bundle to your org, a number of things happen. First, this command validates that the agent file (with extension \".agent\") successfully compiles. Then the authoring bundle metadata component is deployed to the org, and all associated metadata components, such as the Bot, BotVersion, and GenAiXXX components, are either created or updated. The org then creates a new next-gen agent based on the deployed authoring bundle and associated metadata. Finally, all the metadata associated with the new agent is retrieved back to your local DX project.\n\nAuthoring bundles are metadata types that represent the next-gen Salesforce agents. Their exact metadata name is AiAuthoringBundle and they consist of a standard \"\\*-meta.xml\" metadata file and an agent file (with extension \".agent\") that fully describes the next-gen agent.\n\nThis command requires the API name of the authoring bundle; if you don't provide it with the --api-name flag, the command prompts you for it.",
       "examples": [
-        "Publish an Agent Authoring Bundle:\n<%= config.bin %> <%= command.id %> --api-name path/to/bundle --agent-name \"My New Agent\" --target-org myorg@example.com"
+        "Publish an authoring bundle with API name MyAuthoringBundle to the org with alias \"my-org\", resulting in a new agent named \"My Fab Agent\"::\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --agent-name \"My Fab Agent\" --target-org my-org"
       ],
       "flags": {
         "json": {
@@ -839,7 +845,7 @@
         "api-name": {
           "char": "n",
           "name": "api-name",
-          "summary": "API name of the Agent Authoring Bundle to publish.",
+          "summary": "API name of the authoring bundle you want to publish.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -852,12 +858,12 @@
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Publish an Agent Authoring Bundle as a new agent",
+      "summary": "Publish an authoring bundle to your org, which results in a new next-gen agent.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "FLAGGABLE_PROMPTS": {
         "api-name": {
-          "message": "API name of the Agent Authoring Bundle to publish.",
+          "message": "API name of the authoring bundle you want to publish.",
           "promptMessage": "API name of the authoring bundle to publish"
         }
       },
@@ -1396,9 +1402,9 @@
     "agent:validate:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Validates an Agent Authoring Bundle by compiling the .agent file and checking for errors.",
+      "description": "Authoring bundles are metadata types that represent the next-gen Salesforce agents. Their exact metadata name is AiAuthoringBundle and they consist of a standard \"\\*-meta.xml\" metadata file and an agent file (with extension \".agent\") that fully describes the next-gen agent. Generate a local authoring bundle with the \"agent generate authoring-bundle\" command.\n\nThis command validates that the agent file (with extension \".agent\") that's part of the authoring bundle compiles without errors and can later be used to successfully create a next-gen agent.\n\nThis command requires the API name of the authoring bundle; if you don't provide it with the --api-name flag, the command prompts you for it.",
       "examples": [
-        "Validate an Agent Authoring Bundle:\n<%= config.bin %> <%= command.id %> --api-name path/to/bundle"
+        "Validate a local authoring bundle with API name MyAuthoringBundle:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringBundle"
       ],
       "flags": {
         "json": {
@@ -1436,7 +1442,7 @@
         "api-name": {
           "char": "n",
           "name": "api-name",
-          "summary": "API name of the Agent Authoring Bundle to validate.",
+          "summary": "API name of the authoring bundle you want to validate.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1449,12 +1455,12 @@
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Validate an Agent Authoring Bundle",
+      "summary": "Validate a local authoring bundle to ensure it compiles successfully and can be used to create a next-gen agent.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "FLAGGABLE_PROMPTS": {
         "api-name": {
-          "message": "API name of the Agent Authoring Bundle to validate.",
+          "message": "API name of the authoring bundle you want to validate.",
           "promptMessage": "API name of the authoring bundle to validate"
         }
       },
@@ -1477,5 +1483,5 @@
       ]
     }
   },
-  "version": "1.24.14-demo.8"
+  "version": "1.24.14-nga.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-agent",
     "description": "Commands to interact with Salesforce agents",
-    "version": "1.24.14-demo.8",
+    "version": "1.24.14-nga.0",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "dependencies": {
@@ -9,14 +9,16 @@
         "@inquirer/prompts": "^7.8.6",
         "@oclif/core": "^4",
         "@oclif/multi-stage-output": "^0.8.23",
-        "@salesforce/agents": "^0.18.1",
+        "@salesforce/agents": "nga",
         "@salesforce/core": "^8.23.1",
         "@salesforce/kit": "^3.2.3",
         "@salesforce/sf-plugins-core": "^12.2.4",
-        "@salesforce/source-deploy-retrieve": "^12.22.1",
+        "@salesforce/source-deploy-retrieve": "^12.25.0",
         "@salesforce/types": "^1.4.0",
+        "@types/glob": "^9.0.0",
         "ansis": "^3.3.2",
         "fast-xml-parser": "^4.5.1",
+        "glob": "^11.0.3",
         "ink": "5.0.1",
         "ink-text-input": "^6.0.0",
         "inquirer-autocomplete-standalone": "^0.8.1",
@@ -229,7 +231,7 @@
     "exports": "./lib/index.js",
     "type": "module",
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.24.14-demo.8.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.24.14-demo.8.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.24.14-nga.0.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.24.14-nga.0.sig"
     }
 }