@salesforce/plugin-agent 1.27.7 → 1.29.0

package/messages/agent.generate.authoring-bundle.md

@@ -16,7 +16,7 @@ This command requires an org because it uses it to access an LLM for generating
 
 # flags.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. 
+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.
 
 # flags.spec.prompt
 
@@ -44,7 +44,7 @@ API name of the new authoring bundle; if not specified, the API name is derived
 
 # flags.api-name.prompt
 
-API name of the new authoring bundle
+Enter authoring bundle API name
 
 # examples
 
@@ -78,4 +78,52 @@ The specified file is not a valid agent spec YAML file.
 
 # error.failed-to-create-agent
 
-Failed to create an authoring bundle from the agent spec YAML file.
+Failed to generate authoring bundle: %s.
+
+# wizard.specType.prompt
+
+Select an authoring bundle template
+
+# wizard.specType.option.default.name
+
+Default template (Recommended)
+
+# wizard.specType.option.default.description
+
+Start with a ready-to-use Agent Script template.
+
+# wizard.specType.option.fromSpec.name
+
+From an agent spec YAML file (Advanced)
+
+# wizard.specType.option.fromSpec.description
+
+Generate an Agent Script file from an existing agent spec YAML file.
+
+# wizard.specFile.prompt
+
+Select the agent spec YAML file
+
+# wizard.name.prompt
+
+Enter the authoring bundle name
+
+# wizard.name.validation.required
+
+Authoring bundle name is required.
+
+# wizard.name.validation.empty
+
+Authoring bundle name can't be empty.
+
+# progress.title
+
+Generating authoring bundle: %s
+
+# success.message
+
+Authoring bundle "%s" was generated successfully.
+
+# warning.noSpecDir
+
+No agent spec directory found at %s.

package/messages/agent.preview.end.md

@@ -0,0 +1,47 @@
+# summary
+
+End an existing programmatic agent preview session and get trace location.
+
+# 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. 
+
+The original "agent preview start" command outputs a session ID which you then use with the --session-id flag of this command to end the session.  You don't have to specify the --session-id flag if an agent has only one active preview session. You must also use either the --authoring-bundle or --api-name flag to specify the API name of the authoring bundle or the published agent, respecitvely.  To find either API name, navigate to your package directory in your DX project. The API name of an authoring bundle is the same as its directory name under the "aiAuthoringBundles" metadata directory.  Similarly, the published agent's API name is the same as its directory name under the "Bots" metadata directory. 
+
+# flags.session-id.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.
+
+# flags.api-name.summary
+
+API name of the activated published agent you want to preview. 
+
+# flags.authoring-bundle.summary
+
+API name of the authoring bundle metadata component that contains the agent's Agent Script file.
+
+# error.noSession
+
+No agent preview session found. Run "sf agent preview start" to start a new agent preview session.
+
+# error.multipleSessions
+
+Multiple preview sessions found for this agent. Use the --session-id flag to identify a specific session. Sessions: %s
+
+# output.tracesPath
+
+Session traces: %s
+
+# examples
+
+- End a preview session of a published agent by specifying its session ID and API name ; use the default org:
+
+    <%= 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":
+
+    <%= 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.
+
+    <%= config.bin %> <%= command.id %> --authoring-bundle My_Local_Agent

package/messages/agent.preview.md

@@ -21,7 +21,7 @@ When the session concludes, the command asks if you want to save the API respons
 
 # flags.api-name.summary
 
-API name of the published and active agent you want to interact with.
+API name of the activated published agent you want to interact with.
 
 # flags.authoring-bundle.summary
 

package/messages/agent.preview.send.md

@@ -0,0 +1,47 @@
+# summary
+
+Send a message to an existing agent preview session.
+
+# 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.
+
+The 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. 
+
+# flags.session-id.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.
+
+# flags.utterance.summary
+
+Utterance to send to the agent, enclosed in double quotes.
+
+# flags.api-name.summary
+
+API name of the activated published agent you want to preview.
+
+# flags.authoring-bundle.summary
+
+API name of the authoring bundle metadata component that contains the agent's Agent Script file.
+
+# error.noSession
+
+No agent preview session found. Run "sf agent preview start" to start a new agent preview session.
+
+# error.multipleSessions
+
+Multiple preview sessions found for this agent. Use the --session-id flag to identify a specific session. Sessions: %s
+
+# examples
+
+- Send a message to an activated published agent using its API name and session ID; use the default org:
+
+   <%= 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":
+
+    <%= 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:
+
+    <%= config.bin %> <%= command.id %> --utterance "what can you help me with?" --authoring-bundle My_Local_Agent

package/messages/agent.preview.sessions.md

@@ -0,0 +1,27 @@
+# summary
+
+List all known programmatic agent preview sessions.
+
+# 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.
+
+Programmatic 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. 
+
+# output.empty
+
+No cached agent preview sessions found.
+
+# output.tableHeader.agent
+
+Agent (authoring bundle or API name)
+
+# output.tableHeader.sessionId
+
+Session ID
+
+# examples
+
+- List all cached agent preview sessions:
+
+   <%= config.bin %> <%= command.id %>

package/messages/agent.preview.start.md

@@ -0,0 +1,41 @@
+# summary
+
+Start a programmatic agent preview session. 
+
+# 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.
+
+Identify 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. 
+
+When starting a preview session using the authoring bundle, which contains the agent's Agent Script file, the preview uses mocked actions by default.  Specify --use-live-actions for live mode, which uses the real Apex classes, flows, etc, in the org for the actions.
+
+# flags.api-name.summary
+
+API name of the activated published agent you want to preview.
+
+# flags.authoring-bundle.summary
+
+API name of the authoring bundle metadata component that contains the agent's Agent Script file.
+
+# flags.use-live-actions.summary
+
+Use real actions in the org; if not specified, preview uses AI to simulate (mock) actions.
+
+# output.sessionId
+
+Session ID: %s
+
+# examples
+
+- Start a programmatic agent preview session by specifying an authoring bundle; uses mocked actions by default. Use the org with alias "my-dev-org":
+
+    <%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --target-org my-dev-org
+
+- Similar to previous example but use live actions and the default org:
+
+    <%= config.bin %> <%= command.id %> --authoring-bundle My_Agent_Bundle --use-live-actions
+
+- Start a preview session with an activated published agent:
+
+    <%= config.bin %> <%= command.id %> --api-name My_Published_Agent