@salesforce/plugin-agent 1.32.12 → 1.32.14

package/oclif.manifest.json

@@ -816,13 +816,14 @@
         "test-spec:generate:agent"
       ]
     },
-    "agent:publish:authoring-bundle": {
+    "agent:preview:end": {
       "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": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to end it. This command also displays the local directory where the session trace files are stored. \n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to end the session.  You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
       "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"
+        "End a preview session of a published agent by specifying its session ID and API name ; use the default org:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --api-name My_Published_Agent",
+        "Similar to previous example, but don't specify a session ID; you get an error if the published agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent --target-org my-dev-org",
+        "End a preview session of an agent using its authoring bundle API name; you get an error if the agent has more than one active session.\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Local_Agent"
       ],
       "flags": {
         "json": {
@@ -857,63 +858,66 @@
           "multiple": false,
           "type": "option"
         },
+        "session-id": {
+          "name": "session-id",
+          "required": false,
+          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see the list of all sessions.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
         "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 activated published agent you want to preview.",
           "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"
+        "authoring-bundle": {
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:publish:authoring-bundle",
+      "id": "agent:preview:end",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "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": "End an existing programmatic agent preview session and get trace location.",
       "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",
-        "publish",
-        "authoring-bundle.js"
+        "preview",
+        "end.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:preview:end",
+        "preview:agent:end",
+        "preview:end:agent",
+        "agent:end:preview",
+        "end:agent:preview",
+        "end:preview:agent"
       ]
     },
-    "agent:test:create": {
+    "agent:preview:send": {
       "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": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to send the agent a message (utterance). This command then displays the agent's response.\n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to send a message.  You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
       "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"
+        "Send a message to an activated published agent using its API name and session ID; use the default org:\n<%= config.bin %> <%= command.id %> --utterance \"What can you help me with?\" --api-name My_Published_Agent --session-id <SESSION_ID>",
+        "Similar to previous example, but don't specify a session ID; you get an error if the agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --utterance \"What can you help me with?\" --api-name My_Published_Agent --target-org my-dev-org",
+        "Send a message to an agent using its authoring bundle API name; you get an error if the agent has more than one active session:\n<%= config.bin %> <%= command.id %> --utterance \"what can you help me with?\" --authoring-bundle My_Local_Agent"
       ],
       "flags": {
         "json": {
@@ -931,20 +935,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",
@@ -962,53 +952,73 @@
           "multiple": false,
           "type": "option"
         },
-        "preview": {
-          "name": "preview",
-          "summary": "Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.",
-          "allowNo": false,
-          "type": "boolean"
+        "session-id": {
+          "name": "session-id",
+          "required": false,
+          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see list of all sessions.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Don't prompt for confirmation when overwriting an existing test (based on API name) in your org.",
-          "allowNo": false,
-          "type": "boolean"
+        "utterance": {
+          "char": "u",
+          "name": "utterance",
+          "required": true,
+          "summary": "Utterance to send to the agent, enclosed in double quotes.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "API name of the activated published agent you want to preview.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "authoring-bundle": {
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:create",
+      "id": "agent:preview:send",
       "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": "Send a message to an existing agent preview session.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "create.js"
+        "preview",
+        "send.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:create",
-        "test:agent:create",
-        "test:create:agent",
-        "agent:create:test",
-        "create:agent:test",
-        "create:test:agent"
+        "agent:preview:send",
+        "preview:agent:send",
+        "preview:send:agent",
+        "agent:send:preview",
+        "send:agent:preview",
+        "send:preview:agent"
       ]
     },
-    "agent:test:list": {
+    "agent:preview:sessions": {
       "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": "This command lists the agent preview sessions that were started with the \"agent preview start\" command and are still in the local cache. Use this command to discover specific session IDs that you can pass to the \"agent preview send\" or \"agent preview end\" commands with the --session-id flag.\n\nProgrammatic agent preview sessions can be started for both published activated agents and by using an agent's local authoring bundle, which contains its Agent Script file.  In this command's output table, the Agent column contains either the API name of the authoring bundle or the published agent, whichever was used when starting the session. In the table, if the same API name has multiple rows with different session IDs, then it means that you previously started multiple preview sessions with the associated agent.",
       "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"
+        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
       ],
       "flags": {
         "json": {
@@ -1025,60 +1035,44 @@
           "hasDynamicHelp": false,
           "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",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:test:list",
+      "id": "agent:preview:sessions",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "List the available agent tests in your org.",
+      "summary": "List all known programmatic agent preview sessions.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "list.js"
+        "preview",
+        "sessions.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:list",
-        "test:agent:list",
-        "test:list:agent",
-        "agent:list:test",
-        "list:agent:test",
-        "list:test:agent"
+        "agent:preview:sessions",
+        "preview:agent:sessions",
+        "preview:sessions:agent",
+        "agent:sessions:preview",
+        "sessions:agent:preview",
+        "sessions:preview:agent"
       ]
     },
-    "agent:test:results": {
+    "agent:preview:start": {
       "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": "This command outputs a session ID that you then use with the \"agent preview send\" command to send an utterance to the agent.  Use the \"agent preview sessions\" command to list all active sessions and the \"agent preview end\" command to end a specific session.\n\nIdentify the agent you want to start previewing with either the --authoring-bundle flag to specify a local authoring bundle's API name or --api-name to specify an activated published agent's API name.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory. \n\nWhen starting a preview session using the authoring bundle, which contains the agent's Agent Script file, the preview uses mocked actions by default.  Specify --use-live-actions for live mode, which uses the real Apex classes, flows, etc, in the org for the actions.",
       "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"
+        "Start a programmatic agent preview session by specifying an authoring bundle; uses mocked actions by default. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --target-org my-dev-org",
+        "Similar to previous example but use live actions and the default org:\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --use-live-actions",
+        "Start a preview session with an activated published agent:\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent"
       ],
       "flags": {
         "json": {
@@ -1113,81 +1107,63 @@
           "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",
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "API name of the activated published agent you want to preview.",
           "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.",
+        "authoring-bundle": {
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
           "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.",
+        "use-live-actions": {
+          "name": "use-live-actions",
+          "summary": "Use real actions in the org; if not specified, preview uses AI to simulate (mock) actions.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:results",
+      "id": "agent:preview:start",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Get the results of a completed agent test run.",
+      "summary": "Start a programmatic agent preview session.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "results.js"
+        "preview",
+        "start.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:results",
-        "test:agent:results",
-        "test:results:agent",
-        "agent:results:test",
-        "results:agent:test",
-        "results:test:agent"
-      ]
-    },
-    "agent:test:resume": {
-      "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.",
+        "agent:preview:start",
+        "preview:agent:start",
+        "preview:start:agent",
+        "agent:start:preview",
+        "start:agent:preview",
+        "start:preview:agent"
+      ]
+    },
+    "agent:publish: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.",
       "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"
+        "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": {
@@ -1222,99 +1198,63 @@
           "multiple": false,
           "type": "option"
         },
-        "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"
-        },
-        "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.",
+        "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:resume",
+      "id": "agent:publish:authoring-bundle",
       "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": "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",
-        "resume.js"
+        "publish",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:resume",
-        "test:agent:resume",
-        "test:resume:agent",
-        "agent:resume:test",
-        "resume:agent:test",
-        "resume: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:run-eval": {
+    "agent:test:create": {
       "aliases": [],
       "args": {},
-      "description": "Execute rich evaluation tests against an Agentforce agent using the Einstein Evaluation API. Supports both YAML test specs (same format as `sf agent generate test-spec`) and JSON payloads.\n\nWhen you provide a YAML test spec, the command automatically translates test cases into Evaluation API calls and infers the agent name from the spec's `subjectName` field. This means you can use the same test spec with both `sf agent test run` and `sf agent test run-eval`. YAML test specs also support contextVariables, which allow you to inject contextual data (such as CaseId or RoutableId) into agent sessions for testing with different contexts.\n\nWhen you provide a JSON payload, it's sent directly to the API with optional normalization. The normalizer auto-corrects common field name mistakes, converts shorthand references to JSONPath, and injects defaults. Use `--no-normalize` to disable this auto-normalization. JSON payloads can also include context_variables on agent.create_session steps for the same contextual testing capabilities.\n\nSupports 8+ evaluator types, including topic routing assertions, action invocation checks, string/numeric assertions, semantic similarity scoring, and LLM-based quality ratings.",
+      "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": [
-        "Run tests using a YAML test spec on the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --target-org my-org",
-        "Run tests using a YAML spec with explicit agent name override; use your default org:\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --api-name My_Agent --target-org my-org",
-        "Run tests using a JSON payload:\n<%= config.bin %> <%= command.id %> --spec tests/eval-payload.json --target-org my-org",
-        "Run tests and output results in JUnit format; useful for continuous integration and deployment (CI/CD):\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --target-org my-org --result-format junit",
-        "Run tests with contextVariables to inject contextual data into agent sessions (add contextVariables to test cases in your YAML spec):\n<%= config.bin %> <%= command.id %> --spec tests/agent-with-context.yaml --target-org my-org",
-        "Pipe JSON payload from stdin (--spec flag is automatically populated from stdin):\n$ echo '{\"tests\":[...]}' | <%= config.bin %> <%= command.id %> --spec --target-org my-org"
+        "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": {
@@ -1332,88 +1272,58 @@
           "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",
+        "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": {
-          "char": "s",
           "name": "spec",
-          "required": true,
-          "summary": "Path to test spec file (YAML or JSON). Supports reading from stdin when piping content.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "api-name": {
-          "char": "n",
-          "name": "api-name",
-          "summary": "Agent DeveloperName (also called API name) to resolve agent_id and agent_version_id. Auto-inferred from the YAML spec's subjectName.",
+          "summary": "Path to the test spec YAML file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "wait": {
-          "char": "w",
-          "name": "wait",
-          "summary": "Number of minutes to wait for results.",
-          "default": 10,
-          "hasDynamicHelp": false,
+        "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"
         },
-        "result-format": {
-          "name": "result-format",
-          "summary": "Format of the agent test run results.",
-          "default": "human",
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "json",
-            "human",
-            "junit",
-            "tap"
-          ],
           "type": "option"
         },
-        "batch-size": {
-          "name": "batch-size",
-          "summary": "Number of tests per API request (max 5).",
-          "default": 5,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
+        "preview": {
+          "name": "preview",
+          "summary": "Preview the test metadata file (AiEvaluationDefinition) without deploying to your org.",
+          "allowNo": false,
+          "type": "boolean"
         },
-        "no-normalize": {
-          "name": "no-normalize",
-          "summary": "Disable auto-normalization of field names and shorthand references.",
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Don't prompt for confirmation when overwriting an existing test (based on API name) in your org.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
-      "hidden": true,
       "hiddenAliases": [],
-      "id": "agent:test:run-eval",
+      "id": "agent:test:create",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
-      "summary": "Run evaluation tests against an Agentforce agent.",
+      "summary": "Create an agent test in your org using a local test spec YAML file.",
       "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
@@ -1421,26 +1331,25 @@
         "commands",
         "agent",
         "test",
-        "run-eval.js"
+        "create.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:run-eval",
-        "test:agent:run-eval",
-        "test:run-eval:agent",
-        "agent:run-eval:test",
-        "run-eval:agent:test",
-        "run-eval:test:agent"
+        "agent:test:create",
+        "test:agent:create",
+        "test:create:agent",
+        "agent:create:test",
+        "create:agent:test",
+        "create:test:agent"
       ]
     },
-    "agent:test:run": {
+    "agent:test:list": {
       "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": "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": [
-        "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"
+        "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": {
@@ -1474,62 +1383,16 @@
           "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:run",
+      "id": "agent:test:list",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Start an agent test in your org.",
+      "summary": "List the available agent tests in your org.",
       "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
@@ -1537,26 +1400,26 @@
         "commands",
         "agent",
         "test",
-        "run.js"
+        "list.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:run",
-        "test:agent:run",
-        "test:run:agent",
-        "agent:run:test",
-        "run:agent:test",
-        "run:test:agent"
+        "agent:test:list",
+        "test:agent:list",
+        "test:list:agent",
+        "agent:list:test",
+        "list:agent:test",
+        "list:test:agent"
       ]
     },
-    "agent:preview:end": {
+    "agent:test:results": {
       "aliases": [],
       "args": {},
-      "description": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to end it. This command also displays the local directory where the session trace files are stored. \n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to end the session.  You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
+      "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": [
-        "End a preview session of a published agent by specifying its session ID and API name ; use the default org:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --api-name My_Published_Agent",
-        "Similar to previous example, but don't specify a session ID; you get an error if the published agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent --target-org my-dev-org",
-        "End a preview session of an agent using its authoring bundle API name; you get an error if the agent has more than one active session.\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Local_Agent"
+        "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": {
@@ -1591,66 +1454,81 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "name": "session-id",
-          "required": false,
-          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see the list of all sessions.",
+        "job-id": {
+          "char": "i",
+          "name": "job-id",
+          "required": true,
+          "summary": "Job ID of the completed agent test run.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-name": {
-          "char": "n",
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
+        "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"
         },
-        "authoring-bundle": {
-          "name": "authoring-bundle",
-          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+        "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:preview:end",
+      "id": "agent:test:results",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "End an existing programmatic agent preview session and get trace location.",
+      "summary": "Get the results of a completed agent test run.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "end.js"
+        "test",
+        "results.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:end",
-        "preview:agent:end",
-        "preview:end:agent",
-        "agent:end:preview",
-        "end:agent:preview",
-        "end:preview:agent"
+        "agent:test:results",
+        "test:agent:results",
+        "test:results:agent",
+        "agent:results:test",
+        "results:agent:test",
+        "results:test:agent"
       ]
     },
-    "agent:preview:send": {
+    "agent:test:resume": {
       "aliases": [],
       "args": {},
-      "description": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to send the agent a message (utterance). This command then displays the agent's response.\n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to send a message.  You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
+      "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": [
-        "Send a message to an activated published agent using its API name and session ID; use the default org:\n<%= config.bin %> <%= command.id %> --utterance \"What can you help me with?\" --api-name My_Published_Agent --session-id <SESSION_ID>",
-        "Similar to previous example, but don't specify a session ID; you get an error if the agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --utterance \"What can you help me with?\" --api-name My_Published_Agent --target-org my-dev-org",
-        "Send a message to an agent using its authoring bundle API name; you get an error if the agent has more than one active session:\n<%= config.bin %> <%= command.id %> --utterance \"what can you help me with?\" --authoring-bundle My_Local_Agent"
+        "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": {
@@ -1685,73 +1563,99 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "name": "session-id",
-          "required": false,
-          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see list of all sessions.",
+        "job-id": {
+          "char": "i",
+          "name": "job-id",
+          "summary": "Job ID of the original agent test run.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "utterance": {
-          "char": "u",
-          "name": "utterance",
-          "required": true,
-          "summary": "Utterance to send to the agent, enclosed in double quotes.",
-          "hasDynamicHelp": false,
+        "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"
+        },
+        "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"
         },
-        "api-name": {
-          "char": "n",
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
+        "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"
         },
-        "authoring-bundle": {
-          "name": "authoring-bundle",
-          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+        "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:preview:send",
+      "id": "agent:test:resume",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Send a message to an existing agent preview session.",
+      "summary": "Resume an agent test that you previously started in your org so you can view the test results.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "send.js"
+        "test",
+        "resume.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:send",
-        "preview:agent:send",
-        "preview:send:agent",
-        "agent:send:preview",
-        "send:agent:preview",
-        "send:preview:agent"
+        "agent:test:resume",
+        "test:agent:resume",
+        "test:resume:agent",
+        "agent:resume:test",
+        "resume:agent:test",
+        "resume:test:agent"
       ]
     },
-    "agent:preview:sessions": {
+    "agent:test:run-eval": {
       "aliases": [],
       "args": {},
-      "description": "This command lists the agent preview sessions that were started with the \"agent preview start\" command and are still in the local cache. Use this command to discover specific session IDs that you can pass to the \"agent preview send\" or \"agent preview end\" commands with the --session-id flag.\n\nProgrammatic agent preview sessions can be started for both published activated agents and by using an agent's local authoring bundle, which contains its Agent Script file.  In this command's output table, the Agent column contains either the API name of the authoring bundle or the published agent, whichever was used when starting the session. In the table, if the same API name has multiple rows with different session IDs, then it means that you previously started multiple preview sessions with the associated agent.",
+      "description": "Execute rich evaluation tests against an Agentforce agent using the Einstein Evaluation API. Supports both YAML test specs (same format as `sf agent generate test-spec`) and JSON payloads.\n\nWhen you provide a YAML test spec, the command automatically translates test cases into Evaluation API calls and infers the agent name from the spec's `subjectName` field. This means you can use the same test spec with both `sf agent test run` and `sf agent test run-eval`. YAML test specs also support contextVariables, which allow you to inject contextual data (such as CaseId or RoutableId) into agent sessions for testing with different contexts.\n\nWhen you provide a JSON payload, it's sent directly to the API with optional normalization. The normalizer auto-corrects common field name mistakes, converts shorthand references to JSONPath, and injects defaults. Use `--no-normalize` to disable this auto-normalization. JSON payloads can also include context_variables on agent.create_session steps for the same contextual testing capabilities.\n\nSupports 8+ evaluator types, including topic routing assertions, action invocation checks, string/numeric assertions, semantic similarity scoring, and LLM-based quality ratings.",
       "examples": [
-        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
+        "Run tests using a YAML test spec on the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --target-org my-org",
+        "Run tests using a YAML spec with explicit agent name override; use your default org:\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --api-name My_Agent --target-org my-org",
+        "Run tests using a JSON payload:\n<%= config.bin %> <%= command.id %> --spec tests/eval-payload.json --target-org my-org",
+        "Run tests and output results in JUnit format; useful for continuous integration and deployment (CI/CD):\n<%= config.bin %> <%= command.id %> --spec tests/my-agent-testSpec.yaml --target-org my-org --result-format junit",
+        "Run tests with contextVariables to inject contextual data into agent sessions (add contextVariables to test cases in your YAML spec):\n<%= config.bin %> <%= command.id %> --spec tests/agent-with-context.yaml --target-org my-org",
+        "Pipe JSON payload from stdin (--spec flag is automatically populated from stdin):\n$ echo '{\"tests\":[...]}' | <%= config.bin %> <%= command.id %> --spec --target-org my-org"
       ],
       "flags": {
         "json": {
@@ -1768,44 +1672,116 @@
           "hasDynamicHelp": false,
           "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",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "spec": {
+          "char": "s",
+          "name": "spec",
+          "required": true,
+          "summary": "Path to test spec file (YAML or JSON). Supports reading from stdin when piping content.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "Agent DeveloperName (also called API name) to resolve agent_id and agent_version_id. Auto-inferred from the YAML spec's subjectName.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "wait": {
+          "char": "w",
+          "name": "wait",
+          "summary": "Number of minutes to wait for results.",
+          "default": 10,
+          "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"
+        },
+        "batch-size": {
+          "name": "batch-size",
+          "summary": "Number of tests per API request (max 5).",
+          "default": 5,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "no-normalize": {
+          "name": "no-normalize",
+          "summary": "Disable auto-normalization of field names and shorthand references.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
+      "hidden": true,
       "hiddenAliases": [],
-      "id": "agent:preview:sessions",
+      "id": "agent:test:run-eval",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "beta",
       "strict": true,
-      "summary": "List all known programmatic agent preview sessions.",
+      "summary": "Run evaluation tests against an Agentforce agent.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "sessions.js"
+        "test",
+        "run-eval.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:sessions",
-        "preview:agent:sessions",
-        "preview:sessions:agent",
-        "agent:sessions:preview",
-        "sessions:agent:preview",
-        "sessions:preview:agent"
+        "agent:test:run-eval",
+        "test:agent:run-eval",
+        "test:run-eval:agent",
+        "agent:run-eval:test",
+        "run-eval:agent:test",
+        "run-eval:test:agent"
       ]
     },
-    "agent:preview:start": {
+    "agent:test:run": {
       "aliases": [],
       "args": {},
-      "description": "This command outputs a session ID that you then use with the \"agent preview send\" command to send an utterance to the agent.  Use the \"agent preview sessions\" command to list all active sessions and the \"agent preview end\" command to end a specific session.\n\nIdentify the agent you want to start previewing with either the --authoring-bundle flag to specify a local authoring bundle's API name or --api-name to specify an activated published agent's API name.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory. \n\nWhen starting a preview session using the authoring bundle, which contains the agent's Agent Script file, the preview uses mocked actions by default.  Specify --use-live-actions for live mode, which uses the real Apex classes, flows, etc, in the org for the actions.",
+      "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": [
-        "Start a programmatic agent preview session by specifying an authoring bundle; uses mocked actions by default. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --target-org my-dev-org",
-        "Similar to previous example but use live actions and the default org:\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --use-live-actions",
-        "Start a preview session with an activated published agent:\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent"
+        "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": {
@@ -1843,51 +1819,75 @@
         "api-name": {
           "char": "n",
           "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
+          "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"
         },
-        "authoring-bundle": {
-          "name": "authoring-bundle",
-          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+        "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"
         },
-        "use-live-actions": {
-          "name": "use-live-actions",
-          "summary": "Use real actions in the org; if not specified, preview uses AI to simulate (mock) actions.",
+        "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:preview:start",
+      "id": "agent:test:run",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Start a programmatic agent preview session.",
+      "summary": "Start an agent test in your org.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "start.js"
+        "test",
+        "run.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:start",
-        "preview:agent:start",
-        "preview:start:agent",
-        "agent:start:preview",
-        "start:agent:preview",
-        "start:preview:agent"
+        "agent:test:run",
+        "test:agent:run",
+        "test:run:agent",
+        "agent:run:test",
+        "run:agent:test",
+        "run:test:agent"
       ]
     },
     "agent:validate:authoring-bundle": {
@@ -1975,5 +1975,5 @@
       ]
     }
   },
-  "version": "1.32.12"
+  "version": "1.32.14"
 }