npm - @salesforce/plugin-agent - Versions diffs - 1.27.1 → 1.27.3 - Mend

@salesforce/plugin-agent 1.27.1 → 1.27.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (16) hide show

package/README.md +15 -15
package/lib/commands/agent/generate/authoring-bundle.d.ts +0 -1
package/lib/commands/agent/generate/authoring-bundle.js +0 -1
package/lib/commands/agent/generate/authoring-bundle.js.map +1 -1
package/lib/commands/agent/generate/template.js.map +1 -1
package/lib/commands/agent/preview.d.ts +0 -1
package/lib/commands/agent/preview.js +0 -1
package/lib/commands/agent/preview.js.map +1 -1
package/lib/commands/agent/publish/authoring-bundle.d.ts +0 -1
package/lib/commands/agent/publish/authoring-bundle.js +0 -1
package/lib/commands/agent/publish/authoring-bundle.js.map +1 -1
package/lib/commands/agent/validate/authoring-bundle.d.ts +0 -1
package/lib/commands/agent/validate/authoring-bundle.js +0 -1
package/lib/commands/agent/validate/authoring-bundle.js.map +1 -1
package/oclif.manifest.json +544 -548
package/package.json +7 -7

package/oclif.manifest.json CHANGED Viewed

@@ -322,7 +322,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
       "summary": "Interact with an agent to preview how it responds to your statements, questions, and commands (utterances).",
       "enableJsonFlag": false,
@@ -340,16 +339,14 @@
         "preview:agent"
       ]
     },
-    "agent:generate:agent-spec": {
+    "agent:test:create": {
       "aliases": [],
       "args": {},
-      "description": "An agent spec is a YAML-formatted file that contains basic information about the agent, such as its role, company description, and an AI-generated list of topics based on this information. Topics define the range of jobs your agent can handle.\n\nUse flags, such as --role and --company-description, to provide details about your company and the role that the agent plays in your company. If you prefer, you can also be prompted for the basic information; use --full-interview to be prompted for all required and optional properties. Upon command execution, the large language model (LLM) associated with your org uses the provided information to generate a list of topics for the agent. Because the LLM uses the company and role information to generate the topics, we recommend that you provide accurate, complete, and specific details so the LLM generates the best and most relevant topics. Once generated, you can edit the spec file; for example, you can remove topics that don't apply or change a topic's description.\n\nYou can also iterate the spec generation process by using the --spec flag to pass an existing agent spec file to this command, and then using the --role, --company-description, etc, flags to refine your agent properties. Iteratively improving the description of your agent allows the LLM to generate progressively better topics.\n\nYou can also specify other agent properties, such as a custom prompt template, how to ground the prompt template to add context to the agent's prompts, the tone of the prompts, and the username of a user in the org to assign to the agent.\n\nWhen your agent spec is ready, generate an authoring bundle from it by passing the spec file to the --spec flag of the \"agent generate authoring-bundle\" CLI command. An authoring bundle is a metadata type that contains an Agent Script file, which is the blueprint for an agent. (While not recommended, you can also use the agent spec file to immediately create an agent with the \"agent create\" command. We don't recommend this workflow because these types of agents don't use Agent Script, and are thus less flexible and more difficult to maintain.)",
+      "description": "To run this command, you must have an agent test spec file, which is a YAML file that lists the test cases for testing a specific agent. Use the \"agent generate test-spec\" CLI command to generate a test spec file. Then specify the file to this command with the --spec flag, or run this command with no flags to be prompted.\n\nWhen this command completes, your org contains the new agent test, which you can view and edit using the Testing Center UI. This command also retrieves the metadata component (AiEvaluationDefinition) associated with the new test to your local Salesforce DX project and displays its filename.\n\nAfter you've created the test in the org, use the \"agent test run\" command to run it.",
       "examples": [
-        "Generate an agent spec in the default location and use flags to specify the agent properties, such as its role and your company details; use your default org:\n<%= config.bin %> <%= command.id %> --type customer --role \"Field customer complaints and manage employee schedules.\" --company-name \"Coral Cloud Resorts\" --company-description \"Provide customers with exceptional destination activities, unforgettable experiences, and reservation services.\"",
-        "Generate an agent spec by being prompted for the required agent properties and generate a maxiumum of 5 topics; write the generated file to the \"specs/resortManagerSpec.yaml\" file and use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --max-topics 5 --output-file specs/resortManagerAgent.yaml --target-org my-org",
-        "Be prompted for all required and optional agent properties; use your default org:\n<%= config.bin %> <%= command.id %> --full-interview",
-        "Specify an existing agent spec file called \"specs/resortManagerAgent.yaml\", and then overwrite it with a new version that contains newly AI-generated topics based on the updated role information passed in with the --role flag:\n<%= config.bin %> <%= command.id %> --spec specs/resortManagerAgent.yaml --output-file specs/resortManagerAgent.yaml --role \"Field customer complaints, manage employee schedules, and ensure all resort operations are running smoothly\"",
-        "Specify that the conversational tone of the agent is formal and to attach the \"resortmanager@myorg.com\" username to it; be prompted for the required properties and use your default org:\n<%= config.bin %> <%= command.id %> --tone formal --agent-user resortmanager@myorg.com"
+        "Create an agent test interactively and be prompted for the test spec and API name of the test in the org; use the default org:\n<%= config.bin %> <%= command.id %>",
+        "Create an agent test and use flags to specify all required information; if a test with same API name already exists in the org, overwrite it without confirmation. Use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --force-overwrite --target-org my-org",
+        "Preview what the agent test metadata (AiEvaluationDefinition) looks like without deploying it to your default org:\n<%= config.bin %> <%= command.id %> --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview"
       ],
       "flags": {
         "json": {
@@ -367,6 +364,20 @@
           "multiple": false,
           "type": "option"
         },
+        "api-name": {
+          "name": "api-name",
+          "summary": "API name of the new test; the API name must not exist in the org.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "spec": {
+          "name": "spec",
+          "summary": "Path to the test spec YAML file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "target-org": {
           "char": "o",
           "name": "target-org",
@@ -384,163 +395,53 @@
           "multiple": false,
           "type": "option"
         },
-        "type": {
-          "name": "type",
-          "summary": "Type of agent to create. Internal types are copilots used internally by your company and customer types are the agents you create for your customers.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "customer",
-            "internal"
-          ],
-          "type": "option"
-        },
-        "role": {
-          "name": "role",
-          "summary": "Role of the agent.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "company-name": {
-          "name": "company-name",
-          "summary": "Name of your company.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "company-description": {
-          "name": "company-description",
-          "summary": "Description of your company.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "company-website": {
-          "name": "company-website",
-          "summary": "Website URL of your company.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "max-topics": {
-          "name": "max-topics",
-          "summary": "Maximum number of topics to generate in the agent spec; default is 5.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "agent-user": {
-          "name": "agent-user",
-          "summary": "Username of a user in your org to assign to your agent; determines what your agent can access and do.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "enrich-logs": {
-          "name": "enrich-logs",
-          "summary": "Adds agent conversation data to event logs so you can view all agent session activity in one place.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "true",
-            "false"
-          ],
-          "type": "option"
-        },
-        "tone": {
-          "name": "tone",
-          "summary": "Conversational style of the agent, such as how it expresses your brand personality in its messages through word choice, punctuation, and sentence structure.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "formal",
-            "casual",
-            "neutral"
-          ],
-          "type": "option"
-        },
-        "spec": {
-          "name": "spec",
-          "summary": "Agent spec file, in YAML format, to use as input to the command.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "output-file": {
-          "name": "output-file",
-          "summary": "Path for the generated YAML agent spec file; can be an absolute or relative path.",
-          "default": "specs/agentSpec.yaml",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "full-interview": {
-          "name": "full-interview",
-          "summary": "Prompt for both required and optional flags.",
+        "preview": {
+          "name": "preview",
+          "summary": "Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.",
           "allowNo": false,
           "type": "boolean"
         },
-        "prompt-template": {
-          "name": "prompt-template",
-          "summary": "API name of a customized prompt template to use instead of the default prompt template.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "grounding-context": {
-          "dependsOn": [
-            "prompt-template"
-          ],
-          "name": "grounding-context",
-          "summary": "Context information and personalization that's added to your prompts when using a custom prompt template.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "force-overwrite": {
           "name": "force-overwrite",
-          "summary": "Don't prompt the user to confirm that an existing spec file will be overwritten.",
+          "summary": "Don't prompt for confirmation when overwriting an existing test (based on API name) in your org.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:agent-spec",
+      "id": "agent:test:create",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
+      "summary": "Create an agent test in your org using a local test spec YAML file.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "agent-spec.js"
+        "test",
+        "create.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:agent-spec",
-        "generate:agent:agent-spec",
-        "generate:agent-spec:agent",
-        "agent:agent-spec:generate",
-        "agent-spec:agent:generate",
-        "agent-spec:generate:agent"
+        "agent:test:create",
+        "test:agent:create",
+        "test:create:agent",
+        "agent:create:test",
+        "create:agent:test",
+        "create:test:agent"
       ]
     },
-    "agent:generate:authoring-bundle": {
+    "agent:test:list": {
       "aliases": [],
       "args": {},
-      "description": "Authoring bundles are metadata components that contain an agent's Agent Script file. The Agent Script file is the agent's blueprint; it fully describes what the agent can do using the Agent Script language.\n\nUse this command to generate a new authoring bundle based on an agent spec YAML file, which you create with the \"agent generate agent-spec\" command. The agent spec YAML file is a high-level description of the agent; it describes its essence rather than exactly what it can do.\n\nThe metadata type for authoring bundles is aiAuthoringBundle, which consist of a standard \"<bundle-api-name>.bundle-meta.xml\" metadata file and the Agent Script file (with extension \".agent\"). When you run this command, the new authoring bundle is generated in the force-app/main/default/aiAuthoringBundles/<bundle-api-name> directory. Use the --output-dir flag to generate them elsewhere.\n\nAfter you generate the initial authoring bundle, code the Agent Script file so your agent behaves exactly as you want. The Agent Script file generated by this command is just a first draft of your agent! Interactively test the agent by conversing with it using the \"agent preview\" command. Then publish the agent to your org with the \"agent publish authoring-bundle\" command.\n\nThis command requires an org because it uses it to access an LLM for generating the Agent Script file.",
+      "description": "The command outputs a table with the name (API name) of each test along with its unique ID and the date it was created in the org.",
       "examples": [
-        "Generate an authoring bundle by being prompted for all required values, such as the agent spec YAML file, the bundle name, and the API name; use your default org:\n<%= config.bin %> <%= command.id %>",
-        "Generate an authoring bundle from the \"specs/agentSpec.yaml\" agent spec YAML file and give it the label \"My Authoring Bundle\"; use your default org:\n<%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name \"My Authoring Bundle\"",
-        "Similar to previous example, but generate the authoring bundle files in the \"other-package-dir/main/default\" package directory; use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name \"My Authoring Bundle\" --output-dir other-package-dir/main/default --target-org my-dev-org"
+        "List the agent tests in your default org:\n<%= config.bin %> <%= command.id %>",
+        "List the agent tests in an org with alias \"my-org\"\"\n<%= config.bin %> <%= command.id %> --target-org my-org"
       ],
       "flags": {
         "json": {
@@ -568,176 +469,58 @@
           "multiple": false,
           "type": "option"
         },
-        "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 can't exist in the org.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "api-version": {
           "description": "Override the api version used for api requests made by this command",
           "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "spec": {
-          "char": "f",
-          "name": "spec",
-          "summary": "Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "output-dir": {
-          "char": "d",
-          "name": "output-dir",
-          "summary": "Directory where the authoring bundle files are generated.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "name": {
-          "char": "n",
-          "name": "name",
-          "summary": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:authoring-bundle",
-      "pluginAlias": "@salesforce/plugin-agent",
-      "pluginName": "@salesforce/plugin-agent",
-      "pluginType": "core",
-      "state": "beta",
-      "strict": true,
-      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
-      "enableJsonFlag": true,
-      "requiresProject": true,
-      "FLAGGABLE_PROMPTS": {
-        "name": {
-          "message": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
-          "promptMessage": "Name (label) of the authoring bundle",
-          "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 can't exist in the org.",
-          "promptMessage": "API name of the new authoring bundle"
-        },
-        "spec": {
-          "message": "Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.",
-          "promptMessage": "Path to the agent spec YAML file",
-          "required": true
-        }
-      },
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "agent",
-        "generate",
-        "authoring-bundle.js"
-      ],
-      "aliasPermutations": [],
-      "permutations": [
-        "agent:generate:authoring-bundle",
-        "generate:agent:authoring-bundle",
-        "generate:authoring-bundle:agent",
-        "agent:authoring-bundle:generate",
-        "authoring-bundle:agent:generate",
-        "authoring-bundle:generate:agent"
-      ]
-    },
-    "agent:generate:template": {
-      "aliases": [],
-      "args": {},
-      "description": "At a high-level, agents are defined by the Bot, BotVersion, and GenAiPlannerBundle metadata types. The GenAiPlannerBundle type in turn defines the agent's topics and actions. This command uses the metadata files for these three types, located in your local DX project, to generate a BotTemplate file for a specific agent (Bot). You then use the BotTemplate file, along with the GenAiPlannerBundle file that references the BotTemplate, to package the template in a managed package that you can share between orgs or on AppExchange.\n\nUse the --agent-file flag to specify the relative or full pathname of the Bot metadata file, such as force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml. A single Bot can have multiple BotVersions, so use the --agent-version flag to specify the version. The corresponding BotVersion file must exist locally. For example, if you specify \"--agent-version 4\", then the file force-app/main/default/bots/My_Awesome_Agent/v4.botVersion-meta.xml must exist.\n\nThe new BotTemplate file is generated in the \"botTemplates\" directory in your local package directory, and has the name <Agent_API_name>_v<Version>_Template.botTemplate-meta.xml, such as force-app/main/default/botTemplates/My_Awesome_Agent_v4_Template.botTemplate-meta.xml. The command displays the full pathname of the generated files when it completes.",
-      "examples": [
-        "Generate an agent template from a Bot metadata file in your DX project that corresponds to the My_Awesome_Agent agent; use version 1 of the agent.\n<%= config.bin %> <%= command.id %> --agent-file force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1"
-      ],
-      "flags": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "flags-dir": {
-          "helpGroup": "GLOBAL",
-          "name": "flags-dir",
-          "summary": "Import flag values from a directory.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "api-version": {
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "agent-version": {
-          "name": "agent-version",
-          "required": true,
-          "summary": "Version of the agent (BotVersion).",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "agent-file": {
-          "char": "f",
-          "name": "agent-file",
-          "required": true,
-          "summary": "Path to an agent (Bot) metadata file.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "agent:generate:template",
+      "id": "agent:test:list",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an agent template from an existing agent in your DX project so you can then package the template in a managed package.",
+      "summary": "List the available agent tests in your org.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "template.js"
+        "test",
+        "list.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:template",
-        "generate:agent:template",
-        "generate:template:agent",
-        "agent:template:generate",
-        "template:agent:generate",
-        "template:generate:agent"
+        "agent:test:list",
+        "test:agent:list",
+        "test:list:agent",
+        "agent:list:test",
+        "list:agent:test",
+        "list:test:agent"
       ]
     },
-    "agent:generate:test-spec": {
+    "agent:test:results": {
       "aliases": [],
       "args": {},
-      "description": "The first step when using Salesforce CLI to create an agent test in your org is to use this interactive command to generate a local YAML-formatted test spec file. The test spec YAML file contains information about the agent being tested, such as its API name, and then one or more test cases. This command uses the metadata components in your DX project when prompting for information, such as the agent API name; it doesn't look in your org.\n\nTo generate a specific agent test case, this command prompts you for this information; when possible, the command provides a list of options for you to choose from:\n\n- Utterance: Natural language statement, question, or command used to test the agent.\n- Expected topic: API name of the topic you expect the agent to use when responding to the utterance.\n- Expected actions: One or more API names of the expection actions the agent takes.\n- Expected outcome: Natural language description of the outcome you expect.\n- (Optional) Custom evaluation: Test an agent's response for specific strings or numbers.\n- (Optional) Conversation history: Boilerplate for additional context you can add to the test in the form of a conversation history.\n\nWhen your test spec is ready, you then run the \"agent test create\" command to actually create the test in your org and synchronize the metadata with your DX project. The metadata type for an agent test is AiEvaluationDefinition.\n\nIf you have an existing AiEvaluationDefinition metadata XML file in your DX project, you can generate its equivalent YAML test spec file with the --from-definition flag.",
+      "description": "This command requires a job ID, which the original \"agent test run\" command displays when it completes. You can also use the --use-most-recent flag to see results for the most recently run agent test.\n\nBy default, this command outputs test results in human-readable tables for each test case. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
       "examples": [
-        "Generate an agent test spec YAML file interactively:\n<%= config.bin %> <%= command.id %>",
-        "Generate an agent test spec YAML file and specify a name for the new file; if the file exists, overwrite it without confirmation:\n<%= config.bin %> <%= command.id %> --output-file specs/Resort_Manager-new-version-testSpec.yaml --force-overwrite",
-        "Generate an agent test spec YAML file from an existing AiEvaluationDefinition metadata XML file in your DX project:\n<%= config.bin %> <%= command.id %> --from-definition force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml"
+        "Get the results of an agent test run in your default org using its job ID:\n<%= config.bin %> <%= command.id %> --job-id 4KBfake0000003F4AQ",
+        "Get the results of the most recently run agent test in an org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --use-most-recent --target-org my-org",
+        "Get the results of the most recently run agent test in your default org, and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --use-most-recent --output-dir ./test-results --result-format json"
       ],
       "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "flags-dir": {
           "helpGroup": "GLOBAL",
           "name": "flags-dir",
@@ -746,64 +529,98 @@
           "multiple": false,
           "type": "option"
         },
-        "from-definition": {
-          "char": "d",
-          "name": "from-definition",
-          "summary": "Filepath to the AIEvaluationDefinition metadata XML file in your DX project that you want to convert to a test spec YAML file.",
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Don't prompt for confirmation when overwriting an existing test spec YAML file.",
-          "allowNo": false,
-          "type": "boolean"
+        "job-id": {
+          "char": "i",
+          "name": "job-id",
+          "required": true,
+          "summary": "Job ID of the completed agent test run.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "output-file": {
-          "char": "f",
-          "name": "output-file",
-          "summary": "Name of the generated test spec YAML file. Default value is \"specs/<AGENT_API_NAME>-testSpec.yaml\".",
+        "result-format": {
+          "name": "result-format",
+          "summary": "Format of the agent test run results.",
+          "default": "human",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "json",
+            "human",
+            "junit",
+            "tap"
+          ],
+          "type": "option"
+        },
+        "output-dir": {
+          "char": "d",
+          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
+          "name": "output-dir",
+          "summary": "Directory to write the agent test results into.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "verbose": {
+          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
+          "name": "verbose",
+          "summary": "Show generated data in the test results output.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:test-spec",
+      "id": "agent:test:results",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.",
-      "enableJsonFlag": false,
+      "summary": "Get the results of a completed agent test run.",
+      "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "test-spec.js"
+        "test",
+        "results.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:test-spec",
-        "generate:agent:test-spec",
-        "generate:test-spec:agent",
-        "agent:test-spec:generate",
-        "test-spec:agent:generate",
-        "test-spec:generate:agent"
+        "agent:test:results",
+        "test:agent:results",
+        "test:results:agent",
+        "agent:results:test",
+        "results:agent:test",
+        "results:test:agent"
       ]
     },
-    "agent:test:create": {
+    "agent:test:resume": {
       "aliases": [],
       "args": {},
-      "description": "To run this command, you must have an agent test spec file, which is a YAML file that lists the test cases for testing a specific agent. Use the \"agent generate test-spec\" CLI command to generate a test spec file. Then specify the file to this command with the --spec flag, or run this command with no flags to be prompted.\n\nWhen this command completes, your org contains the new agent test, which you can view and edit using the Testing Center UI. This command also retrieves the metadata component (AiEvaluationDefinition) associated with the new test to your local Salesforce DX project and displays its filename.\n\nAfter you've created the test in the org, use the \"agent test run\" command to run it.",
+      "description": "This command requires a job ID, which the original \"agent test run\" command displays when it completes. You can also use the --use-most-recent flag to see results for the most recently run agent test.\n\nUse the --wait flag to specify the number of minutes for this command to wait for the agent test to complete; if the test completes by the end of the wait time, the command displays the test results. If not, the CLI returns control of the terminal to you, and you must run \"agent test resume\" again.\n\nBy default, this command outputs test results in human-readable tables for each test case. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
       "examples": [
-        "Create an agent test interactively and be prompted for the test spec and API name of the test in the org; use the default org:\n<%= config.bin %> <%= command.id %>",
-        "Create an agent test and use flags to specify all required information; if a test with same API name already exists in the org, overwrite it without confirmation. Use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --force-overwrite --target-org my-org",
-        "Preview what the agent test metadata (AiEvaluationDefinition) looks like without deploying it to your default org:\n<%= config.bin %> <%= command.id %> --spec specs/Resort_Manager-testSpec.yaml --api-name Resort_Manager_Test --preview"
+        "Resume an agent test in your default org using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 4KBfake0000003F4AQ",
+        "Resume the most recently-run agent test in an org with alias \"my-org\" org; wait 10 minutes for the tests to finish:\n<%= config.bin %> <%= command.id %> --use-most-recent --wait 10 --target-org my-org",
+        "Resume the most recent agent test in your default org, and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --use-most-recent --output-dir ./test-results --result-format json"
       ],
       "flags": {
         "json": {
@@ -821,20 +638,6 @@
           "multiple": false,
           "type": "option"
         },
-        "api-name": {
-          "name": "api-name",
-          "summary": "API name of the new test; the API name must not exist in the org.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "spec": {
-          "name": "spec",
-          "summary": "Path to the test spec YAML file.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "target-org": {
           "char": "o",
           "name": "target-org",
@@ -852,27 +655,69 @@
           "multiple": false,
           "type": "option"
         },
-        "preview": {
-          "name": "preview",
-          "summary": "Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.",
+        "job-id": {
+          "char": "i",
+          "name": "job-id",
+          "summary": "Job ID of the original agent test run.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "use-most-recent": {
+          "char": "r",
+          "name": "use-most-recent",
+          "summary": "Use the job ID of the most recent agent test run.",
           "allowNo": false,
           "type": "boolean"
         },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Don't prompt for confirmation when overwriting an existing test (based on API name) in your org.",
+        "wait": {
+          "char": "w",
+          "name": "wait",
+          "summary": "Number of minutes to wait for the command to complete and display results to the terminal window.",
+          "default": "5 minutes",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "result-format": {
+          "name": "result-format",
+          "summary": "Format of the agent test run results.",
+          "default": "human",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "json",
+            "human",
+            "junit",
+            "tap"
+          ],
+          "type": "option"
+        },
+        "output-dir": {
+          "char": "d",
+          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
+          "name": "output-dir",
+          "summary": "Directory to write the agent test results into.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "verbose": {
+          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
+          "name": "verbose",
+          "summary": "Show generated data in the test results output.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:create",
+      "id": "agent:test:resume",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Create an agent test in your org using a local test spec YAML file.",
+      "summary": "Resume an agent test that you previously started in your org so you can view the test results.",
       "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
@@ -880,25 +725,26 @@
         "commands",
         "agent",
         "test",
-        "create.js"
+        "resume.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:create",
-        "test:agent:create",
-        "test:create:agent",
-        "agent:create:test",
-        "create:agent:test",
-        "create:test:agent"
+        "agent:test:resume",
+        "test:agent:resume",
+        "test:resume:agent",
+        "agent:resume:test",
+        "resume:agent:test",
+        "resume:test:agent"
       ]
     },
-    "agent:test:list": {
+    "agent:test:run": {
       "aliases": [],
       "args": {},
-      "description": "The command outputs a table with the name (API name) of each test along with its unique ID and the date it was created in the org.",
+      "description": "Use the --api-name flag to specify the name of the agent test you want to run. Use the output of the \"agent test list\" command to get the names of all the available agent tests in your org.\n\nBy default, this command starts the agent test in your org, but it doesn't wait for the test to finish. Instead, it displays the \"agent test resume\" command, with a job ID, that you execute to see the results of the test run, and then returns control of the terminal window to you. Use the --wait flag to specify the number of minutes for the command to wait for the agent test to complete; if the test completes by the end of the wait time, the command displays the test results. If not, run \"agent test resume\".\n\nBy default, this command outputs test results in human-readable tables for each test case, if the test completes in time. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
       "examples": [
-        "List the agent tests in your default org:\n<%= config.bin %> <%= command.id %>",
-        "List the agent tests in an org with alias \"my-org\"\"\n<%= config.bin %> <%= command.id %> --target-org my-org"
+        "Start an agent test called Resort_Manager_Test for an agent in your default org, don't wait for the test to finish:\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test",
+        "Start an agent test for an agent in an org with alias \"my-org\" and wait for 10 minutes for the test to finish:\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test --wait 10 --target-org my-org",
+        "Start an agent test and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test --wait 10 --output-dir ./test-results --result-format json"
       ],
       "flags": {
         "json": {
@@ -932,16 +778,62 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "API name of the agent test to run; corresponds to the name of the AiEvaluationDefinition metadata component that implements the agent test.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "wait": {
+          "char": "w",
+          "name": "wait",
+          "summary": "Number of minutes to wait for the command to complete and display results to the terminal window.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "result-format": {
+          "name": "result-format",
+          "summary": "Format of the agent test run results.",
+          "default": "human",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "json",
+            "human",
+            "junit",
+            "tap"
+          ],
+          "type": "option"
+        },
+        "output-dir": {
+          "char": "d",
+          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
+          "name": "output-dir",
+          "summary": "Directory to write the agent test results into.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "verbose": {
+          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
+          "name": "verbose",
+          "summary": "Show generated data in the test results output.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:list",
+      "id": "agent:test:run",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "List the available agent tests in your org.",
+      "summary": "Start an agent test in your org.",
       "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
@@ -949,26 +841,25 @@
         "commands",
         "agent",
         "test",
-        "list.js"
+        "run.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:list",
-        "test:agent:list",
-        "test:list:agent",
-        "agent:list:test",
-        "list:agent:test",
-        "list:test:agent"
+        "agent:test:run",
+        "test:agent:run",
+        "test:run:agent",
+        "agent:run:test",
+        "run:agent:test",
+        "run:test:agent"
       ]
     },
-    "agent:test:results": {
+    "agent:publish:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "This command requires a job ID, which the original \"agent test run\" command displays when it completes. You can also use the --use-most-recent flag to see results for the most recently run agent test.\n\nBy default, this command outputs test results in human-readable tables for each test case. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
+      "description": "An authoring bundle is a metadata type (named aiAuthoringBundle) that provides the blueprint for an agent. The metadata type contains two files: the standard metatada XML file and an Agent Script file (extension \".agent\") that fully describes the agent using the Agent Script language.\n\nWhen you publish an authoring bundle to your org, a number of things happen. First, this command validates that the Agent Script file successfully compiles. If there are compilation errors, the command exits and you must fix the Agent Script file to continue. Once the Agent Script file compiles, then it's published to the org, which in turn creates new associated metadata (Bot, BotVersion, GenAiX), or new versions of the metadata if the agent already exists. The new or updated metadata is retrieved back to your DX project; specify the --skip-retrieve flag to skip this step. Finally, the authoring bundle metadata (AiAuthoringBundle) is deployed to your org.\n\nThis command uses the API name of the authoring bundle.",
       "examples": [
-        "Get the results of an agent test run in your default org using its job ID:\n<%= config.bin %> <%= command.id %> --job-id 4KBfake0000003F4AQ",
-        "Get the results of the most recently run agent test in an org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --use-most-recent --target-org my-org",
-        "Get the results of the most recently run agent test in your default org, and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --use-most-recent --output-dir ./test-results --result-format json"
+        "Publish an authoring bundle by being prompted for its API name; use your default org:\n<%= config.bin %> <%= command.id %>",
+        "Publish an authoring bundle with API name MyAuthoringBundle to the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --target-org my-dev-org"
       ],
       "flags": {
         "json": {
@@ -1003,81 +894,65 @@
           "multiple": false,
           "type": "option"
         },
-        "job-id": {
-          "char": "i",
-          "name": "job-id",
-          "required": true,
-          "summary": "Job ID of the completed agent test run.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "result-format": {
-          "name": "result-format",
-          "summary": "Format of the agent test run results.",
-          "default": "human",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "options": [
-            "json",
-            "human",
-            "junit",
-            "tap"
-          ],
-          "type": "option"
-        },
-        "output-dir": {
-          "char": "d",
-          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
-          "name": "output-dir",
-          "summary": "Directory to write the agent test results into.",
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "API name of the authoring bundle you want to publish; if not specified, the command provides a list that you can choose from.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "verbose": {
-          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
-          "name": "verbose",
-          "summary": "Show generated data in the test results output.",
+        "skip-retrieve": {
+          "name": "skip-retrieve",
+          "summary": "Don't retrieve the metadata associated with the agent to your DX project.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:results",
+      "id": "agent:publish:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Get the results of a completed agent test run.",
+      "summary": "Publish an authoring bundle to your org, which results in a new agent or a new version of an existing agent.",
       "enableJsonFlag": true,
+      "requiresProject": true,
+      "FLAGGABLE_PROMPTS": {
+        "api-name": {
+          "message": "API name of the authoring bundle you want to publish; if not specified, the command provides a list that you can choose from.",
+          "promptMessage": "API name of the authoring bundle to publish"
+        }
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "results.js"
+        "publish",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:results",
-        "test:agent:results",
-        "test:results:agent",
-        "agent:results:test",
-        "results:agent:test",
-        "results:test: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"
       ]
     },
-    "agent:test:resume": {
+    "agent:generate:agent-spec": {
       "aliases": [],
       "args": {},
-      "description": "This command requires a job ID, which the original \"agent test run\" command displays when it completes. You can also use the --use-most-recent flag to see results for the most recently run agent test.\n\nUse the --wait flag to specify the number of minutes for this command to wait for the agent test to complete; if the test completes by the end of the wait time, the command displays the test results. If not, the CLI returns control of the terminal to you, and you must run \"agent test resume\" again.\n\nBy default, this command outputs test results in human-readable tables for each test case. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
+      "description": "An agent spec is a YAML-formatted file that contains basic information about the agent, such as its role, company description, and an AI-generated list of topics based on this information. Topics define the range of jobs your agent can handle.\n\nUse flags, such as --role and --company-description, to provide details about your company and the role that the agent plays in your company. If you prefer, you can also be prompted for the basic information; use --full-interview to be prompted for all required and optional properties. Upon command execution, the large language model (LLM) associated with your org uses the provided information to generate a list of topics for the agent. Because the LLM uses the company and role information to generate the topics, we recommend that you provide accurate, complete, and specific details so the LLM generates the best and most relevant topics. Once generated, you can edit the spec file; for example, you can remove topics that don't apply or change a topic's description.\n\nYou can also iterate the spec generation process by using the --spec flag to pass an existing agent spec file to this command, and then using the --role, --company-description, etc, flags to refine your agent properties. Iteratively improving the description of your agent allows the LLM to generate progressively better topics.\n\nYou can also specify other agent properties, such as a custom prompt template, how to ground the prompt template to add context to the agent's prompts, the tone of the prompts, and the username of a user in the org to assign to the agent.\n\nWhen your agent spec is ready, generate an authoring bundle from it by passing the spec file to the --spec flag of the \"agent generate authoring-bundle\" CLI command. An authoring bundle is a metadata type that contains an Agent Script file, which is the blueprint for an agent. (While not recommended, you can also use the agent spec file to immediately create an agent with the \"agent create\" command. We don't recommend this workflow because these types of agents don't use Agent Script, and are thus less flexible and more difficult to maintain.)",
       "examples": [
-        "Resume an agent test in your default org using a job ID:\n<%= config.bin %> <%= command.id %> --job-id 4KBfake0000003F4AQ",
-        "Resume the most recently-run agent test in an org with alias \"my-org\" org; wait 10 minutes for the tests to finish:\n<%= config.bin %> <%= command.id %> --use-most-recent --wait 10 --target-org my-org",
-        "Resume the most recent agent test in your default org, and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --use-most-recent --output-dir ./test-results --result-format json"
+        "Generate an agent spec in the default location and use flags to specify the agent properties, such as its role and your company details; use your default org:\n<%= config.bin %> <%= command.id %> --type customer --role \"Field customer complaints and manage employee schedules.\" --company-name \"Coral Cloud Resorts\" --company-description \"Provide customers with exceptional destination activities, unforgettable experiences, and reservation services.\"",
+        "Generate an agent spec by being prompted for the required agent properties and generate a maxiumum of 5 topics; write the generated file to the \"specs/resortManagerSpec.yaml\" file and use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --max-topics 5 --output-file specs/resortManagerAgent.yaml --target-org my-org",
+        "Be prompted for all required and optional agent properties; use your default org:\n<%= config.bin %> <%= command.id %> --full-interview",
+        "Specify an existing agent spec file called \"specs/resortManagerAgent.yaml\", and then overwrite it with a new version that contains newly AI-generated topics based on the updated role information passed in with the --role flag:\n<%= config.bin %> <%= command.id %> --spec specs/resortManagerAgent.yaml --output-file specs/resortManagerAgent.yaml --role \"Field customer complaints, manage employee schedules, and ensure all resort operations are running smoothly\"",
+        "Specify that the conversational tone of the agent is formal and to attach the \"resortmanager@myorg.com\" username to it; be prompted for the required properties and use your default org:\n<%= config.bin %> <%= command.id %> --tone formal --agent-user resortmanager@myorg.com"
       ],
       "flags": {
         "json": {
@@ -1112,96 +987,163 @@
           "multiple": false,
           "type": "option"
         },
-        "job-id": {
-          "char": "i",
-          "name": "job-id",
-          "summary": "Job ID of the original agent test run.",
+        "type": {
+          "name": "type",
+          "summary": "Type of agent to create. Internal types are copilots used internally by your company and customer types are the agents you create for your customers.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "customer",
+            "internal"
+          ],
           "type": "option"
         },
-        "use-most-recent": {
-          "char": "r",
-          "name": "use-most-recent",
-          "summary": "Use the job ID of the most recent agent test run.",
-          "allowNo": false,
-          "type": "boolean"
+        "role": {
+          "name": "role",
+          "summary": "Role of the agent.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "wait": {
-          "char": "w",
-          "name": "wait",
-          "summary": "Number of minutes to wait for the command to complete and display results to the terminal window.",
-          "default": "5 minutes",
-          "hasDynamicHelp": true,
+        "company-name": {
+          "name": "company-name",
+          "summary": "Name of your company.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "result-format": {
-          "name": "result-format",
-          "summary": "Format of the agent test run results.",
-          "default": "human",
+        "company-description": {
+          "name": "company-description",
+          "summary": "Description of your company.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "company-website": {
+          "name": "company-website",
+          "summary": "Website URL of your company.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "max-topics": {
+          "name": "max-topics",
+          "summary": "Maximum number of topics to generate in the agent spec; default is 5.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "agent-user": {
+          "name": "agent-user",
+          "summary": "Username of a user in your org to assign to your agent; determines what your agent can access and do.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "enrich-logs": {
+          "name": "enrich-logs",
+          "summary": "Adds agent conversation data to event logs so you can view all agent session activity in one place.",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "json",
-            "human",
-            "junit",
-            "tap"
+            "true",
+            "false"
           ],
           "type": "option"
         },
-        "output-dir": {
-          "char": "d",
-          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
-          "name": "output-dir",
-          "summary": "Directory to write the agent test results into.",
+        "tone": {
+          "name": "tone",
+          "summary": "Conversational style of the agent, such as how it expresses your brand personality in its messages through word choice, punctuation, and sentence structure.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "formal",
+            "casual",
+            "neutral"
+          ],
           "type": "option"
         },
-        "verbose": {
-          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
-          "name": "verbose",
-          "summary": "Show generated data in the test results output.",
+        "spec": {
+          "name": "spec",
+          "summary": "Agent spec file, in YAML format, to use as input to the command.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "output-file": {
+          "name": "output-file",
+          "summary": "Path for the generated YAML agent spec file; can be an absolute or relative path.",
+          "default": "specs/agentSpec.yaml",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "full-interview": {
+          "name": "full-interview",
+          "summary": "Prompt for both required and optional flags.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "prompt-template": {
+          "name": "prompt-template",
+          "summary": "API name of a customized prompt template to use instead of the default prompt template.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "grounding-context": {
+          "dependsOn": [
+            "prompt-template"
+          ],
+          "name": "grounding-context",
+          "summary": "Context information and personalization that's added to your prompts when using a custom prompt template.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Don't prompt the user to confirm that an existing spec file will be overwritten.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:resume",
+      "id": "agent:generate:agent-spec",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Resume an agent test that you previously started in your org so you can view the test results.",
+      "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "resume.js"
+        "generate",
+        "agent-spec.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:resume",
-        "test:agent:resume",
-        "test:resume:agent",
-        "agent:resume:test",
-        "resume:agent:test",
-        "resume:test:agent"
+        "agent:generate:agent-spec",
+        "generate:agent:agent-spec",
+        "generate:agent-spec:agent",
+        "agent:agent-spec:generate",
+        "agent-spec:agent:generate",
+        "agent-spec:generate:agent"
       ]
     },
-    "agent:test:run": {
+    "agent:generate:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "Use the --api-name flag to specify the name of the agent test you want to run. Use the output of the \"agent test list\" command to get the names of all the available agent tests in your org.\n\nBy default, this command starts the agent test in your org, but it doesn't wait for the test to finish. Instead, it displays the \"agent test resume\" command, with a job ID, that you execute to see the results of the test run, and then returns control of the terminal window to you. Use the --wait flag to specify the number of minutes for the command to wait for the agent test to complete; if the test completes by the end of the wait time, the command displays the test results. If not, run \"agent test resume\".\n\nBy default, this command outputs test results in human-readable tables for each test case, if the test completes in time. The tables show whether the test case passed, the expected and actual values, the test score, how long the test took, and more. Use the --result-format to display the test results in JSON or Junit format. Use the --output-dir flag to write the results to a file rather than to the terminal.",
+      "description": "Authoring bundles are metadata components that contain an agent's Agent Script file. The Agent Script file is the agent's blueprint; it fully describes what the agent can do using the Agent Script language.\n\nUse this command to generate a new authoring bundle based on an agent spec YAML file, which you create with the \"agent generate agent-spec\" command. The agent spec YAML file is a high-level description of the agent; it describes its essence rather than exactly what it can do.\n\nThe metadata type for authoring bundles is aiAuthoringBundle, which consist of a standard \"<bundle-api-name>.bundle-meta.xml\" metadata file and the Agent Script file (with extension \".agent\"). When you run this command, the new authoring bundle is generated in the force-app/main/default/aiAuthoringBundles/<bundle-api-name> directory. Use the --output-dir flag to generate them elsewhere.\n\nAfter you generate the initial authoring bundle, code the Agent Script file so your agent behaves exactly as you want. The Agent Script file generated by this command is just a first draft of your agent! Interactively test the agent by conversing with it using the \"agent preview\" command. Then publish the agent to your org with the \"agent publish authoring-bundle\" command.\n\nThis command requires an org because it uses it to access an LLM for generating the Agent Script file.",
       "examples": [
-        "Start an agent test called Resort_Manager_Test for an agent in your default org, don't wait for the test to finish:\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test",
-        "Start an agent test for an agent in an org with alias \"my-org\" and wait for 10 minutes for the test to finish:\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test --wait 10 --target-org my-org",
-        "Start an agent test and write the JSON-formatted results into a directory called \"test-results\":\n<%= config.bin %> <%= command.id %> --api-name Resort_Manager_Test --wait 10 --output-dir ./test-results --result-format json"
+        "Generate an authoring bundle by being prompted for all required values, such as the agent spec YAML file, the bundle name, and the API name; use your default org:\n<%= config.bin %> <%= command.id %>",
+        "Generate an authoring bundle from the \"specs/agentSpec.yaml\" agent spec YAML file and give it the label \"My Authoring Bundle\"; use your default org:\n<%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name \"My Authoring Bundle\"",
+        "Similar to previous example, but generate the authoring bundle files in the \"other-package-dir/main/default\" package directory; use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --spec specs/agentSpec.yaml --name \"My Authoring Bundle\" --output-dir other-package-dir/main/default --target-org my-dev-org"
       ],
       "flags": {
         "json": {
@@ -1229,94 +1171,95 @@
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "api-name": {
-          "char": "n",
           "name": "api-name",
-          "summary": "API name of the agent test to run; corresponds to the name of the AiEvaluationDefinition metadata component that implements the agent test.",
+          "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"
         },
-        "wait": {
-          "char": "w",
-          "name": "wait",
-          "summary": "Number of minutes to wait for the command to complete and display results to the terminal window.",
-          "hasDynamicHelp": true,
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "result-format": {
-          "name": "result-format",
-          "summary": "Format of the agent test run results.",
-          "default": "human",
+        "spec": {
+          "char": "f",
+          "name": "spec",
+          "summary": "Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "json",
-            "human",
-            "junit",
-            "tap"
-          ],
           "type": "option"
         },
         "output-dir": {
           "char": "d",
-          "description": "If the agent test run completes, write the results to the specified directory. If the test is still running, the test results aren't written.",
           "name": "output-dir",
-          "summary": "Directory to write the agent test results into.",
+          "summary": "Directory where the authoring bundle files are generated.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "verbose": {
-          "description": "When enabled, includes detailed generated data (such as invoked actions) in the human-readable test results output. This is useful for debugging test failures and understanding what actions were actually invoked during the test run.\n\nThe generated data is in JSON format and includes the Apex classes or Flows that were invoked, the Salesforce objects that were touched, and so on. Use the JSON structure of this information to build the test case JSONPath expression when using custom evaluations.",
-          "name": "verbose",
-          "summary": "Show generated data in the test results output.",
-          "allowNo": false,
-          "type": "boolean"
+        "name": {
+          "char": "n",
+          "name": "name",
+          "summary": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:run",
+      "id": "agent:generate:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Start an agent test in your org.",
+      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
       "enableJsonFlag": true,
+      "requiresProject": true,
+      "FLAGGABLE_PROMPTS": {
+        "name": {
+          "message": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
+          "promptMessage": "Name (label) of the authoring bundle",
+          "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 can't exist in the org.",
+          "promptMessage": "API name of the new authoring bundle"
+        },
+        "spec": {
+          "message": "Path to the agent spec YAML file; if not specified, the command provides a list that you can choose from.",
+          "promptMessage": "Path to the agent spec YAML file",
+          "required": true
+        }
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "run.js"
+        "generate",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:run",
-        "test:agent:run",
-        "test:run:agent",
-        "agent:run:test",
-        "run:agent:test",
-        "run:test:agent"
+        "agent:generate:authoring-bundle",
+        "generate:agent:authoring-bundle",
+        "generate:authoring-bundle:agent",
+        "agent:authoring-bundle:generate",
+        "authoring-bundle:agent:generate",
+        "authoring-bundle:generate:agent"
       ]
     },
-    "agent:validate:authoring-bundle": {
+    "agent:generate:template": {
       "aliases": [],
       "args": {},
-      "description": "An authoring bundle is a metadata type (named aiAuthoringBundle) that provides the blueprint for an agent. The metadata type contains two files: the standard metatada XML file and an Agent Script file (extension \".agent\") that fully describes the agent using the Agent Script language.\n\nThis command validates that the Agent Script file in the authoring bundle compiles without errors so that you can later publish the bundle to your org. Use this command while you code the Agent Script file to ensure that it's valid. If the validation fails, the command outputs the list of syntax errors, a brief description of the error, and the location in the Agent Script file where the error occurred.\n\nThis command uses the API name of the authoring bundle. If you don't provide an API name with the --api-name flag, the command searches the current DX project and outputs a list of authoring bundles that it found for you to choose from.",
+      "description": "At a high-level, agents are defined by the Bot, BotVersion, and GenAiPlannerBundle metadata types. The GenAiPlannerBundle type in turn defines the agent's topics and actions. This command uses the metadata files for these three types, located in your local DX project, to generate a BotTemplate file for a specific agent (Bot). You then use the BotTemplate file, along with the GenAiPlannerBundle file that references the BotTemplate, to package the template in a managed package that you can share between orgs or on AppExchange.\n\nUse the --agent-file flag to specify the relative or full pathname of the Bot metadata file, such as force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml. A single Bot can have multiple BotVersions, so use the --agent-version flag to specify the version. The corresponding BotVersion file must exist locally. For example, if you specify \"--agent-version 4\", then the file force-app/main/default/bots/My_Awesome_Agent/v4.botVersion-meta.xml must exist.\n\nThe new BotTemplate file is generated in the \"botTemplates\" directory in your local package directory, and has the name <Agent_API_name>_v<Version>_Template.botTemplate-meta.xml, such as force-app/main/default/botTemplates/My_Awesome_Agent_v4_Template.botTemplate-meta.xml. The command displays the full pathname of the generated files when it completes.",
       "examples": [
-        "Validate an authoring bundle by being prompted for its API name; use your default org:\n<%= config.bin %> <%= command.id %>",
-        "Validate an authoring bundle with API name MyAuthoringBundle; use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringBundle --target-org my-dev-org"
+        "Generate an agent template from a Bot metadata file in your DX project that corresponds to the My_Awesome_Agent agent; use version 1 of the agent.\n<%= config.bin %> <%= command.id %> --agent-file force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1"
       ],
       "flags": {
         "json": {
@@ -1334,16 +1277,6 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
-          "required": true,
-          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
-          "hasDynamicHelp": true,
-          "multiple": false,
-          "type": "option"
-        },
         "api-version": {
           "description": "Override the api version used for api requests made by this command",
           "name": "api-version",
@@ -1351,57 +1284,127 @@
           "multiple": false,
           "type": "option"
         },
-        "api-name": {
-          "char": "n",
-          "name": "api-name",
-          "summary": "API name of the authoring bundle you want to validate; if not specified, the command provides a list that you can choose from.",
+        "agent-version": {
+          "name": "agent-version",
+          "required": true,
+          "summary": "Version of the agent (BotVersion).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "agent-file": {
+          "char": "f",
+          "name": "agent-file",
+          "required": true,
+          "summary": "Path to an agent (Bot) metadata file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:validate:authoring-bundle",
+      "id": "agent:generate:template",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
-      "summary": "Validate an authoring bundle to ensure its Agent Script file compiles successfully and can be used to publish an agent.",
+      "summary": "Generate an agent template from an existing agent in your DX project so you can then package the template in a managed package.",
       "enableJsonFlag": true,
       "requiresProject": true,
-      "FLAGGABLE_PROMPTS": {
-        "api-name": {
-          "message": "API name of the authoring bundle you want to validate; if not specified, the command provides a list that you can choose from.",
-          "promptMessage": "API name of the authoring bundle to validate"
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "generate",
+        "template.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:generate:template",
+        "generate:agent:template",
+        "generate:template:agent",
+        "agent:template:generate",
+        "template:agent:generate",
+        "template:generate:agent"
+      ]
+    },
+    "agent:generate:test-spec": {
+      "aliases": [],
+      "args": {},
+      "description": "The first step when using Salesforce CLI to create an agent test in your org is to use this interactive command to generate a local YAML-formatted test spec file. The test spec YAML file contains information about the agent being tested, such as its API name, and then one or more test cases. This command uses the metadata components in your DX project when prompting for information, such as the agent API name; it doesn't look in your org.\n\nTo generate a specific agent test case, this command prompts you for this information; when possible, the command provides a list of options for you to choose from:\n\n- Utterance: Natural language statement, question, or command used to test the agent.\n- Expected topic: API name of the topic you expect the agent to use when responding to the utterance.\n- Expected actions: One or more API names of the expection actions the agent takes.\n- Expected outcome: Natural language description of the outcome you expect.\n- (Optional) Custom evaluation: Test an agent's response for specific strings or numbers.\n- (Optional) Conversation history: Boilerplate for additional context you can add to the test in the form of a conversation history.\n\nWhen your test spec is ready, you then run the \"agent test create\" command to actually create the test in your org and synchronize the metadata with your DX project. The metadata type for an agent test is AiEvaluationDefinition.\n\nIf you have an existing AiEvaluationDefinition metadata XML file in your DX project, you can generate its equivalent YAML test spec file with the --from-definition flag.",
+      "examples": [
+        "Generate an agent test spec YAML file interactively:\n<%= config.bin %> <%= command.id %>",
+        "Generate an agent test spec YAML file and specify a name for the new file; if the file exists, overwrite it without confirmation:\n<%= config.bin %> <%= command.id %> --output-file specs/Resort_Manager-new-version-testSpec.yaml --force-overwrite",
+        "Generate an agent test spec YAML file from an existing AiEvaluationDefinition metadata XML file in your DX project:\n<%= config.bin %> <%= command.id %> --from-definition force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml"
+      ],
+      "flags": {
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "from-definition": {
+          "char": "d",
+          "name": "from-definition",
+          "summary": "Filepath to the AIEvaluationDefinition metadata XML file in your DX project that you want to convert to a test spec YAML file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Don't prompt for confirmation when overwriting an existing test spec YAML file.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "output-file": {
+          "char": "f",
+          "name": "output-file",
+          "summary": "Name of the generated test spec YAML file. Default value is \"specs/<AGENT_API_NAME>-testSpec.yaml\".",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "agent:generate:test-spec",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.",
+      "enableJsonFlag": false,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "validate",
-        "authoring-bundle.js"
+        "generate",
+        "test-spec.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:generate:test-spec",
+        "generate:agent:test-spec",
+        "generate:test-spec:agent",
+        "agent:test-spec:generate",
+        "test-spec:agent:generate",
+        "test-spec:generate:agent"
       ]
     },
-    "agent:publish:authoring-bundle": {
+    "agent:validate:authoring-bundle": {
       "aliases": [],
       "args": {},
-      "description": "An authoring bundle is a metadata type (named aiAuthoringBundle) that provides the blueprint for an agent. The metadata type contains two files: the standard metatada XML file and an Agent Script file (extension \".agent\") that fully describes the agent using the Agent Script language.\n\nWhen you publish an authoring bundle to your org, a number of things happen. First, this command validates that the Agent Script file successfully compiles. If there are compilation errors, the command exits and you must fix the Agent Script file to continue. Once the Agent Script file compiles, then it's published to the org, which in turn creates new associated metadata (Bot, BotVersion, GenAiX), or new versions of the metadata if the agent already exists. The new or updated metadata is retrieved back to your DX project; specify the --skip-retrieve flag to skip this step. Finally, the authoring bundle metadata (AiAuthoringBundle) is deployed to your org.\n\nThis command uses the API name of the authoring bundle.",
+      "description": "An authoring bundle is a metadata type (named aiAuthoringBundle) that provides the blueprint for an agent. The metadata type contains two files: the standard metatada XML file and an Agent Script file (extension \".agent\") that fully describes the agent using the Agent Script language.\n\nThis command validates that the Agent Script file in the authoring bundle compiles without errors so that you can later publish the bundle to your org. Use this command while you code the Agent Script file to ensure that it's valid. If the validation fails, the command outputs the list of syntax errors, a brief description of the error, and the location in the Agent Script file where the error occurred.\n\nThis command uses the API name of the authoring bundle. If you don't provide an API name with the --api-name flag, the command searches the current DX project and outputs a list of authoring bundles that it found for you to choose from.",
       "examples": [
-        "Publish an authoring bundle by being prompted for its API name; use your default org:\n<%= config.bin %> <%= command.id %>",
-        "Publish an authoring bundle with API name MyAuthoringBundle to the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --target-org my-dev-org"
+        "Validate an authoring bundle by being prompted for its API name; use your default org:\n<%= config.bin %> <%= command.id %>",
+        "Validate an authoring bundle with API name MyAuthoringBundle; use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringBundle --target-org my-dev-org"
       ],
       "flags": {
         "json": {
@@ -1439,33 +1442,26 @@
         "api-name": {
           "char": "n",
           "name": "api-name",
-          "summary": "API name of the authoring bundle you want to publish; if not specified, the command provides a list that you can choose from.",
+          "summary": "API name of the authoring bundle you want to validate; if not specified, the command provides a list that you can choose from.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "skip-retrieve": {
-          "name": "skip-retrieve",
-          "summary": "Don't retrieve the metadata associated with the agent to your DX project.",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:publish:authoring-bundle",
+      "id": "agent:validate:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
-      "summary": "Publish an authoring bundle to your org, which results in a new agent or a new version of an existing agent.",
+      "summary": "Validate an authoring bundle to ensure its Agent Script file compiles successfully and can be used to publish an agent.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "FLAGGABLE_PROMPTS": {
         "api-name": {
-          "message": "API name of the authoring bundle you want to publish; if not specified, the command provides a list that you can choose from.",
-          "promptMessage": "API name of the authoring bundle to publish"
+          "message": "API name of the authoring bundle you want to validate; if not specified, the command provides a list that you can choose from.",
+          "promptMessage": "API name of the authoring bundle to validate"
         }
       },
       "isESM": true,
@@ -1473,19 +1469,19 @@
         "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"
       ]
     }
   },
-  "version": "1.27.1"
+  "version": "1.27.3"
 }