@salesforce/plugin-agent 1.41.0 → 1.42.0

package/oclif.manifest.json

@@ -409,16 +409,14 @@
         "preview:agent"
       ]
     },
-    "agent:generate:agent-spec": {
+    "agent:adl: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": "Creates a new data library in the target org. The --source-type flag determines the type of library: SFDRIVE (file upload), KNOWLEDGE (Salesforce Knowledge articles), or RETRIEVER (existing active Custom Retriever).",
       "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 SFDRIVE library:\n<%= config.bin %> <%= command.id %> --target-org myOrg --name \"My Docs\" --developer-name My_Docs --source-type sfdrive",
+        "Create a KNOWLEDGE library with index fields:\n<%= config.bin %> <%= command.id %> --target-org myOrg --name \"KB Library\" --developer-name KB_Library --source-type knowledge --primary-index-field1 Title --primary-index-field2 Summary",
+        "Create a RETRIEVER library:\n<%= config.bin %> <%= command.id %> --target-org myOrg --name \"Existing Retriever\" --developer-name Existing_Retriever --source-type retriever --retriever-id 0ppXX0000000001"
       ],
       "flags": {
         "json": {
@@ -453,164 +451,110 @@
           "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.",
+        "name": {
+          "char": "n",
+          "name": "name",
+          "required": true,
+          "summary": "Display name for the data library (max 80 characters).",
           "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.",
+        "developer-name": {
+          "name": "developer-name",
+          "required": true,
+          "summary": "API name for the data library (max 80 characters, alphanumeric and underscores only, must start with a letter).",
           "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.",
+        "source-type": {
+          "name": "source-type",
+          "required": true,
+          "summary": "Type of grounding source: sfdrive (file upload), knowledge (Salesforce Knowledge articles), or retriever (existing active Custom Retriever).",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "true",
-            "false"
+            "sfdrive",
+            "knowledge",
+            "retriever"
           ],
           "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.",
+        "description": {
+          "name": "description",
+          "summary": "Description of the data library (max 255 characters).",
           "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.",
+        "index-mode": {
+          "name": "index-mode",
+          "summary": "Index mode for SFDRIVE libraries: basic or enhanced.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "basic",
+            "enhanced"
+          ],
           "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",
+        "retriever-id": {
+          "name": "retriever-id",
+          "summary": "ID of an active Custom Retriever (required for RETRIEVER source type; retriever must be active).",
           "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.",
+        "primary-index-field1": {
+          "name": "primary-index-field1",
+          "summary": "Primary index field 1 for KNOWLEDGE libraries (required, immutable after creation).",
           "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.",
+        "primary-index-field2": {
+          "name": "primary-index-field2",
+          "summary": "Primary index field 2 for KNOWLEDGE libraries (required, immutable after creation).",
           "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:generate:agent-spec",
+      "id": "agent:adl:create",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
+      "summary": "Create an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "agent-spec.js"
+        "adl",
+        "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:adl:create",
+        "adl:agent:create",
+        "adl:create:agent",
+        "agent:create:adl",
+        "create:agent:adl",
+        "create:adl:agent"
       ]
     },
-    "agent:generate:authoring-bundle": {
+    "agent:adl:delete": {
       "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. The resulting Agent Script file is customized to reflect what's in the agent spec file. You can also create an authoring bundle without an agent spec file by specifying the \"--no-spec\" flag; in this case, the resulting Agent Script file is just the default boilerplate.\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": "Permanently deletes a data library and all associated files and indexing data.",
       "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 without using an agent spec file; give the bundle the label \"My Authoring Bundle\" and use your default org:\n<%= config.bin %> <%= command.id %> --no-spec --name \"My Authoring Bundle\"",
-        "Generate an authoring bundle from the \"specs/agentSpec.yaml\" agent spec YAML file and give it the label \"My Authoring Bundle\"; 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"
+        "Delete a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -638,13 +582,6 @@
           "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",
@@ -652,77 +589,50 @@
           "multiple": false,
           "type": "option"
         },
-        "spec": {
-          "char": "f",
-          "name": "spec",
-          "summary": "Path to the agent spec YAML file. If you don't specify the flag, the command provides a list that you can choose from. Use the --no-spec flag to skip using an agent spec entirely.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "no-spec": {
-          "name": "no-spec",
-          "summary": "Skip prompting for an agent spec and use the default Agent Script boilerplate in the generated authoring bundle.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "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.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Overwrite the existing authoring bundle if one with the same API name already exists locally.",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:authoring-bundle",
+      "id": "agent:adl:delete",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
+      "summary": "Delete an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "authoring-bundle.js"
+        "adl",
+        "delete.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:adl:delete",
+        "adl:agent:delete",
+        "adl:delete:agent",
+        "agent:delete:adl",
+        "delete:agent:adl",
+        "delete:adl:agent"
       ]
     },
-    "agent:generate:template": {
+    "agent:adl:get": {
       "aliases": [],
       "args": {},
-      "description": "WARNING: This command doesn't work for agents that were created from an Agent Script file. In other words, you can't currently package an agent template for agents that use Agent Script.\n\nAt 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 metadata file for a specific agent (Bot). You then use the BotTemplate metadata file, along with the GenAiPlannerBundle metadata 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 metadata 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 metadata file is generated in the \"botTemplates\" directory in the output directory specified with the --output-dir flag, and has the name <Agent_API_name>\\_v<Version>\\_Template.botTemplate-meta.xml, such as my-package/botTemplates/My_Awesome_Agent_v4_Template.botTemplate-meta.xml. The command displays the full pathname of the generated files when it completes.\n\nSee \"Develop and Package Agent Templates Using Scratch Orgs\" (https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/dev2gp_package_agent_templates.htm) for details about the complete process, which includes using a scratch org to create and test the agent, retrieving the agent metadata to your DX project, running this command to create the agent template, and then packaging the template.",
+      "description": "Returns the full detail of a data library including its grounding source configuration, status, and retriever ID.",
       "examples": [
-        "Generate an agent template from the My_Awesome_Agent Bot metadata file in your DX project and save the BotTemplate and GenAiPlannerBundle to the specified directory; use version 1 of the agent. The agent that the template is based on is in the org with alias \"my-scratch-org\":\n<%= config.bin %> <%= command.id %> --agent-file force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1 --output-dir my-package --source-org my-scratch-org"
+        "Get details of a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -740,44 +650,28 @@
           "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"
-        },
-        "source-org": {
-          "char": "s",
-          "name": "source-org",
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
           "noCacheDefault": true,
           "required": true,
-          "summary": "Username or alias of the namespaced scratch org that contains the agent which this template is based on.",
+          "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"
         },
-        "agent-version": {
-          "name": "agent-version",
-          "required": true,
-          "summary": "Version of the agent (BotVersion).",
+        "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-file": {
-          "char": "f",
-          "name": "agent-file",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
           "required": true,
-          "summary": "Path to an agent (Bot) metadata file.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "output-dir": {
-          "char": "r",
-          "name": "output-dir",
-          "summary": "Directory where the generated BotTemplate and GenAiPlannerBundle files are saved.",
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -785,42 +679,48 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:template",
+      "id": "agent:adl:get",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Generate an agent template from an existing agent in your DX project so you can then package the template in a second-generation managed package.",
+      "summary": "Get details of an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "template.js"
+        "adl",
+        "get.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:template",
-        "generate:agent:template",
-        "generate:template:agent",
-        "agent:template:generate",
-        "template:agent:generate",
-        "template:generate:agent"
+        "agent:adl:get",
+        "adl:agent:get",
+        "adl:get:agent",
+        "agent:get:adl",
+        "get:agent:adl",
+        "get:adl:agent"
       ]
     },
-    "agent:generate:test-spec": {
+    "agent:adl:list": {
       "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\nYou can manually add contextVariables to test cases in the generated YAML file to inject contextual data (such as CaseId or RoutableId) into agent sessions. This is useful for testing agent behavior with different contextual information.\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": "Returns all data libraries in the target org, including their source type, status, and library ID.",
       "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"
+        "List all data libraries in the default target org:\n<%= config.bin %> <%= command.id %> --target-org myOrg",
+        "List data libraries and output as JSON:\n<%= config.bin %> <%= command.id %> --target-org myOrg --json"
       ],
       "flags": {
+        "json": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "flags-dir": {
           "helpGroup": "GLOBAL",
           "name": "flags-dir",
@@ -829,66 +729,58 @@
           "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,
+        "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"
         },
-        "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,
+        "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": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:test-spec",
+      "id": "agent:adl:list",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "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": "List Agentforce Data Libraries in an org.",
+      "enableJsonFlag": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "test-spec.js"
+        "adl",
+        "list.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:adl:list",
+        "adl:agent:list",
+        "adl:list:agent",
+        "agent:list:adl",
+        "list:agent:adl",
+        "list:adl:agent"
       ]
     },
-    "agent:preview:end": {
+    "agent:adl:status": {
       "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, respectively. 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\nUse the --all flag to end all active preview sessions at once. You can combine --all with --api-name or --authoring-bundle to end only sessions for a specific agent, or use --all on its own to end every session across all agents in the project.",
+      "description": "Returns the current indexing status including stage details (DATA_LAKE_OBJECT, SEARCH_INDEX, RETRIEVER) and any errors.",
       "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",
-        "End all active preview sessions for a specific agent without prompting:\n<%= config.bin %> <%= command.id %> --all --authoring-bundle My_Local_Agent --target-org <target_org> --no-prompt",
-        "End all active preview sessions across every agent in the local session cache for an org:\n<%= config.bin %> <%= command.id %> --all --target-org <target_org>"
+        "Get status of a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -923,129 +815,53 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "exclusive": [
-            "all"
-          ],
-          "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",
-          "exclusive": [
-            "authoring-bundle"
-          ],
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "authoring-bundle": {
-          "exclusive": [
-            "api-name"
-          ],
-          "name": "authoring-bundle",
-          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "all": {
-          "exclusive": [
-            "session-id"
-          ],
-          "name": "all",
-          "summary": "End all active preview sessions. Combine with --api-name or --authoring-bundle to limit to a specific agent, or use with only --target-org to end sessions for all agents found in the local session cache. Requires --target-org.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "no-prompt": {
-          "char": "p",
-          "name": "no-prompt",
-          "summary": "Don't prompt for confirmation before ending sessions. Has an effect only when used with --all.",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:end",
+      "id": "agent:adl:status",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "End an existing programmatic agent preview session and get trace location.",
+      "summary": "Get indexing status of an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Preview session ended successfully and traces saved."
-          },
-          {
-            "name": "ExactlyOneRequired (2)",
-            "description": "Neither --api-name nor --authoring-bundle was provided (required when --all is not set)."
-          },
-          {
-            "name": "NotFound (2)",
-            "description": "Agent not found, or no preview session exists for this agent."
-          },
-          {
-            "name": "PreviewEndFailed (4)",
-            "description": "Failed to end the preview session."
-          },
-          {
-            "name": "PreviewEndPartialFailure (68)",
-            "description": "With --all, one or more sessions failed to end while others succeeded."
-          },
-          {
-            "name": "SessionAmbiguous (5)",
-            "description": "Multiple preview sessions found; specify --session-id to choose one."
-          }
-        ]
-      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "end.js"
+        "adl",
+        "status.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:end",
-        "preview:agent:end",
-        "preview:end:agent",
-        "agent:end:preview",
-        "end:agent:preview",
-        "end:preview:agent"
+        "agent:adl:status",
+        "adl:agent:status",
+        "adl:status:agent",
+        "agent:status:adl",
+        "status:agent:adl",
+        "status:adl:agent"
       ]
     },
-    "agent:preview:send": {
+    "agent:adl:update": {
       "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": "Updates the label, description, or other mutable properties of an existing data library.",
       "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"
+        "Update the label of a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --name \"New Name\" --target-org myOrg",
+        "Update the description:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --description \"Updated description\" --target-org myOrg",
+        "Update Knowledge library content fields (triggers re-indexing):\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --content-fields \"Answer**c,Summary**c\" --target-org myOrg",
+        "Restrict Knowledge library to public articles:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --restrict-to-public-articles --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -1080,103 +896,79 @@
           "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.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "utterance": {
-          "char": "u",
-          "name": "utterance",
-          "required": true,
-          "summary": "Utterance to send to the agent, enclosed in double quotes.",
+        "name": {
+          "char": "n",
+          "name": "name",
+          "summary": "New display name for the data library (max 80 characters).",
           "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.",
+        "description": {
+          "name": "description",
+          "summary": "New description for the data library (max 255 characters).",
           "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.",
+        "content-fields": {
+          "name": "content-fields",
+          "summary": "Comma-separated list of content fields for KNOWLEDGE libraries (triggers re-indexing).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "restrict-to-public-articles": {
+          "name": "restrict-to-public-articles",
+          "summary": "Restrict to public Knowledge articles only (KNOWLEDGE libraries, triggers re-indexing).",
+          "allowNo": true,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:send",
+      "id": "agent:adl:update",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Send a message to an existing agent preview session.",
+      "summary": "Update an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Message sent successfully and agent response received."
-          },
-          {
-            "name": "NotFound (2)",
-            "description": "Agent not found, or no preview session exists for this agent."
-          },
-          {
-            "name": "PreviewSendFailed (4)",
-            "description": "Failed to send message or receive response from the preview session."
-          },
-          {
-            "name": "SessionAmbiguous (5)",
-            "description": "Multiple preview sessions found; specify --session-id to choose one."
-          }
-        ]
-      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "send.js"
+        "adl",
+        "update.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:send",
-        "preview:agent:send",
-        "preview:send:agent",
-        "agent:send:preview",
-        "send:agent:preview",
-        "send:preview:agent"
+        "agent:adl:update",
+        "adl:agent:update",
+        "adl:update:agent",
+        "agent:update:adl",
+        "update:agent:adl",
+        "update:adl:agent"
       ]
     },
-    "agent:preview:sessions": {
+    "agent:adl:upload": {
       "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": "Performs the multi-step upload workflow: checks upload readiness, obtains a pre-signed S3 URL, uploads the file, triggers indexing, and optionally polls until the library is ready (retrieverId is populated).\n\nThis command only works with SFDRIVE libraries. KNOWLEDGE libraries index automatically after creation, and RETRIEVER libraries require no file upload.",
       "examples": [
-        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
+        "Upload a file and wait for indexing to complete:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg --wait 10",
+        "Upload a file without waiting:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -1193,53 +985,1227 @@
           "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"
+        },
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "file": {
+          "char": "f",
+          "name": "file",
+          "required": true,
+          "summary": "Path to the file to upload.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "wait": {
+          "char": "w",
+          "name": "wait",
+          "summary": "Number of minutes to wait for indexing to complete. If not specified, returns after triggering indexing.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:sessions",
+      "id": "agent:adl:upload",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "List all known programmatic agent preview sessions.",
+      "summary": "Upload a file to an SFDRIVE Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Sessions listed successfully (or empty list if no active sessions)."
-          }
-        ]
-      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "sessions.js"
+        "adl",
+        "upload.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:sessions",
-        "preview:agent:sessions",
-        "preview:sessions:agent",
-        "agent:sessions:preview",
-        "sessions:agent:preview",
-        "sessions:preview:agent"
+        "agent:adl:upload",
+        "adl:agent:upload",
+        "adl:upload:agent",
+        "agent:upload:adl",
+        "upload:agent:adl",
+        "upload:adl:agent"
       ]
     },
-    "agent:preview:start": {
+    "agent:generate:agent-spec": {
       "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 with --authoring-bundle, you must explicitly specify the execution mode using one of these flags:\n\n- --use-live-actions: Executes real Apex classes, flows, and other actions in the org. This surfaces compile and validation errors during preview.\n- --simulate-actions: Uses AI to simulate action execution without calling real implementations.\n\nPublished agents (--api-name) always use live actions. The mode flags are optional and have no effect for published agents.",
+      "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": [
-        "Start a programmatic agent preview session by specifying an authoring bundle; use simulated actions. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --target-org my-dev-org --simulate-actions",
-        "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 (always uses live actions):\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent"
+        "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": {
+          "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"
+        },
+        "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"
+        },
+        "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.",
+          "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:generate:agent-spec",
+      "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.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "generate",
+        "agent-spec.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:generate:authoring-bundle": {
+      "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. The resulting Agent Script file is customized to reflect what's in the agent spec file. You can also create an authoring bundle without an agent spec file by specifying the \"--no-spec\" flag; in this case, the resulting Agent Script file is just the default boilerplate.\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": [
+        "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 without using an agent spec file; give the bundle the label \"My Authoring Bundle\" and use your default org:\n<%= config.bin %> <%= command.id %> --no-spec --name \"My Authoring Bundle\"",
+        "Generate an authoring bundle from the \"specs/agentSpec.yaml\" agent spec YAML file and give it the label \"My Authoring Bundle\"; 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": {
+          "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"
+        },
+        "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-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 you don't specify the flag, the command provides a list that you can choose from. Use the --no-spec flag to skip using an agent spec entirely.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "no-spec": {
+          "name": "no-spec",
+          "summary": "Skip prompting for an agent spec and use the default Agent Script boilerplate in the generated authoring bundle.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "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"
+        },
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Overwrite the existing authoring bundle if one with the same API name already exists locally.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "agent:generate:authoring-bundle",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
+      "enableJsonFlag": true,
+      "requiresProject": 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": "WARNING: This command doesn't work for agents that were created from an Agent Script file. In other words, you can't currently package an agent template for agents that use Agent Script.\n\nAt 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 metadata file for a specific agent (Bot). You then use the BotTemplate metadata file, along with the GenAiPlannerBundle metadata 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 metadata 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 metadata file is generated in the \"botTemplates\" directory in the output directory specified with the --output-dir flag, and has the name <Agent_API_name>\\_v<Version>\\_Template.botTemplate-meta.xml, such as my-package/botTemplates/My_Awesome_Agent_v4_Template.botTemplate-meta.xml. The command displays the full pathname of the generated files when it completes.\n\nSee \"Develop and Package Agent Templates Using Scratch Orgs\" (https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/dev2gp_package_agent_templates.htm) for details about the complete process, which includes using a scratch org to create and test the agent, retrieving the agent metadata to your DX project, running this command to create the agent template, and then packaging the template.",
+      "examples": [
+        "Generate an agent template from the My_Awesome_Agent Bot metadata file in your DX project and save the BotTemplate and GenAiPlannerBundle to the specified directory; use version 1 of the agent. The agent that the template is based on is in the org with alias \"my-scratch-org\":\n<%= config.bin %> <%= command.id %> --agent-file force-app/main/default/bots/My_Awesome_Agent/My_Awesome_Agent.bot-meta.xml --agent-version 1 --output-dir my-package --source-org my-scratch-org"
+      ],
+      "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"
+        },
+        "source-org": {
+          "char": "s",
+          "name": "source-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the namespaced scratch org that contains the agent which this template is based on.",
+          "hasDynamicHelp": true,
+          "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"
+        },
+        "output-dir": {
+          "char": "r",
+          "name": "output-dir",
+          "summary": "Directory where the generated BotTemplate and GenAiPlannerBundle files are saved.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "agent:generate:template",
+      "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 second-generation managed package.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "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\nYou can manually add contextVariables to test cases in the generated YAML file to inject contextual data (such as CaseId or RoutableId) into agent sessions. This is useful for testing agent behavior with different contextual information.\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",
+        "generate",
+        "test-spec.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: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": [
+        "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",
+        "Publish with verbose output to see all retrieved and deployed metadata components:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --verbose",
+        "Publish with concise output showing only essential information:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --concise"
+      ],
+      "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"
+        },
+        "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"
+        },
+        "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"
+        },
+        "skip-retrieve": {
+          "name": "skip-retrieve",
+          "summary": "Don't retrieve the metadata associated with the agent to your DX project.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "verbose": {
+          "char": "v",
+          "exclusive": [
+            "concise"
+          ],
+          "name": "verbose",
+          "summary": "Display detailed output showing all metadata components retrieved and deployed during the publish process.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "concise": {
+          "exclusive": [
+            "verbose"
+          ],
+          "name": "concise",
+          "summary": "Display minimal output with only essential information about the publish operation.",
+          "allowNo": false,
+          "type": "boolean"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "agent:publish:authoring-bundle",
+      "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.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Agent published successfully without errors."
+          },
+          {
+            "name": "Failed (1)",
+            "description": "Compilation errors found in the Agent Script file."
+          }
+        ]
+      },
+      "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"
+      ],
+      "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:test:create": {
+      "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 (legacy) or Agentforce Studio (NGT). This command also retrieves the metadata component associated with the new test to your local Salesforce DX project and displays its filename. By default, the legacy AiEvaluationDefinition is created; use --test-runner agentforce-studio to author an AiTestingDefinition (NGT) instead.\n\nAfter you've created the test in the org, use the \"agent test run\" command to run it.",
+      "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",
+        "Author an Agentforce Studio (NGT) test from an NGT-shaped YAML; writes an AiTestingDefinition metadata file:\n<%= config.bin %> <%= command.id %> --spec specs/ReturnsCheckout.ngt.yaml --api-name Returns_Checkout --test-runner agentforce-studio --target-org my-org"
+      ],
+      "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-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",
+          "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"
+        },
+        "preview": {
+          "name": "preview",
+          "summary": "Preview the test metadata file without deploying to your org.",
+          "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.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "test-runner": {
+          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
+          "name": "test-runner",
+          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "agentforce-studio",
+            "testing-center"
+          ],
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "agent:test:create",
+      "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.",
+      "enableJsonFlag": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Test created and deployed successfully."
+          },
+          {
+            "name": "Failed (1)",
+            "description": "Test validation errors or metadata format issues."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Test spec file not found or org connection failed."
+          },
+          {
+            "name": "DeploymentFailed (4)",
+            "description": "Deployment failed due to API or network errors."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "test",
+        "create.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:test:create",
+        "test:agent:create",
+        "test:create:agent",
+        "agent:create:test",
+        "create:agent:test",
+        "create:test:agent"
+      ]
+    },
+    "agent:test:list": {
+      "aliases": [],
+      "args": {},
+      "description": "The command outputs a table with the name (API name) of each test along with its unique ID, type ('agentforce-studio' or 'testing-center'), and the date it was created in the org.",
+      "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"
+      ],
+      "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"
+        },
+        "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,
+      "hiddenAliases": [],
+      "id": "agent:test:list",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "List the available agent tests in your org.",
+      "enableJsonFlag": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Agent tests listed successfully."
+          },
+          {
+            "name": "Failed (4)",
+            "description": "Failed to retrieve agent tests due to API or network errors."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "test",
+        "list.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:test:list",
+        "test:agent:list",
+        "test:list:agent",
+        "agent:list:test",
+        "list:agent:test",
+        "list:test:agent"
+      ]
+    },
+    "agent:test:results": {
+      "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.",
+      "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"
+      ],
+      "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"
+        },
+        "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"
+        },
+        "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.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "test-runner": {
+          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
+          "name": "test-runner",
+          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "agentforce-studio",
+            "testing-center"
+          ],
+          "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:results",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Get the results of a completed agent test run.",
+      "enableJsonFlag": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Results retrieved successfully. Test results (passed/failed) are in the output."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Job ID not found or invalid."
+          },
+          {
+            "name": "Failed (4)",
+            "description": "Failed to retrieve results due to API or network errors."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "test",
+        "results.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.",
+      "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"
+      ],
+      "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"
+        },
+        "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"
+        },
+        "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.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "test-runner": {
+          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
+          "name": "test-runner",
+          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "agentforce-studio",
+            "testing-center"
+          ],
+          "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:resume",
+      "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.",
+      "enableJsonFlag": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Test completed successfully (with test results in the output)."
+          },
+          {
+            "name": "Failed (1)",
+            "description": "Tests encountered execution errors (test cases with ERROR status)."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Job ID not found or invalid."
+          },
+          {
+            "name": "OperationFailed (4)",
+            "description": "Failed to poll test due to API or network errors."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "test",
+        "resume.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:test:resume",
+        "test:agent:resume",
+        "test:resume:agent",
+        "agent:resume:test",
+        "resume:agent:test",
+        "resume:test:agent"
+      ]
+    },
+    "agent:test:run-eval": {
+      "aliases": [],
+      "args": {},
+      "description": "Specify the tests you want to run with one of these inputs to the --spec flag:\n\n- YAML test spec generated by the `agent generate test-spec` CLI command\n- JSON payload\n\nWhen you provide a YAML test spec, this command automatically translates test cases into internal state-based evaluation framework calls and infers the agent name from the test spec's `subjectName` field. As a result, you can use the same test spec with both the `agent test run` and `agent test run-eval` commands. YAML test specs also support context variables, 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 evaluation framework 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 as when you use a YAML test spec.\n\nThis command supports more than 8 evaluator types, including subagent routing assertions, action invocation checks, string/numeric assertions, semantic similarity scoring, and LLM-based quality ratings.",
+      "examples": [
+        "Run tests using a YAML test spec on the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec specs/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 specs/my-agent-testSpec.yaml --api-name My_Agent",
+        "Run tests using a JSON payload:\n<%= config.bin %> <%= command.id %> --spec specs/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 specs/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 specs/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": {
@@ -1274,61 +2240,62 @@
           "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": "API name of the activated published agent you want to preview.",
+          "summary": "Agent API name (also called DeveloperName) used to resolve agent_id and agent_version_id. Auto-inferred from the YAML spec's subjectName.",
           "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.",
+        "result-format": {
+          "name": "result-format",
+          "summary": "Format of the agent test run results.",
+          "default": "human",
           "hasDynamicHelp": false,
           "multiple": false,
-          "type": "option"
-        },
-        "use-live-actions": {
-          "exclusive": [
-            "simulate-actions"
-          ],
-          "name": "use-live-actions",
-          "summary": "Execute real actions in the org (Apex classes, flows, etc.). Required with --authoring-bundle.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "simulate-actions": {
-          "exclusive": [
-            "use-live-actions"
+          "options": [
+            "json",
+            "human",
+            "junit",
+            "tap"
           ],
-          "name": "simulate-actions",
-          "summary": "Use AI to simulate action execution instead of calling real actions. Required with --authoring-bundle.",
-          "allowNo": false,
-          "type": "boolean"
+          "type": "option"
         },
-        "agent-json": {
-          "dependsOn": [
-            "authoring-bundle"
-          ],
-          "hidden": true,
-          "name": "agent-json",
-          "summary": "Path to a pre-compiled AgentJSON file to use instead of compiling the Agent Script file. Intended for internal use and testing.",
+        "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": true,
       "hiddenAliases": [],
-      "id": "agent:preview:start",
+      "id": "agent:test:run-eval",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "beta",
       "strict": true,
-      "summary": "Start a programmatic agent preview session.",
+      "summary": "Run rich evaluation tests against an Agentforce agent.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "envVariablesSection": {
         "header": "ENVIRONMENT VARIABLES",
         "body": [
@@ -1343,23 +2310,19 @@
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Preview session started successfully."
+            "description": "Tests completed successfully. Test results (passed/failed) are in the JSON output."
           },
           {
             "name": "Failed (1)",
-            "description": "Agent Script compilation failed (syntax errors in the script)."
+            "description": "Tests encountered execution errors (tests couldn't run properly)."
           },
           {
             "name": "NotFound (2)",
-            "description": "Agent not found, or compilation API returned HTTP 404 (endpoint may not be available in your org or region)."
-          },
-          {
-            "name": "ServerError (3)",
-            "description": "Compilation API returned HTTP 500 (server error during compilation)."
+            "description": "Agent not found, spec file not found, or invalid agent name."
           },
           {
-            "name": "PreviewStartFailed (4)",
-            "description": "Preview session failed to start due to API or network errors."
+            "name": "OperationFailed (4)",
+            "description": "Failed to execute tests due to API or network errors."
           }
         ]
       },
@@ -1368,28 +2331,27 @@
         "lib",
         "commands",
         "agent",
-        "preview",
-        "start.js"
+        "test",
+        "run-eval.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:start",
-        "preview:agent:start",
-        "preview:start:agent",
-        "agent:start:preview",
-        "start:agent:preview",
-        "start: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:publish:authoring-bundle": {
+    "agent:test:run": {
       "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": "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": [
-        "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",
-        "Publish with verbose output to see all retrieved and deployed metadata components:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --verbose",
-        "Publish with concise output showing only essential information:\n<%= config.bin %> <%= command.id %> --api-name MyAuthoringbundle --concise"
+        "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": {
@@ -1427,93 +2389,126 @@
         "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 agent test to run; corresponds to the name of the AiEvaluationDefinition metadata component that implements the agent test.",
           "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"
+        "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"
         },
-        "verbose": {
-          "char": "v",
-          "exclusive": [
-            "concise"
+        "result-format": {
+          "name": "result-format",
+          "summary": "Format of the agent test run results.",
+          "default": "human",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "json",
+            "human",
+            "junit",
+            "tap"
           ],
-          "name": "verbose",
-          "summary": "Display detailed output showing all metadata components retrieved and deployed during the publish process.",
-          "allowNo": false,
-          "type": "boolean"
+          "type": "option"
         },
-        "concise": {
-          "exclusive": [
-            "verbose"
+        "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"
+        },
+        "test-runner": {
+          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
+          "name": "test-runner",
+          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "agentforce-studio",
+            "testing-center"
           ],
-          "name": "concise",
-          "summary": "Display minimal output with only essential information about the publish operation.",
+          "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:publish:authoring-bundle",
+      "id": "agent:test:run",
       "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": "Start an agent test in your org.",
       "enableJsonFlag": true,
-      "requiresProject": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
       "errorCodes": {
         "header": "ERROR CODES",
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Agent published successfully without errors."
+            "description": "Test started successfully (without --wait), or test completed successfully (with --wait)."
           },
           {
             "name": "Failed (1)",
-            "description": "Compilation errors found in the Agent Script file."
+            "description": "Tests encountered execution errors (test cases with ERROR status when using --wait)."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Test definition not found or invalid test name."
+          },
+          {
+            "name": "OperationFailed (4)",
+            "description": "Failed to start or poll test due to API or network errors."
           }
         ]
       },
-      "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"
+        "test",
+        "run.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:test:run",
+        "test:agent:run",
+        "test:run:agent",
+        "agent:run:test",
+        "run:agent:test",
+        "run:test:agent"
       ]
     },
-    "agent:test:create": {
+    "agent:validate:authoring-bundle": {
       "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 (legacy) or Agentforce Studio (NGT). This command also retrieves the metadata component associated with the new test to your local Salesforce DX project and displays its filename. By default, the legacy AiEvaluationDefinition is created; use --test-runner agentforce-studio to author an AiTestingDefinition (NGT) instead.\n\nAfter you've created the test in the org, use the \"agent test run\" command to run it.",
-      "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",
-        "Author an Agentforce Studio (NGT) test from an NGT-shaped YAML; writes an AiTestingDefinition metadata file:\n<%= config.bin %> <%= command.id %> --spec specs/ReturnsCheckout.ngt.yaml --api-name Returns_Checkout --test-runner agentforce-studio --target-org my-org"
+      "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": [
+        "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": {
@@ -1531,20 +2526,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",
@@ -1562,40 +2543,25 @@
           "multiple": false,
           "type": "option"
         },
-        "preview": {
-          "name": "preview",
-          "summary": "Preview the test metadata file without deploying to your org.",
-          "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.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "test-runner": {
-          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
-          "name": "test-runner",
-          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+        "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.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "agentforce-studio",
-            "testing-center"
-          ],
           "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:create",
+      "id": "agent:validate:authoring-bundle",
       "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": "Validate an authoring bundle to ensure its Agent Script file compiles successfully and can be used to publish an agent.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "envVariablesSection": {
         "header": "ENVIRONMENT VARIABLES",
         "body": [
@@ -1610,47 +2576,57 @@
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Test created and deployed successfully."
+            "description": "Agent Script file compiled successfully without errors."
           },
           {
             "name": "Failed (1)",
-            "description": "Test validation errors or metadata format issues."
+            "description": "Compilation errors found in the Agent Script file."
           },
           {
             "name": "NotFound (2)",
-            "description": "Test spec file not found or org connection failed."
+            "description": "Validation/compilation API returned HTTP 404. The API endpoint may not be available in your org or region."
           },
           {
-            "name": "DeploymentFailed (4)",
-            "description": "Deployment failed due to API or network errors."
+            "name": "ServerError (3)",
+            "description": "Validation/compilation API returned HTTP 500. A server error occurred during compilation."
           }
         ]
       },
+      "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",
-        "test",
-        "create.js"
+        "validate",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:create",
-        "test:agent:create",
-        "test:create:agent",
-        "agent:create:test",
-        "create:agent:test",
-        "create:test:agent"
+        "agent:validate:authoring-bundle",
+        "validate:agent:authoring-bundle",
+        "validate:authoring-bundle:agent",
+        "agent:authoring-bundle:validate",
+        "authoring-bundle:agent:validate",
+        "authoring-bundle:validate:agent"
       ]
     },
-    "agent:test:list": {
+    "agent:trace:delete": {
       "aliases": [],
       "args": {},
-      "description": "The command outputs a table with the name (API name) of each test along with its unique ID, type ('agentforce-studio' or 'testing-center'), and the date it was created in the org.",
+      "description": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. Use this command to delete some or all of the trace files.\n\nBy default, this command shows a preview of what will be deleted and prompts for confirmation. Use --no-prompt to skip confirmation.\n\nWithout filters, this comamnd deletes all trace files for all agents and sessions. Use flags to narrow the scope: filter by agent API name (--agent), by session (--session-id), or by age (--older-than).",
       "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"
+        "Delete all traces for all agents and sessions; prompt for confirmation:\n<%= config.bin %> <%= command.id %>",
+        "Delete all traces for a specific agent:\n<%= config.bin %> <%= command.id %> --agent My_Agent",
+        "Delete traces from a specific session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
+        "Delete traces older than 7 days:\n<%= config.bin %> <%= command.id %> --older-than 7d",
+        "Delete traces older than 24 hours for a specific agent; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --agent My_Agent --older-than 24h --no-prompt",
+        "Delete all traces for all agents and sessions; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --no-prompt"
       ],
       "flags": {
         "json": {
@@ -1668,52 +2644,51 @@
           "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,
+        "agent": {
+          "char": "a",
+          "name": "agent",
+          "summary": "API name of the agent used to filter the list of trace files you want to delete. Matches against the API name used when starting the session, either an authoring bundle or a published agent API name.",
+          "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "api-version": {
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+        "session-id": {
+          "name": "session-id",
+          "summary": "Session ID used to filter the list of trace files you want to delete. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "older-than": {
+          "name": "older-than",
+          "summary": "Duration used to filter the list of trace files; only files older than the duration are deleted. Accepts a number followed by a unit: m/minutes, h/hours, d/days, w/weeks. Examples: 7d, 24h, 2w.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "no-prompt": {
+          "name": "no-prompt",
+          "summary": "Skip the confirmation prompt and delete immediately.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
-      "hasDynamicHelp": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:test:list",
+      "id": "agent:trace:delete",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "List the available agent tests in your org.",
+      "summary": "Delete trace files from an agent preview session.",
       "enableJsonFlag": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
+      "requiresProject": true,
       "errorCodes": {
         "header": "ERROR CODES",
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Agent tests listed successfully."
-          },
-          {
-            "name": "Failed (4)",
-            "description": "Failed to retrieve agent tests due to API or network errors."
+            "description": "Traces deleted successfully (or no traces matched)."
           }
         ]
       },
@@ -1722,27 +2697,31 @@
         "lib",
         "commands",
         "agent",
-        "test",
-        "list.js"
+        "trace",
+        "delete.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:list",
-        "test:agent:list",
-        "test:list:agent",
-        "agent:list:test",
-        "list:agent:test",
-        "list:test:agent"
+        "agent:trace:delete",
+        "trace:agent:delete",
+        "trace:delete:agent",
+        "agent:delete:trace",
+        "delete:agent:trace",
+        "delete:trace:agent"
       ]
     },
-    "agent:test:results": {
+    "agent:trace:list": {
       "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": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. By default, this command lists all trace files for all agents and all of their sessions. Use flags to narrow results: filter by agent name (--agent), by session (--session-id), or by date (--since).\n\nEach row in the output corresponds to one trace file, which in turn corresponds to one agent session. The Agent column shows the authoring bundle or API name used when starting the session.",
       "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"
+        "List all trace files for all agents and sessions:\n<%= config.bin %> <%= command.id %>",
+        "List all trace files for a specific agent:\n<%= config.bin %> <%= command.id %> --agent My_Agent",
+        "List trace files for a specific session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
+        "List trace files recorded on or after April 20, 2026 (date-only, interpreted as UTC midnight):\n<%= config.bin %> <%= command.id %> --since 2026-04-20",
+        "List trace files recorded on or after a specific UTC time:\n<%= config.bin %> <%= command.id %> --since 2026-04-20T14:00:00Z",
+        "Filter by agent and date together:\n<%= config.bin %> <%= command.id %> --agent My_Agent --since 2026-04-20",
+        "Return results as JSON:\n<%= config.bin %> <%= command.id %> --json"
       ],
       "flags": {
         "json": {
@@ -1760,107 +2739,46 @@
           "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"
-        },
-        "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",
+        "session-id": {
+          "name": "session-id",
+          "summary": "Session ID used to filter the list of trace files. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs.",
           "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.",
+        "agent": {
+          "char": "a",
+          "name": "agent",
+          "summary": "API name of the agent used to filter the list of available trace files. Matches against the API name used when starting the session, either an authoring bundle or a published agent API name.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "test-runner": {
-          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
-          "name": "test-runner",
-          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+        "since": {
+          "description": "Accepts ISO 8601 format: date-only (2026-04-20), date-time (2026-04-20T14:00:00Z), or date-time with milliseconds (2026-04-20T14:00:00.000Z). The \"Recorded At\" values shown in the table output are valid inputs.",
+          "name": "since",
+          "summary": "Date used to filter the list of trace files; only those recorded on or after the date are listed.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "agentforce-studio",
-            "testing-center"
-          ],
           "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,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:test:results",
+      "id": "agent:trace:list",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Get the results of a completed agent test run.",
-      "enableJsonFlag": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
+      "summary": "List the available trace files that were recorded during all agent preview sessions.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
       "errorCodes": {
         "header": "ERROR CODES",
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Results retrieved successfully. Test results (passed/failed) are in the output."
-          },
-          {
-            "name": "NotFound (2)",
-            "description": "Job ID not found or invalid."
-          },
-          {
-            "name": "Failed (4)",
-            "description": "Failed to retrieve results due to API or network errors."
+            "description": "Trace files listed successfully (or empty list if none found)."
           }
         ]
       },
@@ -1869,27 +2787,31 @@
         "lib",
         "commands",
         "agent",
-        "test",
-        "results.js"
+        "trace",
+        "list.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:results",
-        "test:agent:results",
-        "test:results:agent",
-        "agent:results:test",
-        "results:agent:test",
-        "results:test:agent"
+        "agent:trace:list",
+        "trace:agent:list",
+        "trace:list:agent",
+        "agent:list:trace",
+        "list:agent:trace",
+        "list:trace:agent"
       ]
     },
-    "agent:test:resume": {
+    "agent:trace:read": {
       "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": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. Each turn (utterance or response) of a conversation creates trace data. Use this command to view trace data for a specific preview session, so you can then analyze the trace data to observe, monitor, investigate, and troubleshoot agent events and behavior.\n\nUse the --format flag to specify one of these formats of the outputted trace data:\n\n- summary (Default): A per-turn narrative showing topic routing, actions executed, and the agent's response. Use this to quickly understand what happened in a preview session.\n- detail: Diagnostic drill-down into a specific dimension. Filters output to only the trace steps relevant to that dimension, minimizing noise.\n- raw: Unprocessed trace JSON. Use this as a fallback when the trace schema has changed or you need to perform custom analysis.\n\nIf you specify \"--format detail\", you must also specify a dimension with the --dimension flag. Dimensions are a way to slice and analyze the agent execution trace from a specific angle or concern. Instead of looking at the raw sequence of everything that happened, each dimension filters and organizes the trace data to answer a specific type of question. These are the available dimensions and the information they provide:\n\n- actions: The actions the agent executed. Includes action name, input parameters, output, and latency. Use this dimension to understand what the agent actually did when answering an utterance in the preview session.\n- grounding: The reasoning steps used by the LLM. Use this dimension to see how the agent \"thought\" about the problem - the AI reasoning that determined which actions to take.\n- routing: How the agent navigated between subagents. Use this dimension to understand conversation flow - when and why the agent switched between different subagents or contexts during the conversation.\n- errors: Aggregates all errors during the session. Use this dimension to quickly identify and debug issues across all steps.",
       "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"
+        "Show a session trace summary for all turns in the session with the specified ID:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
+        "Show a trace summary for the second turn (utterance or response) of the conversation:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --turn 2",
+        "Drill into action execution across all turns:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension actions",
+        "Drill into routing decisions for the first turn of the conversation:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension routing --turn 1",
+        "Show all errors across the session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension errors",
+        "Output raw trace JSON for custom parsing:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format raw",
+        "Return results as JSON:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --json"
       ],
       "flags": {
         "json": {
@@ -1907,158 +2829,90 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
-          "noCacheDefault": true,
+        "session-id": {
+          "char": "s",
+          "name": "session-id",
           "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"
-        },
-        "job-id": {
-          "char": "i",
-          "name": "job-id",
-          "summary": "Job ID of the original agent test run.",
+          "summary": "Session ID to read traces for. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs",
           "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",
+        "format": {
+          "char": "f",
+          "name": "format",
+          "summary": "Output format of the trace data; specifies the level of detail you want in the trace files.",
+          "default": "summary",
           "hasDynamicHelp": false,
           "multiple": false,
           "options": [
-            "json",
-            "human",
-            "junit",
-            "tap"
+            "summary",
+            "detail",
+            "raw"
           ],
           "type": "option"
         },
-        "output-dir": {
+        "dimension": {
           "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.",
+          "name": "dimension",
+          "summary": "Dimension to drill into when using \"--format detail\"; used to filter and organize the trace data to answer a specific type of question.",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "actions",
+            "grounding",
+            "routing",
+            "errors"
+          ],
           "type": "option"
         },
-        "test-runner": {
-          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
-          "name": "test-runner",
-          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+        "turn": {
+          "char": "t",
+          "name": "turn",
+          "summary": "Turn number for which you want trace data. A turn is a single utterance or response in a conversation, starting with 1.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "agentforce-studio",
-            "testing-center"
-          ],
           "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,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:test:resume",
+      "id": "agent:trace:read",
       "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": "Read trace files from an agent preview session.",
       "enableJsonFlag": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Test completed successfully (with test results in the output)."
-          },
-          {
-            "name": "Failed (1)",
-            "description": "Tests encountered execution errors (test cases with ERROR status)."
-          },
-          {
-            "name": "NotFound (2)",
-            "description": "Job ID not found or invalid."
-          },
-          {
-            "name": "OperationFailed (4)",
-            "description": "Failed to poll test due to API or network errors."
-          }
-        ]
-      },
+      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "test",
-        "resume.js"
+        "trace",
+        "read.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:resume",
-        "test:agent:resume",
-        "test:resume:agent",
-        "agent:resume:test",
-        "resume:agent:test",
-        "resume:test:agent"
+        "agent:trace:read",
+        "trace:agent:read",
+        "trace:read:agent",
+        "agent:read:trace",
+        "read:agent:trace",
+        "read:trace:agent"
       ]
     },
-    "agent:test:run-eval": {
+    "agent:preview:end": {
       "aliases": [],
       "args": {},
-      "description": "Specify the tests you want to run with one of these inputs to the --spec flag:\n\n- YAML test spec generated by the `agent generate test-spec` CLI command\n- JSON payload\n\nWhen you provide a YAML test spec, this command automatically translates test cases into internal state-based evaluation framework calls and infers the agent name from the test spec's `subjectName` field. As a result, you can use the same test spec with both the `agent test run` and `agent test run-eval` commands. YAML test specs also support context variables, 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 evaluation framework 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 as when you use a YAML test spec.\n\nThis command supports more than 8 evaluator types, including subagent routing assertions, action invocation checks, string/numeric assertions, semantic similarity scoring, and LLM-based quality ratings.",
+      "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, respectively. 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\nUse the --all flag to end all active preview sessions at once. You can combine --all with --api-name or --authoring-bundle to end only sessions for a specific agent, or use --all on its own to end every session across all agents in the project.",
       "examples": [
-        "Run tests using a YAML test spec on the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --spec specs/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 specs/my-agent-testSpec.yaml --api-name My_Agent",
-        "Run tests using a JSON payload:\n<%= config.bin %> <%= command.id %> --spec specs/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 specs/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 specs/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"
+        "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",
+        "End all active preview sessions for a specific agent without prompting:\n<%= config.bin %> <%= command.id %> --all --authoring-bundle My_Local_Agent --target-org <target_org> --no-prompt",
+        "End all active preview sessions across every agent in the local session cache for an org:\n<%= config.bin %> <%= command.id %> --all --target-org <target_org>"
       ],
       "flags": {
         "json": {
@@ -2093,62 +2947,65 @@
           "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.",
+        "session-id": {
+          "exclusive": [
+            "all"
+          ],
+          "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",
+          "exclusive": [
+            "authoring-bundle"
+          ],
           "name": "api-name",
-          "summary": "Agent API name (also called DeveloperName) used to resolve agent_id and agent_version_id. Auto-inferred from the YAML spec's subjectName.",
+          "summary": "API name of the activated published agent you want to preview.",
           "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"
+        "authoring-bundle": {
+          "exclusive": [
+            "api-name"
           ],
-          "type": "option"
-        },
-        "batch-size": {
-          "name": "batch-size",
-          "summary": "Number of tests per API request (max 5).",
-          "default": 5,
+          "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"
         },
-        "no-normalize": {
-          "name": "no-normalize",
-          "summary": "Disable auto-normalization of field names and shorthand references.",
+        "all": {
+          "exclusive": [
+            "session-id"
+          ],
+          "name": "all",
+          "summary": "End all active preview sessions. Combine with --api-name or --authoring-bundle to limit to a specific agent, or use with only --target-org to end sessions for all agents found in the local session cache. Requires --target-org.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "no-prompt": {
+          "char": "p",
+          "name": "no-prompt",
+          "summary": "Don't prompt for confirmation before ending sessions. Has an effect only when used with --all.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:test:run-eval",
+      "id": "agent:preview:end",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
-      "summary": "Run rich evaluation tests against an Agentforce agent.",
+      "summary": "End an existing programmatic agent preview session and get trace location.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "envVariablesSection": {
         "header": "ENVIRONMENT VARIABLES",
         "body": [
@@ -2163,19 +3020,27 @@
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Tests completed successfully. Test results (passed/failed) are in the JSON output."
+            "description": "Preview session ended successfully and traces saved."
           },
           {
-            "name": "Failed (1)",
-            "description": "Tests encountered execution errors (tests couldn't run properly)."
+            "name": "ExactlyOneRequired (2)",
+            "description": "Neither --api-name nor --authoring-bundle was provided (required when --all is not set)."
           },
           {
             "name": "NotFound (2)",
-            "description": "Agent not found, spec file not found, or invalid agent name."
+            "description": "Agent not found, or no preview session exists for this agent."
           },
           {
-            "name": "OperationFailed (4)",
-            "description": "Failed to execute tests due to API or network errors."
+            "name": "PreviewEndFailed (4)",
+            "description": "Failed to end the preview session."
+          },
+          {
+            "name": "PreviewEndPartialFailure (68)",
+            "description": "With --all, one or more sessions failed to end while others succeeded."
+          },
+          {
+            "name": "SessionAmbiguous (5)",
+            "description": "Multiple preview sessions found; specify --session-id to choose one."
           }
         ]
       },
@@ -2184,27 +3049,27 @@
         "lib",
         "commands",
         "agent",
-        "test",
-        "run-eval.js"
+        "preview",
+        "end.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:preview:end",
+        "preview:agent:end",
+        "preview:end:agent",
+        "agent:end:preview",
+        "end:agent:preview",
+        "end:preview:agent"
       ]
     },
-    "agent:test:run": {
+    "agent:preview:send": {
       "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": "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": [
-        "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"
+        "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": {
@@ -2239,74 +3104,49 @@
           "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.",
+        "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"
         },
-        "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",
+        "utterance": {
+          "char": "u",
+          "name": "utterance",
+          "required": true,
+          "summary": "Utterance to send to the agent, enclosed in double quotes.",
           "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 activated published agent you want to preview.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "test-runner": {
-          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
-          "name": "test-runner",
-          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+        "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,
-          "options": [
-            "agentforce-studio",
-            "testing-center"
-          ],
           "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:preview:send",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Start an agent test in your org.",
+      "summary": "Send a message to an existing agent preview session.",
       "enableJsonFlag": true,
+      "requiresProject": true,
       "envVariablesSection": {
         "header": "ENVIRONMENT VARIABLES",
         "body": [
@@ -2321,19 +3161,19 @@
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Test started successfully (without --wait), or test completed successfully (with --wait)."
+            "description": "Message sent successfully and agent response received."
           },
           {
-            "name": "Failed (1)",
-            "description": "Tests encountered execution errors (test cases with ERROR status when using --wait)."
+            "name": "NotFound (2)",
+            "description": "Agent not found, or no preview session exists for this agent."
           },
           {
-            "name": "NotFound (2)",
-            "description": "Test definition not found or invalid test name."
+            "name": "PreviewSendFailed (4)",
+            "description": "Failed to send message or receive response from the preview session."
           },
           {
-            "name": "OperationFailed (4)",
-            "description": "Failed to start or poll test due to API or network errors."
+            "name": "SessionAmbiguous (5)",
+            "description": "Multiple preview sessions found; specify --session-id to choose one."
           }
         ]
       },
@@ -2342,30 +3182,88 @@
         "lib",
         "commands",
         "agent",
-        "test",
-        "run.js"
+        "preview",
+        "send.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:test:run",
-        "test:agent:run",
-        "test:run:agent",
-        "agent:run:test",
-        "run:agent:test",
-        "run:test:agent"
+        "agent:preview:send",
+        "preview:agent:send",
+        "preview:send:agent",
+        "agent:send:preview",
+        "send:agent:preview",
+        "send:preview:agent"
       ]
     },
-    "agent:trace:delete": {
+    "agent:preview:sessions": {
       "aliases": [],
       "args": {},
-      "description": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. Use this command to delete some or all of the trace files.\n\nBy default, this command shows a preview of what will be deleted and prompts for confirmation. Use --no-prompt to skip confirmation.\n\nWithout filters, this comamnd deletes all trace files for all agents and sessions. Use flags to narrow the scope: filter by agent API name (--agent), by session (--session-id), or by age (--older-than).",
+      "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": [
-        "Delete all traces for all agents and sessions; prompt for confirmation:\n<%= config.bin %> <%= command.id %>",
-        "Delete all traces for a specific agent:\n<%= config.bin %> <%= command.id %> --agent My_Agent",
-        "Delete traces from a specific session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
-        "Delete traces older than 7 days:\n<%= config.bin %> <%= command.id %> --older-than 7d",
-        "Delete traces older than 24 hours for a specific agent; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --agent My_Agent --older-than 24h --no-prompt",
-        "Delete all traces for all agents and sessions; don't prompt for confirmation:\n<%= config.bin %> <%= command.id %> --no-prompt"
+        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
+      ],
+      "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"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "agent:preview:sessions",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "List all known programmatic agent preview sessions.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Sessions listed successfully (or empty list if no active sessions)."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "preview",
+        "sessions.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:preview:sessions",
+        "preview:agent:sessions",
+        "preview:sessions:agent",
+        "agent:sessions:preview",
+        "sessions:agent:preview",
+        "sessions:preview:agent"
+      ]
+    },
+    "agent:preview:start": {
+      "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 with --authoring-bundle, you must explicitly specify the execution mode using one of these flags:\n\n- --use-live-actions: Executes real Apex classes, flows, and other actions in the org. This surfaces compile and validation errors during preview.\n- --simulate-actions: Uses AI to simulate action execution without calling real implementations.\n\nPublished agents (--api-name) always use live actions. The mode flags are optional and have no effect for published agents.",
+      "examples": [
+        "Start a programmatic agent preview session by specifying an authoring bundle; use simulated actions. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --target-org my-dev-org --simulate-actions",
+        "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 (always uses live actions):\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent"
       ],
       "flags": {
         "json": {
@@ -2383,51 +3281,109 @@
           "multiple": false,
           "type": "option"
         },
-        "agent": {
-          "char": "a",
-          "name": "agent",
-          "summary": "API name of the agent used to filter the list of trace files you want to delete. Matches against the API name used when starting the session, either an authoring bundle or a published agent API name.",
+        "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"
         },
-        "session-id": {
-          "name": "session-id",
-          "summary": "Session ID used to filter the list of trace files you want to delete. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs.",
+        "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"
         },
-        "older-than": {
-          "name": "older-than",
-          "summary": "Duration used to filter the list of trace files; only files older than the duration are deleted. Accepts a number followed by a unit: m/minutes, h/hours, d/days, w/weeks. Examples: 7d, 24h, 2w.",
+        "use-live-actions": {
+          "exclusive": [
+            "simulate-actions"
+          ],
+          "name": "use-live-actions",
+          "summary": "Execute real actions in the org (Apex classes, flows, etc.). Required with --authoring-bundle.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "simulate-actions": {
+          "exclusive": [
+            "use-live-actions"
+          ],
+          "name": "simulate-actions",
+          "summary": "Use AI to simulate action execution instead of calling real actions. Required with --authoring-bundle.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "agent-json": {
+          "dependsOn": [
+            "authoring-bundle"
+          ],
+          "hidden": true,
+          "name": "agent-json",
+          "summary": "Path to a pre-compiled AgentJSON file to use instead of compiling the Agent Script file. Intended for internal use and testing.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
-        },
-        "no-prompt": {
-          "name": "no-prompt",
-          "summary": "Skip the confirmation prompt and delete immediately.",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:trace:delete",
+      "id": "agent:preview:start",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Delete trace files from an agent preview session.",
+      "summary": "Start a programmatic agent preview session.",
       "enableJsonFlag": true,
       "requiresProject": true,
+      "envVariablesSection": {
+        "header": "ENVIRONMENT VARIABLES",
+        "body": [
+          {
+            "name": "SF_TARGET_ORG",
+            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
+          }
+        ]
+      },
       "errorCodes": {
         "header": "ERROR CODES",
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Traces deleted successfully (or no traces matched)."
+            "description": "Preview session started successfully."
+          },
+          {
+            "name": "Failed (1)",
+            "description": "Agent Script compilation failed (syntax errors in the script)."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Agent not found, or compilation API returned HTTP 404 (endpoint may not be available in your org or region)."
+          },
+          {
+            "name": "ServerError (3)",
+            "description": "Compilation API returned HTTP 500 (server error during compilation)."
+          },
+          {
+            "name": "PreviewStartFailed (4)",
+            "description": "Preview session failed to start due to API or network errors."
           }
         ]
       },
@@ -2436,31 +3392,25 @@
         "lib",
         "commands",
         "agent",
-        "trace",
-        "delete.js"
+        "preview",
+        "start.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:trace:delete",
-        "trace:agent:delete",
-        "trace:delete:agent",
-        "agent:delete:trace",
-        "delete:agent:trace",
-        "delete:trace:agent"
+        "agent:preview:start",
+        "preview:agent:start",
+        "preview:start:agent",
+        "agent:start:preview",
+        "start:agent:preview",
+        "start:preview:agent"
       ]
     },
-    "agent:trace:list": {
+    "agent:adl:file:add": {
       "aliases": [],
       "args": {},
-      "description": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. By default, this command lists all trace files for all agents and all of their sessions. Use flags to narrow results: filter by agent name (--agent), by session (--session-id), or by date (--since).\n\nEach row in the output corresponds to one trace file, which in turn corresponds to one agent session. The Agent column shows the authoring bundle or API name used when starting the session.",
+      "description": "Adds one or more files to an existing SFDRIVE data library and triggers SearchIndex re-hydration. This is the day-2 operation for adding files to an already-provisioned library.\n\nConstraints: at least 1 file required, no duplicate file names in a batch, maximum 1000 files per library.",
       "examples": [
-        "List all trace files for all agents and sessions:\n<%= config.bin %> <%= command.id %>",
-        "List all trace files for a specific agent:\n<%= config.bin %> <%= command.id %> --agent My_Agent",
-        "List trace files for a specific session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
-        "List trace files recorded on or after April 20, 2026 (date-only, interpreted as UTC midnight):\n<%= config.bin %> <%= command.id %> --since 2026-04-20",
-        "List trace files recorded on or after a specific UTC time:\n<%= config.bin %> <%= command.id %> --since 2026-04-20T14:00:00Z",
-        "Filter by agent and date together:\n<%= config.bin %> <%= command.id %> --agent My_Agent --since 2026-04-20",
-        "Return results as JSON:\n<%= config.bin %> <%= command.id %> --json"
+        "Add a file to an existing library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/new-guide.pdf --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -2478,79 +3428,95 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "name": "session-id",
-          "summary": "Session ID used to filter the list of trace files. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs.",
+        "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"
         },
-        "agent": {
-          "char": "a",
-          "name": "agent",
-          "summary": "API name of the agent used to filter the list of available trace files. Matches against the API name used when starting the session, either an authoring bundle or a published agent API name.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "since": {
-          "description": "Accepts ISO 8601 format: date-only (2026-04-20), date-time (2026-04-20T14:00:00Z), or date-time with milliseconds (2026-04-20T14:00:00.000Z). The \"Recorded At\" values shown in the table output are valid inputs.",
-          "name": "since",
-          "summary": "Date used to filter the list of trace files; only those recorded on or after the date are listed.",
+        "file": {
+          "char": "f",
+          "name": "file",
+          "required": true,
+          "summary": "Path to the file to add to the library.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:trace:list",
+      "id": "agent:adl:file:add",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "List the available trace files that were recorded during all agent preview sessions.",
+      "summary": "Add files to an existing Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Trace files listed successfully (or empty list if none found)."
-          }
-        ]
-      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "trace",
-        "list.js"
+        "adl",
+        "file",
+        "add.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:trace:list",
-        "trace:agent:list",
-        "trace:list:agent",
-        "agent:list:trace",
-        "list:agent:trace",
-        "list:trace:agent"
+        "agent:adl:file:add",
+        "adl:agent:file:add",
+        "adl:file:agent:add",
+        "adl:file:add:agent",
+        "agent:file:adl:add",
+        "file:agent:adl:add",
+        "file:adl:agent:add",
+        "file:adl:add:agent",
+        "agent:file:add:adl",
+        "file:agent:add:adl",
+        "file:add:agent:adl",
+        "file:add:adl:agent",
+        "agent:adl:add:file",
+        "adl:agent:add:file",
+        "adl:add:agent:file",
+        "adl:add:file:agent",
+        "agent:add:adl:file",
+        "add:agent:adl:file",
+        "add:adl:agent:file",
+        "add:adl:file:agent",
+        "agent:add:file:adl",
+        "add:agent:file:adl",
+        "add:file:agent:adl",
+        "add:file:adl:agent"
       ]
     },
-    "agent:trace:read": {
+    "agent:adl:file:delete": {
       "aliases": [],
       "args": {},
-      "description": "When you run an agent preview conversation (either interactive or programmatic), trace files are automatically recorded and saved in your local DX project. Each turn (utterance or response) of a conversation creates trace data. Use this command to view trace data for a specific preview session, so you can then analyze the trace data to observe, monitor, investigate, and troubleshoot agent events and behavior.\n\nUse the --format flag to specify one of these formats of the outputted trace data:\n\n- summary (Default): A per-turn narrative showing topic routing, actions executed, and the agent's response. Use this to quickly understand what happened in a preview session.\n- detail: Diagnostic drill-down into a specific dimension. Filters output to only the trace steps relevant to that dimension, minimizing noise.\n- raw: Unprocessed trace JSON. Use this as a fallback when the trace schema has changed or you need to perform custom analysis.\n\nIf you specify \"--format detail\", you must also specify a dimension with the --dimension flag. Dimensions are a way to slice and analyze the agent execution trace from a specific angle or concern. Instead of looking at the raw sequence of everything that happened, each dimension filters and organizes the trace data to answer a specific type of question. These are the available dimensions and the information they provide:\n\n- actions: The actions the agent executed. Includes action name, input parameters, output, and latency. Use this dimension to understand what the agent actually did when answering an utterance in the preview session.\n- grounding: The reasoning steps used by the LLM. Use this dimension to see how the agent \"thought\" about the problem - the AI reasoning that determined which actions to take.\n- routing: How the agent navigated between subagents. Use this dimension to understand conversation flow - when and why the agent switched between different subagents or contexts during the conversation.\n- errors: Aggregates all errors during the session. Use this dimension to quickly identify and debug issues across all steps.",
+      "description": "Permanently removes a file from an SFDRIVE data library and triggers re-indexing of the search index.",
       "examples": [
-        "Show a session trace summary for all turns in the session with the specified ID:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
-        "Show a trace summary for the second turn (utterance or response) of the conversation:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --turn 2",
-        "Drill into action execution across all turns:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension actions",
-        "Drill into routing decisions for the first turn of the conversation:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension routing --turn 1",
-        "Show all errors across the session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format detail --dimension errors",
-        "Output raw trace JSON for custom parsing:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --format raw",
-        "Return results as JSON:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --json"
+        "Delete a file from a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file-id a1B2C3D4E5F6G7H8I9 --target-org myOrg"
       ],
       "flags": {
         "json": {
@@ -2568,87 +3534,95 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "char": "s",
-          "name": "session-id",
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
           "required": true,
-          "summary": "Session ID to read traces for. Use the \"agent preview sessions\" CLI command to list all known agent preview sessions along with their session IDs",
-          "hasDynamicHelp": false,
+          "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"
         },
-        "format": {
-          "char": "f",
-          "name": "format",
-          "summary": "Output format of the trace data; specifies the level of detail you want in the trace files.",
-          "default": "summary",
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "summary",
-            "detail",
-            "raw"
-          ],
           "type": "option"
         },
-        "dimension": {
-          "char": "d",
-          "name": "dimension",
-          "summary": "Dimension to drill into when using \"--format detail\"; used to filter and organize the trace data to answer a specific type of question.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "actions",
-            "grounding",
-            "routing",
-            "errors"
-          ],
           "type": "option"
         },
-        "turn": {
-          "char": "t",
-          "name": "turn",
-          "summary": "Turn number for which you want trace data. A turn is a single utterance or response in a conversation, starting with 1.",
+        "file-id": {
+          "name": "file-id",
+          "required": true,
+          "summary": "ID of the file to delete (AiGroundingFileRef record ID).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:trace:read",
+      "id": "agent:adl:file:delete",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Read trace files from an agent preview session.",
+      "summary": "Delete a file from an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "trace",
-        "read.js"
+        "adl",
+        "file",
+        "delete.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:trace:read",
-        "trace:agent:read",
-        "trace:read:agent",
-        "agent:read:trace",
-        "read:agent:trace",
-        "read:trace:agent"
+        "agent:adl:file:delete",
+        "adl:agent:file:delete",
+        "adl:file:agent:delete",
+        "adl:file:delete:agent",
+        "agent:file:adl:delete",
+        "file:agent:adl:delete",
+        "file:adl:agent:delete",
+        "file:adl:delete:agent",
+        "agent:file:delete:adl",
+        "file:agent:delete:adl",
+        "file:delete:agent:adl",
+        "file:delete:adl:agent",
+        "agent:adl:delete:file",
+        "adl:agent:delete:file",
+        "adl:delete:agent:file",
+        "adl:delete:file:agent",
+        "agent:delete:adl:file",
+        "delete:agent:adl:file",
+        "delete:adl:agent:file",
+        "delete:adl:file:agent",
+        "agent:delete:file:adl",
+        "delete:agent:file:adl",
+        "delete:file:agent:adl",
+        "delete:file:adl:agent"
       ]
     },
-    "agent:validate:authoring-bundle": {
+    "agent:adl:file:list": {
       "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": "Returns the list of files in an SFDRIVE library including file name, size, and creation date.",
       "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"
+        "List files in a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg",
+        "List files and output as JSON:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg --json"
       ],
       "flags": {
         "json": {
@@ -2683,10 +3657,11 @@
           "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.",
+        "library-id": {
+          "char": "i",
+          "name": "library-id",
+          "required": true,
+          "summary": "Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
@@ -2694,68 +3669,51 @@
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:validate:authoring-bundle",
+      "id": "agent:adl:file:list",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
+      "state": "preview",
       "strict": true,
-      "summary": "Validate an authoring bundle to ensure its Agent Script file compiles successfully and can be used to publish an agent.",
+      "summary": "List files in an Agentforce Data Library.",
       "enableJsonFlag": true,
-      "requiresProject": true,
-      "envVariablesSection": {
-        "header": "ENVIRONMENT VARIABLES",
-        "body": [
-          {
-            "name": "SF_TARGET_ORG",
-            "description": "Username or alias of your default org. Overrides the target-org configuration variable."
-          }
-        ]
-      },
-      "errorCodes": {
-        "header": "ERROR CODES",
-        "body": [
-          {
-            "name": "Succeeded (0)",
-            "description": "Agent Script file compiled successfully without errors."
-          },
-          {
-            "name": "Failed (1)",
-            "description": "Compilation errors found in the Agent Script file."
-          },
-          {
-            "name": "NotFound (2)",
-            "description": "Validation/compilation API returned HTTP 404. The API endpoint may not be available in your org or region."
-          },
-          {
-            "name": "ServerError (3)",
-            "description": "Validation/compilation API returned HTTP 500. A server error occurred during compilation."
-          }
-        ]
-      },
-      "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",
-        "validate",
-        "authoring-bundle.js"
+        "adl",
+        "file",
+        "list.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:adl:file:list",
+        "adl:agent:file:list",
+        "adl:file:agent:list",
+        "adl:file:list:agent",
+        "agent:file:adl:list",
+        "file:agent:adl:list",
+        "file:adl:agent:list",
+        "file:adl:list:agent",
+        "agent:file:list:adl",
+        "file:agent:list:adl",
+        "file:list:agent:adl",
+        "file:list:adl:agent",
+        "agent:adl:list:file",
+        "adl:agent:list:file",
+        "adl:list:agent:file",
+        "adl:list:file:agent",
+        "agent:list:adl:file",
+        "list:agent:adl:file",
+        "list:adl:agent:file",
+        "list:adl:file:agent",
+        "agent:list:file:adl",
+        "list:agent:file:adl",
+        "list:file:agent:adl",
+        "list:file:adl:agent"
       ]
     }
   },
-  "version": "1.41.0"
+  "version": "1.42.0"
 }