@salesforce/plugin-agent 1.42.1 → 1.44.4

package/README.md

@@ -76,6 +76,14 @@ sf plugins
 - [`sf agent generate authoring-bundle`](#sf-agent-generate-authoring-bundle)
 - [`sf agent generate template`](#sf-agent-generate-template)
 - [`sf agent generate test-spec`](#sf-agent-generate-test-spec)
+- [`sf agent mcp asset list`](#sf-agent-mcp-asset-list)
+- [`sf agent mcp asset replace`](#sf-agent-mcp-asset-replace)
+- [`sf agent mcp create`](#sf-agent-mcp-create)
+- [`sf agent mcp delete`](#sf-agent-mcp-delete)
+- [`sf agent mcp fetch`](#sf-agent-mcp-fetch)
+- [`sf agent mcp get`](#sf-agent-mcp-get)
+- [`sf agent mcp list`](#sf-agent-mcp-list)
+- [`sf agent mcp update`](#sf-agent-mcp-update)
 - [`sf agent preview`](#sf-agent-preview)
 - [`sf agent preview end`](#sf-agent-preview-end)
 - [`sf agent preview send`](#sf-agent-preview-send)
@@ -140,7 +148,7 @@ EXAMPLES
     $ sf agent activate --api-name Resort_Manager --version 2 --target-org my-org
 ```
 
-_See code: [src/commands/agent/activate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/activate.ts)_
+_See code: [src/commands/agent/activate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/activate.ts)_
 
 ## `sf agent adl create`
 
@@ -150,13 +158,24 @@ Create an Agentforce Data Library.
 USAGE
   $ sf agent adl create -o <value> -n <value> --developer-name <value> --source-type sfdrive|knowledge|retriever
     [--json] [--flags-dir <value>] [--api-version <value>] [--description <value>] [--index-mode basic|enhanced]
-    [--retriever-id <value>] [--primary-index-field1 <value>] [--primary-index-field2 <value>]
+    [--retriever-id <value>] [--primary-index-field1 <value>] [--primary-index-field2 <value>] [--content-fields
+    <value>] [--data-category-ids <value>] [--data-category-names <value>] [-w <value>]
 
 FLAGS
   -n, --name=<value>                  (required) Display name for the data library (max 80 characters).
   -o, --target-org=<value>            (required) Username or alias of the target org. Not required if the `target-org`
                                       configuration variable is already set.
+  -w, --wait=<value>                  Wait N minutes for indexing to complete (KNOWLEDGE libraries). SFDRIVE libraries
+                                      require upload before indexing; RETRIEVER libraries are ready immediately.
       --api-version=<value>           Override the api version used for api requests made by this command
+      --content-fields=<value>        Comma-separated list of content fields for KNOWLEDGE libraries (optional, mutable
+                                      after creation).
+      --data-category-ids=<value>     Comma-separated list of data category selection IDs for KNOWLEDGE libraries.
+                                      Mutually exclusive with --data-category-names (provide one or the other, not
+                                      both).
+      --data-category-names=<value>   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).
       --description=<value>           Description of the data library (max 255 characters).
       --developer-name=<value>        (required) API name for the data library (max 80 characters, alphanumeric and
                                       underscores only, must start with a letter).
@@ -182,6 +201,9 @@ 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).
 
+  For 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:
 
@@ -198,7 +220,7 @@ EXAMPLES
       --source-type retriever --retriever-id 0ppXX0000000001
 ```
 
-_See code: [src/commands/agent/adl/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/create.ts)_
+_See code: [src/commands/agent/adl/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/create.ts)_
 
 ## `sf agent adl delete`
 
@@ -229,7 +251,7 @@ EXAMPLES
     $ sf agent adl delete --library-id 1JDSG000007IbWX4A0 --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/delete.ts)_
+_See code: [src/commands/agent/adl/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/delete.ts)_
 
 ## `sf agent adl file add`
 
@@ -256,6 +278,9 @@ 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.
 
+  Adds 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.
+
   Constraints: at least 1 file required, no duplicate file names in a batch, maximum 1000 files per library.
 
 EXAMPLES
@@ -268,7 +293,7 @@ EXAMPLES
     $ sf agent adl file add -i 1JDSG000007IbWX4A0 --path ./docs/guide.pdf --path ./docs/faq.txt --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/file/add.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/file/add.ts)_
+_See code: [src/commands/agent/adl/file/add.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/file/add.ts)_
 
 ## `sf agent adl file delete`
 
@@ -301,7 +326,7 @@ EXAMPLES
     $ sf agent adl file delete --library-id 1JDSG000007IbWX4A0 --file-id a1B2C3D4E5F6G7H8I9 --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/file/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/file/delete.ts)_
+_See code: [src/commands/agent/adl/file/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/file/delete.ts)_
 
 ## `sf agent adl file list`
 
@@ -309,13 +334,18 @@ List files in an Agentforce Data Library.
 
 ```
 USAGE
-  $ sf agent adl file list -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+  $ sf agent adl file list -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--page-size
+    <value>] [--offset <value>] [--status uploaded|indexing|indexed|index_failed|deleting|delete_failed]
 
 FLAGS
   -i, --library-id=<value>   (required) Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).
   -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
                              configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
+      --offset=<value>       Number of files to skip before returning results (for pagination).
+      --page-size=<value>    [default: 50] Number of files to return per page (1-200, default 50).
+      --status=<option>      Filter files by indexing status.
+                             <options: uploaded|indexing|indexed|index_failed|deleting|delete_failed>
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -336,7 +366,7 @@ EXAMPLES
     $ sf agent adl file list --library-id 1JDSG000007IbWX4A0 --target-org myOrg --json
 ```
 
-_See code: [src/commands/agent/adl/file/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/file/list.ts)_
+_See code: [src/commands/agent/adl/file/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/file/list.ts)_
 
 ## `sf agent adl get`
 
@@ -367,7 +397,7 @@ EXAMPLES
     $ sf agent adl get --library-id 1JDSG000007IbWX4A0 --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/get.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/get.ts)_
+_See code: [src/commands/agent/adl/get.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/get.ts)_
 
 ## `sf agent adl list`
 
@@ -404,7 +434,7 @@ EXAMPLES
     $ sf agent adl list --target-org myOrg --json
 ```
 
-_See code: [src/commands/agent/adl/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/list.ts)_
+_See code: [src/commands/agent/adl/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/list.ts)_
 
 ## `sf agent adl status`
 
@@ -413,12 +443,15 @@ Get indexing status of an Agentforce Data Library.
 ```
 USAGE
   $ sf agent adl status -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+    [--include-artifacts]
 
 FLAGS
   -i, --library-id=<value>   (required) Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).
   -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
                              configuration variable is already set.
       --api-version=<value>  Override the api version used for api requests made by this command
+      --include-artifacts    Resolve DC asset artifacts (DataStream, DLO, DMO, SearchIndex, Retriever) with entity IDs
+                             and names on each stage. Slower — requires additional queries.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -427,8 +460,8 @@ GLOBAL FLAGS
 DESCRIPTION
   Get indexing status of an Agentforce Data Library.
 
-  Returns the current indexing status including stage details (DATA_LAKE_OBJECT, SEARCH_INDEX, RETRIEVER) and any
-  errors.
+  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:
@@ -436,7 +469,7 @@ EXAMPLES
     $ sf agent adl status --library-id 1JDSG000007IbWX4A0 --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/status.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/status.ts)_
+_See code: [src/commands/agent/adl/status.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/status.ts)_
 
 ## `sf agent adl update`
 
@@ -445,7 +478,8 @@ Update an Agentforce Data Library.
 ```
 USAGE
   $ sf agent adl update -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>]
-    [--description <value>] [--content-fields <value>] [--restrict-to-public-articles] [--retriever-id <value>]
+    [--description <value>] [--content-fields <value>] [--restrict-to-public-articles] [--data-category-rule]
+    [--retriever-id <value>]
 
 FLAGS
   -i, --library-id=<value>                (required) Agentforce Data Library ID (18-char Salesforce ID with prefix 1JD).
@@ -455,6 +489,8 @@ FLAGS
       --api-version=<value>               Override the api version used for api requests made by this command
       --content-fields=<value>            Comma-separated list of content fields for KNOWLEDGE libraries (triggers
                                           re-indexing).
+      --[no-]data-category-rule           Enable or disable data category filtering for KNOWLEDGE libraries. Use
+                                          --no-data-category-rule to disable.
       --description=<value>               New description for the data library (max 255 characters).
       --[no-]restrict-to-public-articles  Restrict to public Knowledge articles only (KNOWLEDGE libraries, triggers
                                           re-indexing).
@@ -488,7 +524,7 @@ EXAMPLES
     $ sf agent adl update --library-id 1JDSG000007IbWX4A0 --restrict-to-public-articles --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/update.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/update.ts)_
+_See code: [src/commands/agent/adl/update.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/update.ts)_
 
 ## `sf agent adl upload`
 
@@ -518,6 +554,10 @@ 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).
 
+  Upload 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.
+
   This command only works with SFDRIVE libraries. KNOWLEDGE libraries index automatically after creation, and RETRIEVER
   libraries require no file upload.
 
@@ -531,7 +571,7 @@ EXAMPLES
     $ sf agent adl upload --library-id 1JDSG000007IbWX4A0 --file ./docs/guide.pdf --target-org myOrg
 ```
 
-_See code: [src/commands/agent/adl/upload.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/adl/upload.ts)_
+_See code: [src/commands/agent/adl/upload.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/adl/upload.ts)_
 
 ## `sf agent create`
 
@@ -598,7 +638,7 @@ EXAMPLES
     $ sf agent create --name "Resort Manager" --spec specs/resortManagerAgent.yaml --preview
 ```
 
-_See code: [src/commands/agent/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/create.ts)_
+_See code: [src/commands/agent/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/create.ts)_
 
 ## `sf agent deactivate`
 
@@ -639,7 +679,7 @@ EXAMPLES
     $ sf agent deactivate --api-name Resort_Manager --target-org my-org
 ```
 
-_See code: [src/commands/agent/deactivate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/deactivate.ts)_
+_See code: [src/commands/agent/deactivate.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/deactivate.ts)_
 
 ## `sf agent generate agent-spec`
 
@@ -746,7 +786,7 @@ EXAMPLES
     $ sf agent generate agent-spec --tone formal --agent-user resortmanager@myorg.com
 ```
 
-_See code: [src/commands/agent/generate/agent-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/generate/agent-spec.ts)_
+_See code: [src/commands/agent/generate/agent-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/generate/agent-spec.ts)_
 
 ## `sf agent generate authoring-bundle`
 
@@ -823,7 +863,7 @@ EXAMPLES
       other-package-dir/main/default --target-org my-dev-org
 ```
 
-_See code: [src/commands/agent/generate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/generate/authoring-bundle.ts)_
+_See code: [src/commands/agent/generate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/generate/authoring-bundle.ts)_
 
 ## `sf agent generate template`
 
@@ -885,7 +925,7 @@ EXAMPLES
       my-package --source-org my-scratch-org
 ```
 
-_See code: [src/commands/agent/generate/template.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/generate/template.ts)_
+_See code: [src/commands/agent/generate/template.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/generate/template.ts)_
 
 ## `sf agent generate test-spec`
 
@@ -893,14 +933,18 @@ Generate an agent test spec, which is a YAML file that lists the test cases for
 
 ```
 USAGE
-  $ sf agent generate test-spec [--flags-dir <value>] [-d <value>] [--force-overwrite] [-f <value>]
+  $ sf agent generate test-spec [--flags-dir <value>] [-d <value>] [--force-overwrite] [-f <value>] [--test-runner
+    agentforce-studio|testing-center]
 
 FLAGS
-  -d, --from-definition=<value>  Filepath to the AIEvaluationDefinition metadata XML file in your DX project that you
-                                 want to convert to a test spec YAML file.
+  -d, --from-definition=<value>  Filepath to an AiEvaluationDefinition or AiTestingDefinition metadata XML file in your
+                                 DX project that you want to convert to a test spec YAML file.
   -f, --output-file=<value>      Name of the generated test spec YAML file. Default value is
-                                 "specs/<AGENT_API_NAME>-testSpec.yaml".
+                                 "specs/<AGENT_API_NAME>-testSpec.yaml" (legacy) or
+                                 "specs/<AGENT_API_NAME>-ngtTestSpec.yaml" (Agentforce Studio).
       --force-overwrite          Don't prompt for confirmation when overwriting an existing test spec YAML file.
+      --test-runner=<option>     Explicitly specify which test runner to use (agentforce-studio or testing-center).
+                                 <options: agentforce-studio|testing-center>
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -929,16 +973,22 @@ DESCRIPTION
   information.
 
   When 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.
+  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.
 
-  If you have an existing AiEvaluationDefinition metadata XML file in your DX project, you can generate its equivalent
-  YAML test spec file with the --from-definition flag.
+  If 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:
 
     $ sf agent generate test-spec
 
+  Generate an Agentforce Studio (NGT) test spec YAML file interactively:
+
+    $ sf agent generate test-spec --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:
 
@@ -947,10 +997,361 @@ EXAMPLES
   Generate an agent test spec YAML file from an existing AiEvaluationDefinition metadata XML file in your DX project:
 
     $ sf agent generate test-spec --from-definition \
-      force-app//main/default/aiEvaluationDefinitions/Resort_Manager_Tests.aiEvaluationDefinition-meta.xml
+      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:
+
+    $ sf agent generate test-spec --from-definition \
+      force-app/main/default/aiTestingDefinitions/Returns_Checkout_Tests.aiTestingDefinition-meta.xml
+
+FLAG DESCRIPTIONS
+  --test-runner=agentforce-studio|testing-center
+
+    Explicitly specify which test runner to use (agentforce-studio or testing-center).
+
+    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.
+```
+
+_See code: [src/commands/agent/generate/test-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/generate/test-spec.ts)_
+
+## `sf agent mcp asset list`
+
+List the assets (tools, prompts, and resources) for an MCP server in the catalog.
+
+```
+USAGE
+  $ sf agent mcp asset list -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+
+FLAGS
+  -i, --mcp-server-id=<value>  (required) The ID of the MCP server whose assets you want to list.
+  -o, --target-org=<value>     (required) Username or alias of the target org. Not required if the `target-org`
+                               configuration variable is already set.
+      --api-version=<value>    Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  List the assets (tools, prompts, and resources) for an MCP server in the catalog.
+
+  Returns the assets discovered for the specified MCP server, including each asset's kind (MCP_TOOL, MCP_PROMPT, or
+  MCP_RESOURCE), whether it is active, and whether it is available as an agent action.
+
+EXAMPLES
+  List the assets for an MCP server in the default target org:
+
+    $ sf agent mcp asset list --target-org myOrg --mcp-server-id 0XSxx0000000001
+
+  List the assets for an MCP server and output as JSON:
+
+    $ sf agent mcp asset list --target-org myOrg --mcp-server-id 0XSxx0000000001 --json
+```
+
+_See code: [src/commands/agent/mcp/asset/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/asset/list.ts)_
+
+## `sf agent mcp asset replace`
+
+Replace the asset set of an MCP server in the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp asset replace -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--assets <value>
+    | --assets-file <value>]
+
+FLAGS
+  -i, --mcp-server-id=<value>  (required) ID of the MCP server whose assets you want to replace.
+  -o, --target-org=<value>     (required) Username or alias of the target org. Not required if the `target-org`
+                               configuration variable is already set.
+      --api-version=<value>    Override the api version used for api requests made by this command
+      --assets=<value>         The desired asset allowlist as a JSON string (or "-" to read from stdin). Mutually
+                               exclusive with --assets-file.
+      --assets-file=<value>    Path to a JSON file containing the desired asset allowlist. Mutually exclusive with
+                               --assets.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Replace the asset set of an MCP server in the API Catalog.
+
+  Replaces the full set of assets (tools, prompts, resources) for an MCP server with the asset items you supply. Provide
+  the assets either inline with `--assets` (a JSON string, or `-` to read from stdin) or from a file with
+  `--assets-file`. The JSON must be either an array of asset items or an object of the form `{ "assets": [...] }`. Each
+  asset item may include `id`, `name`, `label`, `description`, `active`, and `kind`. This is a full replacement:
+  existing assets not present in the supplied set are removed, so provide the complete desired asset set (read the
+  current set first with `agent mcp asset list` or `agent mcp fetch`).
+
+EXAMPLES
+  Replace the assets inline with a JSON string:
+
+    $ sf agent mcp asset replace --mcp-server-id 0XSxx0000000001 --assets \
+      '{"assets":[{"name":"McpTool__add","active":true}]}' --target-org myOrg
+
+  Replace the assets from a JSON file:
+
+    $ sf agent mcp asset replace --mcp-server-id 0XSxx0000000001 --assets-file ./assets.json --target-org myOrg
+
+  Pipe the assets from stdin:
+  cat assets.json | sf agent mcp asset replace --mcp-server-id 0XSxx0000000001 --assets - --target-org myOrg
+```
+
+_See code: [src/commands/agent/mcp/asset/replace.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/asset/replace.ts)_
+
+## `sf agent mcp create`
+
+Create an MCP server in the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp create -o <value> -n <value> --server-url <value> [--json] [--flags-dir <value>] [--api-version
+    <value>] [--label <value>] [--description <value>] [--auth-type OAUTH|NO_AUTH] [--identity-provider <value>]
+    [--client-id <value>] [--client-secret <value>] [--scope <value>]
+
+FLAGS
+  -n, --name=<value>               (required) Unique name of the MCP server.
+  -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
+                                   configuration variable is already set.
+      --api-version=<value>        Override the api version used for api requests made by this command
+      --auth-type=<option>         [default: NO_AUTH] Authorization type to use when connecting to the MCP server.
+                                   <options: OAUTH|NO_AUTH>
+      --client-id=<value>          OAuth client ID. Required when auth-type is OAUTH.
+      --client-secret=<value>      OAuth client secret. Required when auth-type is OAUTH. Pass "-" to read it from stdin
+                                   (piped) and keep it out of shell history.
+      --description=<value>        Description of the MCP server.
+      --identity-provider=<value>  Identity provider to use for OAuth authorization. Required when auth-type is OAUTH.
+      --label=<value>              Human-readable label for the MCP server.
+      --scope=<value>              OAuth scope to request. Required when auth-type is OAUTH.
+      --server-url=<value>         (required) URL of the external MCP server.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Create an MCP server in the API Catalog.
+
+  Registers an external Model Context Protocol (MCP) server with the API Catalog and discovers its assets (tools,
+  prompts, and resources). Provide the server URL and, when the server requires it, OAuth authorization details. When
+  the authorization type is OAUTH you must supply the identity provider, client ID, client secret, and scope.
+
+EXAMPLES
+  Create an MCP server with no authentication:
+
+    $ sf agent mcp create --name myServer --server-url https://mcp.example.com --target-org myOrg
+
+  Create an MCP server that uses OAuth authentication, piping the client secret from stdin to keep it out of shell history:
+  cat secret.txt | sf agent mcp create --name myServer --server-url https://mcp.example.com --auth-type OAUTH --identity-provider myIdp --client-id abc123 --client-secret - --scope "read write" --target-org myOrg
+```
+
+_See code: [src/commands/agent/mcp/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/create.ts)_
+
+## `sf agent mcp delete`
+
+Delete an MCP server from the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp delete -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--no-prompt]
+
+FLAGS
+  -i, --mcp-server-id=<value>  (required) ID of the MCP server to delete.
+  -o, --target-org=<value>     (required) Username or alias of the target org. Not required if the `target-org`
+                               configuration variable is already set.
+      --api-version=<value>    Override the api version used for api requests made by this command
+      --no-prompt              Skip the confirmation prompt and delete the MCP server immediately.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Delete an MCP server from the API Catalog.
+
+  Permanently removes an MCP (Model Context Protocol) server registration from the API Catalog, identified by its ID. By
+  default you are prompted to confirm the deletion; pass --no-prompt to skip the confirmation (for example in scripts
+  and CI).
+
+EXAMPLES
+  Delete an MCP server, confirming interactively:
+
+    $ sf agent mcp delete --mcp-server-id 0XSxx0000000001 --target-org myOrg
+
+  Delete an MCP server without a confirmation prompt:
+
+    $ sf agent mcp delete --mcp-server-id 0XSxx0000000001 --target-org myOrg --no-prompt
+```
+
+_See code: [src/commands/agent/mcp/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/delete.ts)_
+
+## `sf agent mcp fetch`
+
+Fetch the live assets (tools, prompts, resources) advertised by an MCP server.
+
 ```
+USAGE
+  $ sf agent mcp fetch -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
 
-_See code: [src/commands/agent/generate/test-spec.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/generate/test-spec.ts)_
+FLAGS
+  -i, --mcp-server-id=<value>  (required) ID of the MCP server to fetch assets from.
+  -o, --target-org=<value>     (required) Username or alias of the target org. Not required if the `target-org`
+                               configuration variable is already set.
+      --api-version=<value>    Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Fetch the live assets (tools, prompts, resources) advertised by an MCP server.
+
+  Performs a live fetch against the configured MCP server identified by its ID, returning the assets (MCP tools,
+  prompts, and resources) it currently advertises along with their status and activation state. Use this to refresh the
+  view of what an MCP server exposes before activating its assets as agent actions.
+
+EXAMPLES
+  Fetch the assets advertised by an MCP server in the default target org:
+
+    $ sf agent mcp fetch --target-org myOrg --mcp-server-id 0XSxx0000000001
+
+  Fetch MCP server assets and output as JSON:
+
+    $ sf agent mcp fetch --target-org myOrg --mcp-server-id 0XSxx0000000001 --json
+```
+
+_See code: [src/commands/agent/mcp/fetch.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/fetch.ts)_
+
+## `sf agent mcp get`
+
+Get a single MCP server registered in the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp get -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>]
+
+FLAGS
+  -i, --mcp-server-id=<value>  (required) The identifier of the MCP server to retrieve.
+  -o, --target-org=<value>     (required) Username or alias of the target org. Not required if the `target-org`
+                               configuration variable is already set.
+      --api-version=<value>    Override the api version used for api requests made by this command
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Get a single MCP server registered in the API Catalog.
+
+  Retrieves the details of an MCP (Model Context Protocol) server by its identifier, including its name, label, type,
+  status, and server URL.
+
+EXAMPLES
+  Get an MCP server by id in the default target org:
+
+    $ sf agent mcp get --target-org myOrg --mcp-server-id 0Mx000000000001
+
+  Get an MCP server and output as JSON:
+
+    $ sf agent mcp get --target-org myOrg --mcp-server-id 0Mx000000000001 --json
+```
+
+_See code: [src/commands/agent/mcp/get.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/get.ts)_
+
+## `sf agent mcp list`
+
+List the MCP servers registered in the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp list -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [--label <value>] [--type
+    EXTERNAL] [--status ACTIVE|DISCONNECTED]
+
+FLAGS
+  -o, --target-org=<value>   (required) Username or alias of the target org. Not required if the `target-org`
+                             configuration variable is already set.
+      --api-version=<value>  Override the api version used for api requests made by this command
+      --label=<value>        Filter the MCP servers by label.
+      --status=<option>      Filter the MCP servers by connection status. Only ACTIVE and DISCONNECTED are supported as
+                             filters.
+                             <options: ACTIVE|DISCONNECTED>
+      --type=<option>        Filter the MCP servers by type.
+                             <options: EXTERNAL>
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  List the MCP servers registered in the API Catalog.
+
+  Returns the Model Context Protocol (MCP) servers registered in the API Catalog, optionally filtered by label, type, or
+  status. Use this to discover which MCP servers are available and inspect their server URLs and current status.
+
+EXAMPLES
+  List all MCP servers in the default target org:
+
+    $ sf agent mcp list --target-org myOrg
+
+  List external MCP servers filtered by status and output as JSON:
+
+    $ sf agent mcp list --target-org myOrg --type EXTERNAL --status ACTIVE --json
+```
+
+_See code: [src/commands/agent/mcp/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/list.ts)_
+
+## `sf agent mcp update`
+
+Update an MCP server registered in the API Catalog.
+
+```
+USAGE
+  $ sf agent mcp update -o <value> -i <value> [--json] [--flags-dir <value>] [--api-version <value>] [--label <value>]
+    [--description <value>] [--server-url <value>] [--auth-type OAUTH|NO_AUTH] [--identity-provider <value>]
+    [--client-id <value>] [--client-secret <value>] [--scope <value>]
+
+FLAGS
+  -i, --mcp-server-id=<value>      (required) ID of the MCP server to update.
+  -o, --target-org=<value>         (required) Username or alias of the target org. Not required if the `target-org`
+                                   configuration variable is already set.
+      --api-version=<value>        Override the api version used for api requests made by this command
+      --auth-type=<option>         Authorization type to apply to the MCP server (OAUTH or NO_AUTH).
+                                   <options: OAUTH|NO_AUTH>
+      --client-id=<value>          OAuth client ID (required when --auth-type is OAUTH).
+      --client-secret=<value>      OAuth client secret (required when --auth-type is OAUTH). Pass "-" to read it from
+                                   stdin (piped) and keep it out of shell history.
+      --description=<value>        New description for the MCP server.
+      --identity-provider=<value>  Identity provider name for OAuth authorization (required when --auth-type is OAUTH).
+      --label=<value>              New display label for the MCP server.
+      --scope=<value>              OAuth scope (required when --auth-type is OAUTH).
+      --server-url=<value>         New endpoint URL of the MCP server.
+
+GLOBAL FLAGS
+  --flags-dir=<value>  Import flag values from a directory.
+  --json               Format output as json.
+
+DESCRIPTION
+  Update an MCP server registered in the API Catalog.
+
+  Updates an existing MCP server in the API Catalog. Only the fields you provide are changed; omitted fields are left
+  untouched. You can update the label, description, and server URL, and replace the authorization configuration. When
+  setting `--auth-type OAUTH`, you must also provide `--identity-provider`, `--client-id`, `--client-secret`, and
+  `--scope`. When setting `--auth-type NO_AUTH`, no authorization credentials are required. At least one updatable field
+  must be supplied.
+
+EXAMPLES
+  Update the label and description of an MCP server in the default target org:
+
+    $ sf agent mcp update --mcp-server-id 0XSxx0000000001 --label "Orders MCP" --description "Order tooling" \
+      --target-org myOrg
+
+  Update the server URL and switch the authorization to OAuth, piping the client secret from stdin and outputting as JSON:
+  cat secret.txt | sf agent mcp update --mcp-server-id 0XSxx0000000001 --server-url https://mcp.example.com --auth-type OAUTH --identity-provider MyIdp --client-id abc --client-secret - --scope "read write" --target-org myOrg --json
+```
+
+_See code: [src/commands/agent/mcp/update.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/mcp/update.ts)_
 
 ## `sf agent preview`
 
@@ -959,19 +1360,20 @@ Interact with an agent to preview how it responds to your statements, questions,
 ```
 USAGE
   $ sf agent preview -o <value> [--flags-dir <value>] [--api-version <value>] [-n <value>] [--authoring-bundle
-    <value>] [-d <value>] [-x] [--use-live-actions]
+    <value>] [-d <value>] [-x] [--use-live-actions] [--context-variables <value>...]
 
 FLAGS
-  -d, --output-dir=<value>        Directory where conversation transcripts are saved.
-  -n, --api-name=<value>          API name of the activated published agent you want to interact with.
-  -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
-                                  configuration variable is already set.
-  -x, --apex-debug                Enable Apex debug logging during the agent preview conversation.
-      --api-version=<value>       Override the api version used for api requests made by this command
-      --authoring-bundle=<value>  API name of the authoring bundle metadata component that contains the agent's Agent
-                                  Script file.
-      --use-live-actions          Use real actions in the org; if not specified, preview uses AI to simulate (mock)
-                                  actions.
+  -d, --output-dir=<value>            Directory where conversation transcripts are saved.
+  -n, --api-name=<value>              API name of the activated published agent you want to interact with.
+  -o, --target-org=<value>            (required) Username or alias of the target org. Not required if the `target-org`
+                                      configuration variable is already set.
+  -x, --apex-debug                    Enable Apex debug logging during the agent preview conversation.
+      --api-version=<value>           Override the api version used for api requests made by this command
+      --authoring-bundle=<value>      API name of the authoring bundle metadata component that contains the agent's
+                                      Agent Script file.
+      --context-variables=<value>...  Session variables for the agent preview session, in the form Name=Value.
+      --use-live-actions              Use real actions in the org; if not specified, preview uses AI to simulate (mock)
+                                      actions.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -1021,9 +1423,30 @@ EXAMPLES
   "./transcripts/my-preview" directory, enable the Apex debug logs, and use your default org:
 
     $ sf agent preview --use-live-actions --apex-debug --output-dir transcripts/my-preview
+
+FLAG DESCRIPTIONS
+  --context-variables=<value>...  Session variables for the agent preview session, in the form Name=Value.
+
+    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.
+
+    Linked 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.
+
+    State variables use the bare developerName, no prefix. These seed mutable agent state declared in
+    agentVersion.stateVariables. Example: MyStateVar=some-value.
+
+    Both namespaces can be mixed in one value. Example: --context-variables '$Context.MyLinkedVar=foo,MyStateVar=bar'.
+
+    Tips: (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.
 ```
 
-_See code: [src/commands/agent/preview.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/preview.ts)_
+_See code: [src/commands/agent/preview.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/preview.ts)_
 
 ## `sf agent preview end`
 
@@ -1095,7 +1518,7 @@ EXAMPLES
     $ sf agent preview end --all --target-org <target_org>
 ```
 
-_See code: [src/commands/agent/preview/end.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/preview/end.ts)_
+_See code: [src/commands/agent/preview/end.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/preview/end.ts)_
 
 ## `sf agent preview send`
 
@@ -1153,7 +1576,7 @@ EXAMPLES
     $ sf agent preview send --utterance "what can you help me with?" --authoring-bundle My_Local_Agent
 ```
 
-_See code: [src/commands/agent/preview/send.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/preview/send.ts)_
+_See code: [src/commands/agent/preview/send.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/preview/send.ts)_
 
 ## `sf agent preview sessions`
 
@@ -1186,7 +1609,7 @@ EXAMPLES
     $ sf agent preview sessions
 ```
 
-_See code: [src/commands/agent/preview/sessions.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/preview/sessions.ts)_
+_See code: [src/commands/agent/preview/sessions.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/preview/sessions.ts)_
 
 ## `sf agent preview start`
 
@@ -1195,19 +1618,20 @@ Start a programmatic agent preview session.
 ```
 USAGE
   $ sf agent preview start -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-n <value>]
-    [--authoring-bundle <value>] [--use-live-actions | --simulate-actions]
+    [--authoring-bundle <value>] [--use-live-actions | --simulate-actions] [--context-variables <value>...]
 
 FLAGS
-  -n, --api-name=<value>          API name of the activated published agent you want to preview.
-  -o, --target-org=<value>        (required) Username or alias of the target org. Not required if the `target-org`
-                                  configuration variable is already set.
-      --api-version=<value>       Override the api version used for api requests made by this command
-      --authoring-bundle=<value>  API name of the authoring bundle metadata component that contains the agent's Agent
-                                  Script file.
-      --simulate-actions          Use AI to simulate action execution instead of calling real actions. Required with
-                                  --authoring-bundle.
-      --use-live-actions          Execute real actions in the org (Apex classes, flows, etc.). Required with
-                                  --authoring-bundle.
+  -n, --api-name=<value>              API name of the activated published agent you want to preview.
+  -o, --target-org=<value>            (required) Username or alias of the target org. Not required if the `target-org`
+                                      configuration variable is already set.
+      --api-version=<value>           Override the api version used for api requests made by this command
+      --authoring-bundle=<value>      API name of the authoring bundle metadata component that contains the agent's
+                                      Agent Script file.
+      --context-variables=<value>...  Session variables for the agent preview session, in the form Name=Value.
+      --simulate-actions              Use AI to simulate action execution instead of calling real actions. Required with
+                                      --authoring-bundle.
+      --use-live-actions              Execute real actions in the org (Apex classes, flows, etc.). Required with
+                                      --authoring-bundle.
 
 GLOBAL FLAGS
   --flags-dir=<value>  Import flag values from a directory.
@@ -1249,9 +1673,30 @@ EXAMPLES
   Start a preview session with an activated published agent (always uses live actions):
 
     $ sf agent preview start --api-name My_Published_Agent
+
+FLAG DESCRIPTIONS
+  --context-variables=<value>...  Session variables for the agent preview session, in the form Name=Value.
+
+    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.
+
+    Linked 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.
+
+    State variables use the bare developerName, no prefix. These seed mutable agent state declared in
+    agentVersion.stateVariables. Example: MyStateVar=some-value.
+
+    Both namespaces can be mixed in one value. Example: --context-variables '$Context.MyLinkedVar=foo,MyStateVar=bar'.
+
+    Tips: (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.
 ```
 
-_See code: [src/commands/agent/preview/start.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/preview/start.ts)_
+_See code: [src/commands/agent/preview/start.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/preview/start.ts)_
 
 ## `sf agent publish authoring-bundle`
 
@@ -1311,7 +1756,7 @@ EXAMPLES
     $ sf agent publish authoring-bundle --api-name MyAuthoringbundle --concise
 ```
 
-_See code: [src/commands/agent/publish/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/publish/authoring-bundle.ts)_
+_See code: [src/commands/agent/publish/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/publish/authoring-bundle.ts)_
 
 ## `sf agent test create`
 
@@ -1383,7 +1828,7 @@ FLAG DESCRIPTIONS
     metadata. 'testing-center' uses AiEvaluationDefinition metadata.
 ```
 
-_See code: [src/commands/agent/test/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/create.ts)_
+_See code: [src/commands/agent/test/create.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/create.ts)_
 
 ## `sf agent test list`
 
@@ -1418,7 +1863,7 @@ EXAMPLES
     $ sf agent test list --target-org my-org
 ```
 
-_See code: [src/commands/agent/test/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/list.ts)_
+_See code: [src/commands/agent/test/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/list.ts)_
 
 ## `sf agent test results`
 
@@ -1494,7 +1939,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/results.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/results.ts)_
+_See code: [src/commands/agent/test/results.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/results.ts)_
 
 ## `sf agent test resume`
 
@@ -1578,7 +2023,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/resume.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/resume.ts)_
+_See code: [src/commands/agent/test/resume.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/resume.ts)_
 
 ## `sf agent test run`
 
@@ -1662,7 +2107,7 @@ FLAG DESCRIPTIONS
     expression when using custom evaluations.
 ```
 
-_See code: [src/commands/agent/test/run.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/run.ts)_
+_See code: [src/commands/agent/test/run.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/run.ts)_
 
 ## `sf agent test run-eval`
 
@@ -1738,7 +2183,7 @@ EXAMPLES
   $ echo '{"tests":[...]}' | sf agent test run-eval --spec --target-org my-org
 ```
 
-_See code: [src/commands/agent/test/run-eval.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/test/run-eval.ts)_
+_See code: [src/commands/agent/test/run-eval.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/test/run-eval.ts)_
 
 ## `sf agent trace delete`
 
@@ -1802,7 +2247,7 @@ EXAMPLES
     $ sf agent trace delete --no-prompt
 ```
 
-_See code: [src/commands/agent/trace/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/trace/delete.ts)_
+_See code: [src/commands/agent/trace/delete.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/trace/delete.ts)_
 
 ## `sf agent trace list`
 
@@ -1872,7 +2317,7 @@ FLAG DESCRIPTIONS
     (2026-04-20T14:00:00.000Z). The "Recorded At" values shown in the table output are valid inputs.
 ```
 
-_See code: [src/commands/agent/trace/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/trace/list.ts)_
+_See code: [src/commands/agent/trace/list.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/trace/list.ts)_
 
 ## `sf agent trace read`
 
@@ -1960,7 +2405,7 @@ EXAMPLES
     $ sf agent trace read --session-id <SESSION_ID> --json
 ```
 
-_See code: [src/commands/agent/trace/read.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/trace/read.ts)_
+_See code: [src/commands/agent/trace/read.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/trace/read.ts)_
 
 ## `sf agent validate authoring-bundle`
 
@@ -2007,6 +2452,6 @@ EXAMPLES
     $ sf agent validate authoring-bundle --api-name MyAuthoringBundle --target-org my-dev-org
 ```
 
-_See code: [src/commands/agent/validate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.42.1/src/commands/agent/validate/authoring-bundle.ts)_
+_See code: [src/commands/agent/validate/authoring-bundle.ts](https://github.com/salesforcecli/plugin-agent/blob/1.44.4/src/commands/agent/validate/authoring-bundle.ts)_
 
 <!-- commandsstop -->