@salesforce/plugin-agent 1.36.1 → 1.38.0

package/oclif.manifest.json

@@ -409,16 +409,14 @@
         "preview:agent"
       ]
     },
-    "agent:generate:agent-spec": {
+    "agent:preview:end": {
       "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": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to end it. This command also displays the local directory where the session trace files are stored.\n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to end the session. You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely. To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory. Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
       "examples": [
-        "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"
+        "End a preview session of a published agent by specifying its session ID and API name ; use the default org:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --api-name My_Published_Agent",
+        "Similar to previous example, but don't specify a session ID; you get an error if the published agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent --target-org my-dev-org",
+        "End a preview session of an agent using its authoring bundle API name; you get an error if the agent has more than one active session.\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Local_Agent"
       ],
       "flags": {
         "json": {
@@ -453,164 +451,96 @@
           "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",
+        "session-id": {
+          "name": "session-id",
+          "required": false,
+          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see the list of all sessions.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "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.",
+        "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"
         },
-        "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.",
+        "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"
-        },
-        "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:preview:end",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
+      "summary": "End an existing programmatic agent preview session and get trace location.",
       "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": "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": "SessionAmbiguous (5)",
+            "description": "Multiple preview sessions found; specify --session-id to choose one."
+          }
+        ]
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "agent-spec.js"
+        "preview",
+        "end.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:preview:end",
+        "preview:agent:end",
+        "preview:end:agent",
+        "agent:end:preview",
+        "end:agent:preview",
+        "end:preview:agent"
       ]
     },
-    "agent:generate:authoring-bundle": {
+    "agent:preview:send": {
       "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": "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": [
-        "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"
+        "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": {
@@ -638,13 +568,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 +575,103 @@
           "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.",
+        "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"
         },
-        "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.",
+        "utterance": {
+          "char": "u",
+          "name": "utterance",
+          "required": true,
+          "summary": "Utterance to send to the agent, enclosed in double quotes.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "name": {
+        "api-name": {
           "char": "n",
-          "name": "name",
-          "summary": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
+          "name": "api-name",
+          "summary": "API name of the activated published agent you want to preview.",
           "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"
+        "authoring-bundle": {
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:authoring-bundle",
+      "id": "agent:preview:send",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
+      "summary": "Send a message to an existing agent preview session.",
       "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"
+      "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"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:preview:send",
+        "preview:agent:send",
+        "preview:send:agent",
+        "agent:send:preview",
+        "send:agent:preview",
+        "send:preview:agent"
       ]
     },
-    "agent:generate:template": {
+    "agent:preview:sessions": {
       "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": "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": [
-        "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"
+        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
       ],
       "flags": {
         "json": {
@@ -739,88 +688,62 @@
           "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,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:generate:template",
+      "id": "agent:preview:sessions",
       "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.",
+      "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",
-        "generate",
-        "template.js"
+        "preview",
+        "sessions.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:template",
-        "generate:agent:template",
-        "generate:template:agent",
-        "agent:template:generate",
-        "template:agent:generate",
-        "template:generate:agent"
+        "agent:preview:sessions",
+        "preview:agent:sessions",
+        "preview:sessions:agent",
+        "agent:sessions:preview",
+        "sessions:agent:preview",
+        "sessions:preview:agent"
       ]
     },
-    "agent:generate:test-spec": {
+    "agent:preview:start": {
       "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": "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": [
-        "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"
+        "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": {
+          "description": "Format output as json.",
+          "helpGroup": "GLOBAL",
+          "name": "json",
+          "allowNo": false,
+          "type": "boolean"
+        },
         "flags-dir": {
           "helpGroup": "GLOBAL",
           "name": "flags-dir",
@@ -829,64 +752,140 @@
           "multiple": false,
           "type": "option"
         },
-        "from-definition": {
-          "char": "d",
-          "name": "from-definition",
-          "summary": "Filepath to the AIEvaluationDefinition metadata XML file in your DX project that you want to convert to a test spec YAML file.",
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Don't prompt for confirmation when overwriting an existing test spec YAML file.",
+        "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"
+        },
+        "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"
         },
-        "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\".",
+        "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"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:generate:test-spec",
+      "id": "agent:preview:start",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.",
-      "enableJsonFlag": false,
+      "summary": "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": "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."
+          }
+        ]
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "generate",
-        "test-spec.js"
+        "preview",
+        "start.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:preview:start",
+        "preview:agent:start",
+        "preview:start:agent",
+        "agent:start:preview",
+        "start:agent:preview",
+        "start:preview:agent"
       ]
     },
-    "agent:preview:end": {
+    "agent:generate:agent-spec": {
       "aliases": [],
       "args": {},
-      "description": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to end it. This command also displays the local directory where the session trace files are stored.\n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to end the session. You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely. To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory. Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.",
+      "description": "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": [
-        "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"
+        "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": {
@@ -921,96 +920,164 @@
           "multiple": false,
           "type": "option"
         },
-        "session-id": {
-          "name": "session-id",
-          "required": false,
-          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see the list of all sessions.",
+        "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"
         },
-        "api-name": {
-          "char": "n",
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
+        "company-name": {
+          "name": "company-name",
+          "summary": "Name of your company.",
           "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.",
+        "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:preview:end",
+      "id": "agent:generate:agent-spec",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "End an existing programmatic agent preview session and get trace location.",
+      "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
       "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": "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": "SessionAmbiguous (5)",
-            "description": "Multiple preview sessions found; specify --session-id to choose one."
-          }
-        ]
-      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "preview",
-        "end.js"
+        "generate",
+        "agent-spec.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:end",
-        "preview:agent:end",
-        "preview:end:agent",
-        "agent:end:preview",
-        "end:agent:preview",
-        "end:preview:agent"
+        "agent:generate:agent-spec",
+        "generate:agent:agent-spec",
+        "generate:agent-spec:agent",
+        "agent:agent-spec:generate",
+        "agent-spec:agent:generate",
+        "agent-spec:generate:agent"
       ]
     },
-    "agent:preview:send": {
+    "agent:generate:authoring-bundle": {
       "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": "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": [
-        "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"
+        "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": {
@@ -1038,6 +1105,13 @@
           "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",
@@ -1045,103 +1119,77 @@
           "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.",
+        "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"
         },
-        "utterance": {
-          "char": "u",
-          "name": "utterance",
-          "required": true,
-          "summary": "Utterance to send to the agent, enclosed in double quotes.",
+        "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"
         },
-        "api-name": {
+        "name": {
           "char": "n",
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
+          "name": "name",
+          "summary": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
           "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"
+        "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:preview:send",
+      "id": "agent:generate:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "Send a message to an existing agent preview session.",
+      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
       "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"
+        "generate",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:send",
-        "preview:agent:send",
-        "preview:send:agent",
-        "agent:send:preview",
-        "send:agent:preview",
-        "send:preview:agent"
+        "agent:generate:authoring-bundle",
+        "generate:agent:authoring-bundle",
+        "generate:authoring-bundle:agent",
+        "agent:authoring-bundle:generate",
+        "authoring-bundle:agent:generate",
+        "authoring-bundle:generate:agent"
       ]
     },
-    "agent:preview:sessions": {
+    "agent:generate:template": {
       "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": "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": [
-        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
+        "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": {
@@ -1158,62 +1206,88 @@
           "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": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:sessions",
+      "id": "agent:generate:template",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "List all known programmatic agent preview sessions.",
+      "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,
-      "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"
+        "generate",
+        "template.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:sessions",
-        "preview:agent:sessions",
-        "preview:sessions:agent",
-        "agent:sessions:preview",
-        "sessions:agent:preview",
-        "sessions:preview:agent"
+        "agent:generate:template",
+        "generate:agent:template",
+        "generate:template:agent",
+        "agent:template:generate",
+        "template:agent:generate",
+        "template:generate:agent"
       ]
     },
-    "agent:preview:start": {
+    "agent:generate:test-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": "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": [
-        "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 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": {
-        "json": {
-          "description": "Format output as json.",
-          "helpGroup": "GLOBAL",
-          "name": "json",
-          "allowNo": false,
-          "type": "boolean"
-        },
         "flags-dir": {
           "helpGroup": "GLOBAL",
           "name": "flags-dir",
@@ -1222,128 +1296,54 @@
           "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 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.",
+        "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"
         },
-        "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.",
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Don't prompt for confirmation when overwriting an existing test spec YAML file.",
           "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.",
+        "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": true,
+      "hasDynamicHelp": false,
       "hiddenAliases": [],
-      "id": "agent:preview:start",
+      "id": "agent:generate:test-spec",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "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": "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."
-          }
-        ]
-      },
+      "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",
-        "preview",
-        "start.js"
+        "generate",
+        "test-spec.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:start",
-        "preview:agent:start",
-        "preview:start:agent",
-        "agent:start:preview",
-        "start:agent:preview",
-        "start:preview:agent"
+        "agent:generate:test-spec",
+        "generate:agent:test-spec",
+        "generate:test-spec:agent",
+        "agent:test-spec:generate",
+        "test-spec:agent:generate",
+        "test-spec:generate:agent"
       ]
     },
     "agent:publish:authoring-bundle": {
@@ -2062,15 +2062,6 @@
           "multiple": false,
           "type": "option"
         },
-        "wait": {
-          "char": "w",
-          "name": "wait",
-          "summary": "Number of minutes to wait for results.",
-          "default": 10,
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
         "result-format": {
           "name": "result-format",
           "summary": "Format of the agent test run results.",
@@ -2101,13 +2092,11 @@
         }
       },
       "hasDynamicHelp": true,
-      "hidden": true,
       "hiddenAliases": [],
       "id": "agent:test:run-eval",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "beta",
       "strict": true,
       "summary": "Run evaluation tests against an Agentforce agent.",
       "enableJsonFlag": true,
@@ -2317,6 +2306,293 @@
         "run:test:agent"
       ]
     },
+    "agent:trace:delete": {
+      "aliases": [],
+      "args": {},
+      "description": "Deletes trace files recorded during agent preview sessions. By default, shows a preview of what will be deleted and prompts for confirmation. Use --no-prompt to skip confirmation.\n\nWithout filters, deletes all traces for all agents and sessions. Use flags to narrow the scope: filter by agent name (--agent), by session (--session-id), or by age (--older-than).",
+      "examples": [
+        "Delete all traces for all agents and sessions (with confirmation prompt):\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, no prompt:\n<%= config.bin %> <%= command.id %> --agent My_Agent --older-than 24h --no-prompt",
+        "Delete all traces without confirmation:\n<%= config.bin %> <%= command.id %> --no-prompt"
+      ],
+      "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"
+        },
+        "agent": {
+          "char": "a",
+          "name": "agent",
+          "summary": "Only delete traces for this agent name (substring match). Matches against the name used when starting the session, whether that's an authoring bundle or a published agent API name.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "session-id": {
+          "name": "session-id",
+          "summary": "Only delete traces from this session ID.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "older-than": {
+          "name": "older-than",
+          "summary": "Only delete traces older than this duration. Accepts a number followed by a unit: m/minutes, h/hours, d/days, w/weeks (e.g. 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": false,
+      "hiddenAliases": [],
+      "id": "agent:trace:delete",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Delete agent preview trace files.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "errorCodes": {
+        "header": "ERROR CODES",
+        "body": [
+          {
+            "name": "Succeeded (0)",
+            "description": "Traces deleted successfully (or no traces matched)."
+          }
+        ]
+      },
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "trace",
+        "delete.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:trace:delete",
+        "trace:agent:delete",
+        "trace:delete:agent",
+        "agent:delete:trace",
+        "delete:agent:trace",
+        "delete:trace:agent"
+      ]
+    },
+    "agent:trace:list": {
+      "aliases": [],
+      "args": {},
+      "description": "Lists trace files recorded during agent preview sessions. By default, lists all traces 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": [
+        "List all traces for all agents and sessions:\n<%= config.bin %> <%= command.id %>",
+        "List all traces for a specific agent:\n<%= config.bin %> <%= command.id %> --agent My_Agent",
+        "List traces for a specific session:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
+        "List traces recorded on or after April 20, 2026 (date-only, interpreted as UTC midnight):\n<%= config.bin %> <%= command.id %> --since 2026-04-20",
+        "List traces 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": {
+          "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"
+        },
+        "session-id": {
+          "name": "session-id",
+          "summary": "Session ID used to filter the list of trace files.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "agent": {
+          "char": "a",
+          "name": "agent",
+          "summary": "Only show traces for this agent name (substring match). Matches against the name used when starting the session, whether that's an authoring bundle or a published agent API name.",
+          "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.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "agent:trace:list",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "List the trace files that were recorded during all agent preview sessions.",
+      "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"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:trace:list",
+        "trace:agent:list",
+        "trace:list:agent",
+        "agent:list:trace",
+        "list:agent:trace",
+        "list:trace:agent"
+      ]
+    },
+    "agent:trace:read": {
+      "aliases": [],
+      "args": {},
+      "description": "Reads trace files recorded during an agent preview session and outputs them in one of three formats.\n\n**--format 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 session.\n\n**--format detail**: Diagnostic drill-down into a specific dimension (--dimension required). Filters output to only the trace steps relevant to that dimension, minimizing noise.\n\n**--format raw**: Unprocessed trace JSON. Use this as a fallback when the trace schema has changed or you need to perform custom analysis.\n\nAvailable dimensions for --format detail: actions, grounding, routing, errors.\n\nUse --turn N to scope output to a single conversation turn.",
+      "examples": [
+        "Show a session summary (all turns):\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID>",
+        "Show summary for a single turn:\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 a specific turn:\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": {
+          "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"
+        },
+        "session-id": {
+          "char": "s",
+          "name": "session-id",
+          "required": true,
+          "summary": "Session ID to read traces for.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "format": {
+          "char": "f",
+          "name": "format",
+          "summary": "Output format: summary (default), detail, or raw. Use detail with --dimension to drill into a specific aspect of the trace.",
+          "default": "summary",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "summary",
+            "detail",
+            "raw"
+          ],
+          "type": "option"
+        },
+        "dimension": {
+          "char": "d",
+          "name": "dimension",
+          "summary": "Dimension to drill into when using --format detail. One of: actions, grounding, routing, errors. Required when --format is detail.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "actions",
+            "grounding",
+            "routing",
+            "errors"
+          ],
+          "type": "option"
+        },
+        "turn": {
+          "char": "t",
+          "name": "turn",
+          "summary": "Scope output to this conversation turn number.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": false,
+      "hiddenAliases": [],
+      "id": "agent:trace:read",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Read and analyze trace files from an agent preview session.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "trace",
+        "read.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:trace:read",
+        "trace:agent:read",
+        "trace:read:agent",
+        "agent:read:trace",
+        "read:agent:trace",
+        "read:trace:agent"
+      ]
+    },
     "agent:validate:authoring-bundle": {
       "aliases": [],
       "args": {},
@@ -2432,5 +2708,5 @@
       ]
     }
   },
-  "version": "1.36.1"
+  "version": "1.38.0"
 }