@salesforce/plugin-agent 1.43.0 → 1.44.4

package/oclif.manifest.json

@@ -421,7 +421,7 @@
     "agent:adl:create": {
       "aliases": [],
       "args": {},
-      "description": "Creates a new data library in the target org. The --source-type flag determines the type of library: SFDRIVE (file upload), KNOWLEDGE (Salesforce Knowledge articles), or RETRIEVER (existing active Custom Retriever).",
+      "description": "Creates a new data library in the target org. The --source-type flag determines the type of library: SFDRIVE (file upload), KNOWLEDGE (Salesforce Knowledge articles), or RETRIEVER (existing active Custom Retriever).\n\nFor SFDRIVE libraries, creation provisions the full Data Cloud pipeline (DLO → DMO → SearchIndex → Retriever). Upload files with `sf agent adl upload` after creation.",
       "examples": [
         "Create an SFDRIVE library:\n<%= config.bin %> <%= command.id %> --target-org myOrg --name \"My Docs\" --developer-name My_Docs --source-type sfdrive",
         "Create a KNOWLEDGE library with index fields:\n<%= config.bin %> <%= command.id %> --target-org myOrg --name \"KB Library\" --developer-name KB_Library --source-type knowledge --primary-index-field1 Title --primary-index-field2 Summary",
@@ -528,6 +528,35 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "content-fields": {
+          "name": "content-fields",
+          "summary": "Comma-separated list of content fields for KNOWLEDGE libraries (optional, mutable after creation).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "data-category-ids": {
+          "name": "data-category-ids",
+          "summary": "Comma-separated list of data category selection IDs for KNOWLEDGE libraries. Mutually exclusive with --data-category-names (provide one or the other, not both).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "data-category-names": {
+          "name": "data-category-names",
+          "summary": "Comma-separated list of data category names in qualified format (e.g., \"Group_API_Name.Category\"). Mutually exclusive with --data-category-ids (provide one or the other, not both).",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "wait": {
+          "char": "w",
+          "name": "wait",
+          "summary": "Wait N minutes for indexing to complete (KNOWLEDGE libraries). SFDRIVE libraries require upload before indexing; RETRIEVER libraries are ready immediately.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
@@ -536,7 +565,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Create an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -614,7 +642,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Delete an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -692,7 +719,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Get details of an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -774,7 +800,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "List Agentforce Data Libraries in an org.",
       "enableJsonFlag": true,
@@ -799,7 +824,7 @@
     "agent:adl:status": {
       "aliases": [],
       "args": {},
-      "description": "Returns the current indexing status including stage details (DATA_LAKE_OBJECT, SEARCH_INDEX, RETRIEVER) and any errors.",
+      "description": "Returns the current indexing status including stage details (DATA_STREAM, DATA_LAKE_OBJECT, DATA_MODEL_OBJECT, SEARCH_INDEX, RETRIEVER) and any errors.",
       "examples": [
         "Get status of a data library:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --target-org myOrg"
       ],
@@ -844,6 +869,12 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "include-artifacts": {
+          "name": "include-artifacts",
+          "summary": "Resolve DC asset artifacts (DataStream, DLO, DMO, SearchIndex, Retriever) with entity IDs and names on each stage. Slower — requires additional queries.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
@@ -852,7 +883,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Get indexing status of an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -954,6 +984,12 @@
           "allowNo": true,
           "type": "boolean"
         },
+        "data-category-rule": {
+          "name": "data-category-rule",
+          "summary": "Enable or disable data category filtering for KNOWLEDGE libraries. Use --no-data-category-rule to disable.",
+          "allowNo": true,
+          "type": "boolean"
+        },
         "retriever-id": {
           "name": "retriever-id",
           "summary": "Swap the retriever for a RETRIEVER library (must be an active Custom Retriever ID).",
@@ -968,7 +1004,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Update an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -993,7 +1028,7 @@
     "agent:adl:upload": {
       "aliases": [],
       "args": {},
-      "description": "Performs the multi-step upload workflow: checks upload readiness, obtains a pre-signed S3 URL, uploads the file, triggers indexing, and optionally polls until the library is ready (retrieverId is populated).\n\nThis command only works with SFDRIVE libraries. KNOWLEDGE libraries index automatically after creation, and RETRIEVER libraries require no file upload.",
+      "description": "Performs the multi-step upload workflow: checks upload readiness, obtains a pre-signed S3 URL, uploads the file, triggers indexing, and optionally polls until the library is ready (retrieverId is populated).\n\nUpload triggers the full Data Cloud provisioning pipeline, creating all downstream assets (DLO, DMO, SearchIndex, Retriever). Use `sf agent adl status` to monitor progress. For adding files to an already-provisioned library, use `sf agent adl file add` instead.\n\nThis command only works with SFDRIVE libraries. KNOWLEDGE libraries index automatically after creation, and RETRIEVER libraries require no file upload.",
       "examples": [
         "Upload a file and wait for indexing to complete:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg --wait 10",
         "Upload a file without waiting:\n<%= config.bin %> <%= command.id %> --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg"
@@ -1064,7 +1099,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Upload a file to an SFDRIVE Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -1707,16 +1741,16 @@
         "update:mcp: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, respectively. To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory. Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.\n\nUse the --all flag to end all active preview sessions at once. You can combine --all with --api-name or --authoring-bundle to end only sessions for a specific agent, or use --all on its own to end every session across all agents in the project.",
       "examples": [
-        "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",
+        "End all active preview sessions for a specific agent without prompting:\n<%= config.bin %> <%= command.id %> --all --authoring-bundle My_Local_Agent --target-org <target_org> --no-prompt",
+        "End all active preview sessions across every agent in the local session cache for an org:\n<%= config.bin %> <%= command.id %> --all --target-org <target_org>"
       ],
       "flags": {
         "json": {
@@ -1751,164 +1785,129 @@
           "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"
+        "session-id": {
+          "exclusive": [
+            "all"
           ],
-          "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.",
+          "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,
-          "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"
+        "api-name": {
+          "char": "n",
+          "exclusive": [
+            "authoring-bundle"
           ],
-          "type": "option"
-        },
-        "spec": {
-          "name": "spec",
-          "summary": "Agent spec file, in YAML format, to use as input to the command.",
+          "name": "api-name",
+          "summary": "API name of the activated published agent you want to preview.",
           "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",
+        "authoring-bundle": {
+          "exclusive": [
+            "api-name"
+          ],
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "full-interview": {
-          "name": "full-interview",
-          "summary": "Prompt for both required and optional flags.",
+        "all": {
+          "exclusive": [
+            "session-id"
+          ],
+          "name": "all",
+          "summary": "End all active preview sessions. Combine with --api-name or --authoring-bundle to limit to a specific agent, or use with only --target-org to end sessions for all agents found in the local session cache. Requires --target-org.",
           "allowNo": false,
           "type": "boolean"
         },
-        "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.",
+        "no-prompt": {
+          "char": "p",
+          "name": "no-prompt",
+          "summary": "Don't prompt for confirmation before ending sessions. Has an effect only when used with --all.",
           "allowNo": false,
           "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent: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": "ExactlyOneRequired (2)",
+            "description": "Neither --api-name nor --authoring-bundle was provided (required when --all is not set)."
+          },
+          {
+            "name": "NotFound (2)",
+            "description": "Agent not found, or no preview session exists for this agent."
+          },
+          {
+            "name": "PreviewEndFailed (4)",
+            "description": "Failed to end the preview session."
+          },
+          {
+            "name": "PreviewEndPartialFailure (68)",
+            "description": "With --all, one or more sessions failed to end while others succeeded."
+          },
+          {
+            "name": "SessionAmbiguous (5)",
+            "description": "Multiple preview sessions found; specify --session-id to choose one."
+          }
+        ]
+      },
       "isESM": true,
       "relativePath": [
         "lib",
         "commands",
         "agent",
-        "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": {
@@ -1936,13 +1935,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",
@@ -1950,77 +1942,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,
+      "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",
-        "generate",
-        "authoring-bundle.js"
+        "preview",
+        "send.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:generate:authoring-bundle",
-        "generate:agent:authoring-bundle",
-        "generate:authoring-bundle:agent",
-        "agent:authoring-bundle:generate",
-        "authoring-bundle:agent:generate",
-        "authoring-bundle:generate:agent"
+        "agent: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": {
@@ -2037,90 +2055,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` (legacy testing-center) or `AiTestingDefinition` (Agentforce Studio / NGT), selected via --test-runner.\n\nIf you have an existing AiEvaluationDefinition or AiTestingDefinition metadata XML file in your DX project, you can generate its equivalent YAML test spec file with the --from-definition flag. The runner is inferred from the file extension; pass --test-runner to override.",
+      "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 Agentforce Studio (NGT) test spec YAML file interactively:\n<%= config.bin %> <%= command.id %> --test-runner agentforce-studio",
-        "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",
-        "Generate an Agentforce Studio (NGT) test spec YAML file from an existing AiTestingDefinition metadata XML file:\n<%= config.bin %> <%= command.id %> --from-definition force-app/main/default/aiTestingDefinitions/Returns_Checkout_Tests.aiTestingDefinition-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",
@@ -2129,169 +2119,85 @@
           "multiple": false,
           "type": "option"
         },
-        "from-definition": {
-          "char": "d",
-          "name": "from-definition",
-          "summary": "Filepath to an AiEvaluationDefinition or AiTestingDefinition metadata XML file in your DX project that you want to convert to a test spec YAML file.",
-          "hasDynamicHelp": false,
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
           "multiple": false,
           "type": "option"
         },
-        "force-overwrite": {
-          "name": "force-overwrite",
-          "summary": "Don't prompt for confirmation when overwriting an existing test spec YAML file.",
-          "allowNo": false,
-          "type": "boolean"
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "output-file": {
-          "char": "f",
-          "name": "output-file",
-          "summary": "Name of the generated test spec YAML file. Default value is \"specs/<AGENT_API_NAME>-testSpec.yaml\" (legacy) or \"specs/<AGENT_API_NAME>-ngtTestSpec.yaml\" (Agentforce Studio).",
+        "api-name": {
+          "char": "n",
+          "name": "api-name",
+          "summary": "API name of the activated published agent you want to preview.",
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
         },
-        "test-runner": {
-          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
-          "name": "test-runner",
-          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
+        "authoring-bundle": {
+          "name": "authoring-bundle",
+          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
           "hasDynamicHelp": false,
           "multiple": false,
-          "options": [
-            "agentforce-studio",
-            "testing-center"
+          "type": "option"
+        },
+        "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"
           ],
-          "type": "option"
-        }
-      },
-      "hasDynamicHelp": false,
-      "hiddenAliases": [],
-      "id": "agent:generate:test-spec",
-      "pluginAlias": "@salesforce/plugin-agent",
-      "pluginName": "@salesforce/plugin-agent",
-      "pluginType": "core",
-      "strict": true,
-      "summary": "Generate an agent test spec, which is a YAML file that lists the test cases for testing a specific agent.",
-      "enableJsonFlag": false,
-      "isESM": true,
-      "relativePath": [
-        "lib",
-        "commands",
-        "agent",
-        "generate",
-        "test-spec.js"
-      ],
-      "aliasPermutations": [],
-      "permutations": [
-        "agent:generate:test-spec",
-        "generate:agent:test-spec",
-        "generate:test-spec:agent",
-        "agent:test-spec:generate",
-        "test-spec:agent:generate",
-        "test-spec:generate:agent"
-      ]
-    },
-    "agent:preview:end": {
-      "aliases": [],
-      "args": {},
-      "description": "You must have previously started a programmatic agent preview session with the \"agent preview start\" command to then use this command to end it. This command also displays the local directory where the session trace files are stored.\n\nThe original \"agent preview start\" command outputs a session ID which you then use with the --session-id flag of this command to end the session. You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respectively. To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the \"aiAuthoringBundles\" metadata directory. Similarly, the published agent's API name is the same as its directory name under the \"Bots\" metadata directory.\n\nUse the --all flag to end all active preview sessions at once. You can combine --all with --api-name or --authoring-bundle to end only sessions for a specific agent, or use --all on its own to end every session across all agents in the project.",
-      "examples": [
-        "End a preview session of a published agent by specifying its session ID and API name; use the default org:\n<%= config.bin %> <%= command.id %> --session-id <SESSION_ID> --api-name My_Published_Agent",
-        "Similar to previous example, but don't specify a session ID; you get an error if the published agent has more than one active session. Use the org with alias \"my-dev-org\":\n<%= config.bin %> <%= command.id %> --api-name My_Published_Agent --target-org my-dev-org",
-        "End a preview session of an agent using its authoring bundle API name; you get an error if the agent has more than one active session.\n<%= config.bin %> <%= command.id %> --authoring-bundle My_Local_Agent",
-        "End all active preview sessions for a specific agent without prompting:\n<%= config.bin %> <%= command.id %> --all --authoring-bundle My_Local_Agent --target-org <target_org> --no-prompt",
-        "End all active preview sessions across every agent in the local session cache for an org:\n<%= config.bin %> <%= command.id %> --all --target-org <target_org>"
-      ],
-      "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,
+          "name": "simulate-actions",
+          "summary": "Use AI to simulate action execution instead of calling real actions. Required with --authoring-bundle.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "context-variables": {
+          "description": "Sets variables on the agent preview session, mirroring what the in-org Agentforce Builder UI does when you override variables before sending a message. Specify this flag multiple times or use comma-separated values. Two namespaces are supported, distinguished by the name shape. Names pass through to the runtime verbatim — the CLI doesn't transform them.\n\nLinked context variables use the \"$Context.\" prefix. These map to externally-provided fields that the runtime resolves (declared in the bundle's globalConfiguration.contextVariables) and are read by live actions and topic-routing expressions via $Context.Name. Example: $Context.MyLinkedVar=some-value.\n\nState variables use the bare developerName, no prefix. These seed mutable agent state declared in agentVersion.stateVariables. Example: MyStateVar=some-value.\n\nBoth namespaces can be mixed in one value. Example: --context-variables '$Context.MyLinkedVar=foo,MyStateVar=bar'.\n\nTips: (1) Quote the whole value in single quotes so $Context isn't shell-expanded. (2) Names are sent verbatim — a bare name is treated as a state variable, not a linked context variable, so live actions that bind via $Context.Name will see null. (3) Type defaults to Text.",
+          "name": "context-variables",
+          "summary": "Session variables for the agent preview session, in the form Name=Value.",
+          "delimiter": ",",
+          "hasDynamicHelp": false,
+          "multiple": true,
           "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"
-        },
-        "session-id": {
-          "exclusive": [
-            "all"
-          ],
-          "name": "session-id",
-          "required": false,
-          "summary": "Session ID outputted by \"agent preview start\". Not required when the agent has exactly one active session. Run \"agent preview sessions\" to see the list of all sessions.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "api-name": {
-          "char": "n",
-          "exclusive": [
+        "agent-json": {
+          "dependsOn": [
             "authoring-bundle"
           ],
-          "name": "api-name",
-          "summary": "API name of the activated published agent you want to preview.",
-          "hasDynamicHelp": false,
-          "multiple": false,
-          "type": "option"
-        },
-        "authoring-bundle": {
-          "exclusive": [
-            "api-name"
-          ],
-          "name": "authoring-bundle",
-          "summary": "API name of the authoring bundle metadata component that contains the agent's Agent Script file.",
+          "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"
-        },
-        "all": {
-          "exclusive": [
-            "session-id"
-          ],
-          "name": "all",
-          "summary": "End all active preview sessions. Combine with --api-name or --authoring-bundle to limit to a specific agent, or use with only --target-org to end sessions for all agents found in the local session cache. Requires --target-org.",
-          "allowNo": false,
-          "type": "boolean"
-        },
-        "no-prompt": {
-          "char": "p",
-          "name": "no-prompt",
-          "summary": "Don't prompt for confirmation before ending sessions. Has an effect only when used with --all.",
-          "allowNo": false,
-          "type": "boolean"
         }
       },
       "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:end",
+      "id": "agent:preview:start",
       "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": "Start a programmatic agent preview session.",
       "enableJsonFlag": true,
       "requiresProject": true,
       "envVariablesSection": {
@@ -2308,27 +2214,23 @@
         "body": [
           {
             "name": "Succeeded (0)",
-            "description": "Preview session ended successfully and traces saved."
+            "description": "Preview session started successfully."
           },
           {
-            "name": "ExactlyOneRequired (2)",
-            "description": "Neither --api-name nor --authoring-bundle was provided (required when --all is not set)."
+            "name": "Failed (1)",
+            "description": "Agent Script compilation failed (syntax errors in the script)."
           },
           {
             "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."
+            "description": "Agent not found, or compilation API returned HTTP 404 (endpoint may not be available in your org or region)."
           },
           {
-            "name": "PreviewEndPartialFailure (68)",
-            "description": "With --all, one or more sessions failed to end while others succeeded."
+            "name": "ServerError (3)",
+            "description": "Compilation API returned HTTP 500 (server error during compilation)."
           },
           {
-            "name": "SessionAmbiguous (5)",
-            "description": "Multiple preview sessions found; specify --session-id to choose one."
+            "name": "PreviewStartFailed (4)",
+            "description": "Preview session failed to start due to API or network errors."
           }
         ]
       },
@@ -2338,26 +2240,28 @@
         "commands",
         "agent",
         "preview",
-        "end.js"
+        "start.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:end",
-        "preview:agent:end",
-        "preview:end:agent",
-        "agent:end:preview",
-        "end:agent:preview",
-        "end:preview:agent"
+        "agent:preview:start",
+        "preview:agent:start",
+        "preview:start:agent",
+        "agent:start:preview",
+        "start:agent:preview",
+        "start:preview:agent"
       ]
     },
-    "agent:preview:send": {
+    "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 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": "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": [
-        "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 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": {
@@ -2392,103 +2296,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 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"
         },
-        "utterance": {
-          "char": "u",
-          "name": "utterance",
-          "required": true,
-          "summary": "Utterance to send to the agent, enclosed in double quotes.",
+        "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:send",
+      "id": "agent:generate:agent-spec",
       "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 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": "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",
+        "agent-spec.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:send",
-        "preview:agent:send",
-        "preview:send:agent",
-        "agent:send:preview",
-        "send:agent:preview",
-        "send: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:sessions": {
+    "agent:generate:authoring-bundle": {
       "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": "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": [
-        "List all cached agent preview sessions:\n<%= config.bin %> <%= command.id %>"
+        "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": {
@@ -2505,53 +2470,102 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "target-org": {
+          "char": "o",
+          "name": "target-org",
+          "noCacheDefault": true,
+          "required": true,
+          "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
+          "hasDynamicHelp": true,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-name": {
+          "name": "api-name",
+          "summary": "API name of the new authoring bundle; if not specified, the API name is derived from the authoring bundle name (label); the API name can't exist in the org.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "api-version": {
+          "description": "Override the api version used for api requests made by this command",
+          "name": "api-version",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "spec": {
+          "char": "f",
+          "name": "spec",
+          "summary": "Path to the agent spec YAML file. If you don't specify the flag, the command provides a list that you can choose from. Use the --no-spec flag to skip using an agent spec entirely.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "no-spec": {
+          "name": "no-spec",
+          "summary": "Skip prompting for an agent spec and use the default Agent Script boilerplate in the generated authoring bundle.",
+          "allowNo": false,
+          "type": "boolean"
+        },
+        "output-dir": {
+          "char": "d",
+          "name": "output-dir",
+          "summary": "Directory where the authoring bundle files are generated.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "name": {
+          "char": "n",
+          "name": "name",
+          "summary": "Name (label) of the authoring bundle; if not specified, you're prompted for the name.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "force-overwrite": {
+          "name": "force-overwrite",
+          "summary": "Overwrite the existing authoring bundle if one with the same API name already exists locally.",
+          "allowNo": false,
+          "type": "boolean"
         }
       },
-      "hasDynamicHelp": false,
+      "hasDynamicHelp": true,
       "hiddenAliases": [],
-      "id": "agent:preview:sessions",
+      "id": "agent:generate:authoring-bundle",
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
       "strict": true,
-      "summary": "List all known programmatic agent preview sessions.",
+      "summary": "Generate an authoring bundle from an existing agent spec YAML file.",
       "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",
+        "authoring-bundle.js"
       ],
       "aliasPermutations": [],
       "permutations": [
-        "agent:preview:sessions",
-        "preview:agent:sessions",
-        "preview:sessions:agent",
-        "agent:sessions:preview",
-        "sessions:agent:preview",
-        "sessions: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:start": {
+    "agent:generate:template": {
       "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": "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": [
-        "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 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": {
@@ -2569,137 +2583,157 @@
           "multiple": false,
           "type": "option"
         },
-        "target-org": {
-          "char": "o",
-          "name": "target-org",
+        "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 target org. Not required if the `target-org` configuration variable is already set.",
+          "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"
         },
-        "api-version": {
-          "description": "Override the api version used for api requests made by this command",
-          "name": "api-version",
+        "agent-version": {
+          "name": "agent-version",
+          "required": true,
+          "summary": "Version of the agent (BotVersion).",
           "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.",
+        "agent-file": {
+          "char": "f",
+          "name": "agent-file",
+          "required": true,
+          "summary": "Path to an agent (Bot) metadata file.",
           "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.",
+        "output-dir": {
+          "char": "r",
+          "name": "output-dir",
+          "summary": "Directory where the generated BotTemplate and GenAiPlannerBundle files are saved.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        }
+      },
+      "hasDynamicHelp": true,
+      "hiddenAliases": [],
+      "id": "agent:generate:template",
+      "pluginAlias": "@salesforce/plugin-agent",
+      "pluginName": "@salesforce/plugin-agent",
+      "pluginType": "core",
+      "strict": true,
+      "summary": "Generate an agent template from an existing agent in your DX project so you can then package the template in a second-generation managed package.",
+      "enableJsonFlag": true,
+      "requiresProject": true,
+      "isESM": true,
+      "relativePath": [
+        "lib",
+        "commands",
+        "agent",
+        "generate",
+        "template.js"
+      ],
+      "aliasPermutations": [],
+      "permutations": [
+        "agent:generate:template",
+        "generate:agent:template",
+        "generate:template:agent",
+        "agent:template:generate",
+        "template:agent:generate",
+        "template:generate:agent"
+      ]
+    },
+    "agent:generate:test-spec": {
+      "aliases": [],
+      "args": {},
+      "description": "The first step when using Salesforce CLI to create an agent test in your org is to use this interactive command to generate a local YAML-formatted test spec file. The test spec YAML file contains information about the agent being tested, such as its API name, and then one or more test cases. This command uses the metadata components in your DX project when prompting for information, such as the agent API name; it doesn't look in your org.\n\nTo generate a specific agent test case, this command prompts you for this information; when possible, the command provides a list of options for you to choose from:\n\n- Utterance: Natural language statement, question, or command used to test the agent.\n- Expected topic: API name of the topic you expect the agent to use when responding to the utterance.\n- Expected actions: One or more API names of the expection actions the agent takes.\n- Expected outcome: Natural language description of the outcome you expect.\n- (Optional) Custom evaluation: Test an agent's response for specific strings or numbers.\n- (Optional) Conversation history: Boilerplate for additional context you can add to the test in the form of a conversation history.\n\nYou can manually add contextVariables to test cases in the generated YAML file to inject contextual data (such as CaseId or RoutableId) into agent sessions. This is useful for testing agent behavior with different contextual information.\n\nWhen your test spec is ready, you then run the \"agent test create\" command to actually create the test in your org and synchronize the metadata with your DX project. The metadata type for an agent test is `AiEvaluationDefinition` (legacy testing-center) or `AiTestingDefinition` (Agentforce Studio / NGT), selected via --test-runner.\n\nIf you have an existing AiEvaluationDefinition or AiTestingDefinition metadata XML file in your DX project, you can generate its equivalent YAML test spec file with the --from-definition flag. The runner is inferred from the file extension; pass --test-runner to override.",
+      "examples": [
+        "Generate an agent test spec YAML file interactively:\n<%= config.bin %> <%= command.id %>",
+        "Generate an Agentforce Studio (NGT) test spec YAML file interactively:\n<%= config.bin %> <%= command.id %> --test-runner agentforce-studio",
+        "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",
+        "Generate an Agentforce Studio (NGT) test spec YAML file from an existing AiTestingDefinition metadata XML file:\n<%= config.bin %> <%= command.id %> --from-definition force-app/main/default/aiTestingDefinitions/Returns_Checkout_Tests.aiTestingDefinition-meta.xml"
+      ],
+      "flags": {
+        "flags-dir": {
+          "helpGroup": "GLOBAL",
+          "name": "flags-dir",
+          "summary": "Import flag values from a directory.",
           "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"
+        "from-definition": {
+          "char": "d",
+          "name": "from-definition",
+          "summary": "Filepath to an AiEvaluationDefinition or AiTestingDefinition metadata XML file in your DX project that you want to convert to a test spec YAML file.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
         },
-        "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"
         },
-        "context-variables": {
-          "description": "Sets variables on the agent preview session, mirroring what the in-org Agentforce Builder UI does when you override variables before sending a message. Specify this flag multiple times or use comma-separated values. Two namespaces are supported, distinguished by the name shape. Names pass through to the runtime verbatim — the CLI doesn't transform them.\n\nLinked context variables use the \"$Context.\" prefix. These map to externally-provided fields that the runtime resolves (declared in the bundle's globalConfiguration.contextVariables) and are read by live actions and topic-routing expressions via $Context.Name. Example: $Context.MyLinkedVar=some-value.\n\nState variables use the bare developerName, no prefix. These seed mutable agent state declared in agentVersion.stateVariables. Example: MyStateVar=some-value.\n\nBoth namespaces can be mixed in one value. Example: --context-variables '$Context.MyLinkedVar=foo,MyStateVar=bar'.\n\nTips: (1) Quote the whole value in single quotes so $Context isn't shell-expanded. (2) Names are sent verbatim — a bare name is treated as a state variable, not a linked context variable, so live actions that bind via $Context.Name will see null. (3) Type defaults to Text.",
-          "name": "context-variables",
-          "summary": "Session variables for the agent preview session, in the form Name=Value.",
-          "delimiter": ",",
+        "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\" (legacy) or \"specs/<AGENT_API_NAME>-ngtTestSpec.yaml\" (Agentforce Studio).",
           "hasDynamicHelp": false,
-          "multiple": true,
+          "multiple": false,
           "type": "option"
         },
-        "agent-json": {
-          "dependsOn": [
-            "authoring-bundle"
-          ],
-          "hidden": true,
-          "name": "agent-json",
-          "summary": "Path to a pre-compiled AgentJSON file to use instead of compiling the Agent Script file. Intended for internal use and testing.",
+        "test-runner": {
+          "description": "By default, the command automatically detects which test runner to use based on the test definition metadata type in your org. Use this flag to explicitly specify the runner type. 'agentforce-studio' uses AiTestingDefinition metadata. 'testing-center' uses AiEvaluationDefinition metadata.",
+          "name": "test-runner",
+          "summary": "Explicitly specify which test runner to use (agentforce-studio or testing-center).",
           "hasDynamicHelp": false,
           "multiple": false,
+          "options": [
+            "agentforce-studio",
+            "testing-center"
+          ],
           "type": "option"
         }
       },
-      "hasDynamicHelp": true,
+      "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": {
@@ -4080,7 +4114,7 @@
     "agent:adl:file:add": {
       "aliases": [],
       "args": {},
-      "description": "Adds one or more files to an existing SFDRIVE data library and triggers SearchIndex re-hydration. This is the day-2 operation for adding files to an already-provisioned library.\n\nConstraints: at least 1 file required, no duplicate file names in a batch, maximum 1000 files per library.",
+      "description": "Adds one or more files to an existing SFDRIVE data library and triggers SearchIndex re-hydration. This is the day-2 operation for adding files to an already-provisioned library.\n\nAdds files to an existing READY library. Unlike `sf agent adl upload`, this does NOT create new downstream Data Cloud assets — it appends files to the existing SearchIndex and triggers re-indexing.\n\nConstraints: at least 1 file required, no duplicate file names in a batch, maximum 1000 files per library.",
       "examples": [
         "Add a file to an existing library:\n<%= config.bin %> <%= command.id %> -i 1JDSG000007IbWX4A0 --path ./docs/new-guide.pdf --target-org myOrg",
         "Add multiple files:\n<%= config.bin %> <%= command.id %> -i 1JDSG000007IbWX4A0 --path ./docs/guide.pdf --path ./docs/faq.txt --target-org myOrg"
@@ -4143,7 +4177,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Add files to an existing Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -4248,7 +4281,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "Delete a file from an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -4338,6 +4370,37 @@
           "hasDynamicHelp": false,
           "multiple": false,
           "type": "option"
+        },
+        "page-size": {
+          "name": "page-size",
+          "summary": "Number of files to return per page (1-200, default 50).",
+          "default": 50,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "offset": {
+          "name": "offset",
+          "summary": "Number of files to skip before returning results (for pagination).",
+          "default": 0,
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "type": "option"
+        },
+        "status": {
+          "name": "status",
+          "summary": "Filter files by indexing status.",
+          "hasDynamicHelp": false,
+          "multiple": false,
+          "options": [
+            "uploaded",
+            "indexing",
+            "indexed",
+            "index_failed",
+            "deleting",
+            "delete_failed"
+          ],
+          "type": "option"
         }
       },
       "hasDynamicHelp": true,
@@ -4346,7 +4409,6 @@
       "pluginAlias": "@salesforce/plugin-agent",
       "pluginName": "@salesforce/plugin-agent",
       "pluginType": "core",
-      "state": "preview",
       "strict": true,
       "summary": "List files in an Agentforce Data Library.",
       "enableJsonFlag": true,
@@ -4605,5 +4667,5 @@
       ]
     }
   },
-  "version": "1.43.0"
+  "version": "1.44.4"
 }