From 36ab7cdfe44626ba60593700e5aa7a1f66f344bc Mon Sep 17 00:00:00 2001 From: Zach Leventer Date: Fri, 24 Apr 2026 17:51:26 -0400 Subject: [PATCH] fix: typo and prose tightening in agent preview send/end help text --- messages/agent.preview.end.md | 2 +- messages/agent.preview.send.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/messages/agent.preview.end.md b/messages/agent.preview.end.md index fc75cfe6..2734aa5c 100644 --- a/messages/agent.preview.end.md +++ b/messages/agent.preview.end.md @@ -6,7 +6,7 @@ End an existing programmatic agent preview session and get trace location. 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. +Use the session ID from `agent preview start` with the `--session-id` flag to end the session. Omit `--session-id` if the 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. # flags.session-id.summary diff --git a/messages/agent.preview.send.md b/messages/agent.preview.send.md index 5890e6cd..cd26bf7f 100644 --- a/messages/agent.preview.send.md +++ b/messages/agent.preview.send.md @@ -6,7 +6,7 @@ Send a message to an existing agent preview session. 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. +Use the session ID from `agent preview start` with the `--session-id` flag to send a message. Omit `--session-id` if the 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. # flags.session-id.summary