@salesforce/plugin-agent 1.24.14-demo.8 → 1.24.14-demo.9

package/README.md

@@ -112,7 +112,7 @@ EXAMPLES
     $ sf agent activate --api-name Resort_Manager --target-org my-org
 ```
 
-_See code: [src/commands/agent/activate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/activate.ts)_
+_See code: [src/commands/agent/activate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/activate.ts)_
 
 ## `sf agent create`
 
@@ -174,7 +174,7 @@ EXAMPLES
     $ sf agent create --name "Resort Manager" --spec specs/resortManagerAgent.yaml --preview
 ```
 
-_See code: [src/commands/agent/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/create.ts)_
+_See code: [src/commands/agent/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/create.ts)_
 
 ## `sf agent deactivate`
 
@@ -214,7 +214,7 @@ EXAMPLES
     $ sf agent deactivate --api-name Resort_Manager --target-org my-org
 ```
 
-_See code: [src/commands/agent/deactivate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/deactivate.ts)_
+_See code: [src/commands/agent/deactivate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/deactivate.ts)_
 
 ## `sf agent generate agent-spec`
 
@@ -319,11 +319,11 @@ EXAMPLES
     $ sf agent generate agent-spec --tone formal --agent-user resortmanager@myorg.com
 ```
 
-_See code: [src/commands/agent/generate/agent-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/generate/agent-spec.ts)_
+_See code: [src/commands/agent/generate/agent-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/generate/agent-spec.ts)_
 
 ## `sf agent generate authoring-bundle`
 
-Generate an authoring bundle from an agent specification.
+Generate a local authoring bundle from an existing agent spec YAML file.
 
 ```
 USAGE
@@ -331,13 +331,13 @@ USAGE
     <value>] [-d <value>] [-n <value>]
 
 FLAGS
-  -d, --output-dir=<value>   Directory where the authoring bundle files will be generated.
-  -f, --spec=<value>         Path to the agent specification file.
+  -d, --output-dir=<value>   Directory where the authoring bundle files are generated.
+  -f, --spec=<value>         Path to the agent spec YAML file.
   -n, --name=<value>         Name (label) of the authoring bundle.
   -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
                              configuration variable is already set.
       --api-name=<value>     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.
+                             authoring bundle name (label); the API name can't exist in the org.
       --api-version=<value>  Override the api version used for api requests made by this command
 
 GLOBAL FLAGS
@@ -345,22 +345,29 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Generate an authoring bundle from an agent specification.
+  Generate a local authoring bundle from an existing agent spec YAML file.
 
-  Generates an authoring bundle containing Agent and its meta.xml file from an agent specification file.
+  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.
+
+  By 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:
+  Generate an authoring bundle from the "specs/agentSpec.yaml" agent spec YAML file and give it the label "My
+  Authoring Bundle":
 
-    $ sf agent generate authoring-bundle --spec-file path/to/spec.yaml --name "My Authoring Bundle"
+    $ sf agent generate authoring-bundle --spec-file specs/agentSpec.yaml --name "My Authoring Bundle"
 
-  Generate an authoring bundle with a custom output directory:
+  Same as previous example, but generate the files in the other-package-dir/main/default/aiAuthoringBundles directory:
 
-    $ sf agent generate authoring-bundle --spec-file path/to/spec.yaml --name "My Authoring Bundle" --output-dir \
-      path/to/output
+    $ sf agent generate authoring-bundle --spec-file specs/agentSpec.yaml --name "My Authoring Bundle" --output-dir \
+      other-package-dir/main/default/aiAuthoringBundles
 ```
 
-_See code: [src/commands/agent/generate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/generate/authoring-bundle.ts)_
+_See code: [src/commands/agent/generate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/generate/authoring-bundle.ts)_
 
 ## `sf agent generate template`
 
@@ -408,7 +415,7 @@ EXAMPLES
       force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1
 ```
 
-_See code: [src/commands/agent/generate/template.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/generate/template.ts)_
+_See code: [src/commands/agent/generate/template.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/generate/template.ts)_
 
 ## `sf agent generate test-spec`
 
@@ -469,7 +476,7 @@ EXAMPLES
       force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml
 ```
 
-_See code: [src/commands/agent/generate/test-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/generate/test-spec.ts)_
+_See code: [src/commands/agent/generate/test-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/generate/test-spec.ts)_
 
 ## `sf agent preview`
 
@@ -481,16 +488,15 @@ USAGE
     [--authoring-bundle <value>] [-d <value>] [-x]
 
 FLAGS
-  -c, --client-app=<value>        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.
+  -c, --client-app=<value>        Name of the linked client app to use for the agent connection.
   -d, --output-dir=<value>        Directory where conversation transcripts are saved.
   -n, --api-name=<value>          API name of the agent you want to interact with.
   -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
                                   configuration variable is already set.
   -x, --apex-debug                Enable Apex debug logging during the agent preview conversation.
       --api-version=<value>       Override the api version used for api requests made by this command
-      --authoring-bundle=<value>  Preview an ephemeral agent by specifying the API name of the Authoring Bundle metadata
+      --authoring-bundle=<value>  Preview a next-gen agent by specifying the API name of the authoring bundle metadata
+                                  component that implements it.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -517,8 +523,9 @@ DESCRIPTION
   currently deactivated, use the "agent activate" CLI command to activate it.
 
   IMPORTANT: 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:
+  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
@@ -534,18 +541,18 @@ EXAMPLES
       transcripts/my-preview
 ```
 
-_See code: [src/commands/agent/preview.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/preview.ts)_
+_See code: [src/commands/agent/preview.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/preview.ts)_
 
 ## `sf agent publish authoring-bundle`
 
-Publish an Agent Authoring Bundle as a new agent
+Publish an authoring bundle to your org, which results in a new next-gen agent.
 
 ```
 USAGE
   $ sf agent publish authoring-bundle -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>]
 
 FLAGS
-  -n, --api-name=<value>     API name of the Agent Authoring Bundle to publish.
+  -n, --api-name=<value>     API name of the authoring bundle you want to publish.
   -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
                              configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
@@ -555,18 +562,29 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Publish an Agent Authoring Bundle as a new agent
+  Publish an authoring bundle to your org, which results in a new next-gen agent.
+
+  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.
+
+  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.
 
-  Publishes an Agent Authoring Bundle by compiling the .agent file and creating a new agent in your org.
+  This 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:
+  Publish an authoring bundle with API name MyAuthoringBundle to the org with alias "my-org", resulting in a new agent
+  named "My Fab Agent"::
 
-    $ sf agent publish authoring-bundle --api-name path/to/bundle --agent-name "My New Agent" --target-org \
-      myorg@example.com
+    $ sf agent publish authoring-bundle --api-name MyAuthoringbundle --agent-name "My Fab Agent" --target-org my-org
 ```
 
-_See code: [src/commands/agent/publish/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/publish/authoring-bundle.ts)_
+_See code: [src/commands/agent/publish/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/publish/authoring-bundle.ts)_
 
 ## `sf agent test create`
 
@@ -621,7 +639,7 @@ EXAMPLES
     $ sf agent test create --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview
 ```
 
-_See code: [src/commands/agent/test/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/test/create.ts)_
+_See code: [src/commands/agent/test/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/test/create.ts)_
 
 ## `sf agent test list`
 
@@ -656,7 +674,7 @@ EXAMPLES
     $ sf agent test list --target-org my-org
 ```
 
-_See code: [src/commands/agent/test/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/test/list.ts)_
+_See code: [src/commands/agent/test/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/test/list.ts)_
 
 ## `sf agent test results`
 
@@ -722,7 +740,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/results.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/test/results.ts)_
+_See code: [src/commands/agent/test/results.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/test/results.ts)_
 
 ## `sf agent test resume`
 
@@ -795,7 +813,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/resume.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/test/resume.ts)_
+_See code: [src/commands/agent/test/resume.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/test/resume.ts)_
 
 ## `sf agent test run`
 
@@ -869,18 +887,18 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/run.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/test/run.ts)_
+_See code: [src/commands/agent/test/run.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/test/run.ts)_
 
 ## `sf agent validate authoring-bundle`
 
-Validate an Agent Authoring Bundle
+Validate a local authoring bundle to ensure it compiles successfully and can be used to create a next-gen agent.
 
 ```
 USAGE
   $ sf agent validate authoring-bundle -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>]
 
 FLAGS
-  -n, --api-name=<value>     API name of the Agent Authoring Bundle to validate.
+  -n, --api-name=<value>     API name of the authoring bundle you want to validate.
   -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
                              configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
@@ -890,16 +908,25 @@ GLOBAL FLAGS
   --json               Format output as json.
 
 DESCRIPTION
-  Validate an Agent Authoring Bundle
+  Validate a local authoring bundle to ensure it compiles successfully and can be used to create a next-gen agent.
+
+  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.
+
+  This 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.
 
-  Validates an Agent Authoring Bundle by compiling the .agent file and checking for errors.
+  This 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:
+  Validate a local authoring bundle with API name MyAuthoringBundle:
 
-    $ sf agent validate authoring-bundle --api-name path/to/bundle
+    $ sf agent validate authoring-bundle --api-name MyAuthoringBundle
 ```
 
-_See code: [src/commands/agent/validate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.8/src/commands/agent/validate/authoring-bundle.ts)_
+_See code: [src/commands/agent/validate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.24.14-demo.9/src/commands/agent/validate/authoring-bundle.ts)_
 
 <!-- commandsstop -->

package/messages/agent.generate.authoring-bundle.md

@@ -1,18 +1,20 @@
 # summary
 
-Generate an authoring bundle from an agent specification.
+Generate a local authoring bundle from an existing agent spec YAML file.
 
 # description
 
-Generates an authoring bundle containing Agent and its meta.xml file from an agent specification file.
+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.
+
+By default, authoring bundles are generated in the force-app/main/default/aiAuthoringBundles/<api-name> directory. Use the --output-dir to generate them elsewhere.
 
 # flags.spec.summary
 
-Path to the agent specification file.
+Path to the agent spec YAML file.
 
 # flags.output-dir.summary
 
-Directory where the authoring bundle files will be generated.
+Directory where the authoring bundle files are generated.
 
 # flags.name.summary
 
@@ -20,7 +22,7 @@ Name (label) of the authoring bundle.
 
 # flags.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.
+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.
 
 # flags.api-name.prompt
 
@@ -28,20 +30,22 @@ API name of the new authoring bundle
 
 # examples
 
-- Generate an authoring bundle from a specification file:
-  <%= config.bin %> <%= command.id %> --spec-file path/to/spec.yaml --name "My Authoring Bundle"
+- Generate an authoring bundle from the "specs/agentSpec.yaml" agent spec YAML file and give it the label "My Authoring Bundle":
+
+  <%= 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:
 
-- Generate an authoring bundle with a custom output directory:
-  <%= config.bin %> <%= command.id %> --spec-file path/to/spec.yaml --name "My Authoring Bundle" --output-dir path/to/output
+  <%= config.bin %> <%= command.id %> --spec-file specs/agentSpec.yaml --name "My Authoring Bundle" --output-dir other-package-dir/main/default/aiAuthoringBundles
 
 # error.no-spec-file
 
-No agent specification file found at the specified path.
+No agent spec YAML file found at the specified path.
 
 # error.invalid-spec-file
 
-The specified file is not a valid agent specification file.
+The specified file is not a valid agent spec YAML file.
 
 # error.failed-to-create-agent
 
-Failed to create Agent from the agent specification.
+Failed to create a next-gen agent from the agent spec YAML file.

package/messages/agent.preview.md

@@ -12,7 +12,7 @@ When the session concludes, the command asks if you want to save the API respons
 
 Find 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.
 
-IMPORTANT: 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.
+IMPORTANT: 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.
 
 # flags.api-name.summary
 
@@ -20,11 +20,11 @@ API name of the agent you want to interact with.
 
 # flags.authoring-bundle.summary
 
-Preview an ephemeral agent by specifying the API name of the Authoring Bundle metadata
+Preview a next-gen agent by specifying the API name of the authoring bundle metadata component that implements it. 
 
 # flags.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.
+Name of the linked client app to use for the agent connection.
 
 # flags.output-dir.summary
 

package/messages/agent.publish.authoring-bundle.md

@@ -1,19 +1,24 @@
 # summary
 
-Publish an Agent Authoring Bundle as a new agent
+Publish an authoring bundle to your org, which results in a new next-gen agent.
 
 # description
 
-Publishes an Agent Authoring Bundle by compiling the .agent file and creating a new agent in your org.
+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.
+
+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.
+
+This 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:
-  <%= 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"::
+
+  <%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --agent-name "My Fab Agent" --target-org my-org
 
 # flags.api-name.summary
 
-API name of the Agent Authoring Bundle to publish.
+API name of the authoring bundle you want to publish.
 
 # flags.api-name.prompt
 
@@ -21,15 +26,15 @@ API name of the authoring bundle to publish
 
 # flags.agent-name.summary
 
-Name for the new agent to be created
+Name for the new agent that is created from the published authoring bundle.
 
 # error.missingRequiredFlags
 
-Required flag(s) missing: %s
+Required flag(s) missing: %s.
 
 # error.invalidBundlePath
 
-Invalid bundle path. Please provide a valid path to an Agent Authoring Bundle.
+Invalid bundle path. Provide a valid directory path to an authoring bundle.
 
 # error.publishFailed
 
@@ -42,4 +47,4 @@ Could not find a .bundle-meta.xml file with API name '%s' in the project.
 
 # error.agentNotFoundAction
 
-Please check that the API name is correct and that the .agent file exists in your project directory.
+Check that the API name is correct and that the .agent file exists in your project directory.

package/messages/agent.validate.authoring-bundle.md

@@ -1,19 +1,24 @@
 # summary
 
-Validate an Agent Authoring Bundle
+Validate a local authoring bundle to ensure it compiles successfully and can be used to create a next-gen agent.
 
 # description
 
-Validates an Agent Authoring Bundle by compiling the .agent file and checking for errors.
+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.
+
+This 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.
+
+This 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:
-  <%= config.bin %> <%= command.id %> --api-name path/to/bundle
+- Validate a local authoring bundle with API name MyAuthoringBundle:
+
+  <%= config.bin %> <%= command.id %> --api-name MyAuthoringBundle
 
 # flags.api-name.summary
 
-API name of the Agent Authoring Bundle to validate.
+API name of the authoring bundle you want to validate.
 
 # flags.api-name.prompt
 
@@ -21,15 +26,15 @@ API name of the authoring bundle to validate
 
 # error.missingRequiredFlags
 
-Required flag(s) missing: %s
+Required flag(s) missing: %s.
 
 # error.invalidBundlePath
 
-Invalid bundle path. Please provide a valid path to an Agent Authoring Bundle.
+Invalid authoring bundle path. Provide a valid directory path to the authoring bundle you want to validate.
 
 # error.compilationFailed
 
-Agent compilation failed with the following errors:
+Compilation of the agent file failed with the following errors:
 %s
 
 # error.agentNotFound
@@ -38,4 +43,4 @@ Could not find a .bundle-meta.xml file with API name '%s' in the project.
 
 # error.agentNotFoundAction
 
-Please check that the API name is correct and that the .agent file exists in your project directory.
+Check that the API name is correct and that the ".agent" file exists in your project directory.

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"
@@ -540,10 +540,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 +573,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 +588,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 +596,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 +617,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 +626,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
         }
       },
@@ -796,12 +796,12 @@
         "test-spec:generate:agent"
       ]
     },
-    "agent:publish:authoring-bundle": {
+    "agent:validate:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Publishes an Agent Authoring Bundle by compiling the .agent file and creating a new agent in your org.",
+      "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": [
-        "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"
+        "Validate a local authoring bundle with API name MyAuthoringBundle:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringBundle"
       ],
       "flags": {
         "json": {
@@ -839,7 +839,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 validate.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -847,18 +847,18 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:publish:authoring-bundle",
+      "id": "agent:validate:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Publish an Agent Authoring Bundle as a new agent",
+      "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 publish.",
-          "promptMessage": "API name of the authoring bundle to publish"
+          "message": "API name of the authoring bundle you want to validate.",
+          "promptMessage": "API name of the authoring bundle to validate"
         }
       },
       "isESM": true,
@@ -866,17 +866,17 @@
         "lib",
         "commands",
         "agent",
-        "publish",
+        "validate",
         "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:publish:authoring-bundle",
-        "publish:agent:authoring-bundle",
-        "publish:authoring-bundle:agent",
-        "agent:authoring-bundle:publish",
-        "authoring-bundle:agent:publish",
-        "authoring-bundle:publish:agent"
+        "agent:validate:authoring-bundle",
+        "validate:agent:authoring-bundle",
+        "validate:authoring-bundle:agent",
+        "agent:authoring-bundle:validate",
+        "authoring-bundle:agent:validate",
+        "authoring-bundle:validate:agent"
       ]
     },
     "agent:test:create": {
@@ -1393,12 +1393,12 @@
         "run:test:agent"
       ]
     },
-    "agent:validate:authoring-bundle": {
+    "agent:publish:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Validates an Agent Authoring Bundle by compiling the .agent file and checking for errors.",
+      "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": [
-        "Validate an Agent Authoring Bundle:\n<%= config.bin %> <%= command.id %> --api-name path/to/bundle"
+        "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": {
@@ -1436,7 +1436,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 publish.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -1444,18 +1444,18 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:validate:authoring-bundle",
+      "id": "agent:publish:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Validate an Agent Authoring Bundle",
+      "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 validate.",
-          "promptMessage": "API name of the authoring bundle to validate"
+          "message": "API name of the authoring bundle you want to publish.",
+          "promptMessage": "API name of the authoring bundle to publish"
         }
       },
       "isESM": true,
@@ -1463,19 +1463,19 @@
         "lib",
         "commands",
         "agent",
-        "validate",
+        "publish",
         "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:validate:authoring-bundle",
-        "validate:agent:authoring-bundle",
-        "validate:authoring-bundle:agent",
-        "agent:authoring-bundle:validate",
-        "authoring-bundle:agent:validate",
-        "authoring-bundle:validate:agent"
+        "agent:publish:authoring-bundle",
+        "publish:agent:authoring-bundle",
+        "publish:authoring-bundle:agent",
+        "agent:authoring-bundle:publish",
+        "authoring-bundle:agent:publish",
+        "authoring-bundle:publish:agent"
       ]
     }
   },
-  "version": "1.24.14-demo.8"
+  "version": "1.24.14-demo.9"
 }

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-demo.9",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "dependencies": {
@@ -9,7 +9,7 @@
         "@inquirer/prompts": "^7.8.6",
         "@oclif/core": "^4",
         "@oclif/multi-stage-output": "^0.8.23",
-        "@salesforce/agents": "^0.18.1",
+        "@salesforce/agents": "^0.18.2",
         "@salesforce/core": "^8.23.1",
         "@salesforce/kit": "^3.2.3",
         "@salesforce/sf-plugins-core": "^12.2.4",
@@ -229,7 +229,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-demo.9.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.24.14-demo.9.sig"
     }
 }