@@ -62,9 +62,7 @@ sf plugins
6262<!-- commands -->
6363
6464- [ ` sf agent create ` ] ( #sf-agent-create )
65- - [ ` sf agent create-v2 ` ] ( #sf-agent-create-v2 )
6665- [ ` sf agent generate spec ` ] ( #sf-agent-generate-spec )
67- - [ ` sf agent generate spec-v2 ` ] ( #sf-agent-generate-spec-v2 )
6866- [ ` sf agent generate test-spec ` ] ( #sf-agent-generate-test-spec )
6967- [ ` sf agent preview ` ] ( #sf-agent-preview )
7068- [ ` sf agent test cancel ` ] ( #sf-agent-test-cancel )
@@ -76,53 +74,11 @@ sf plugins
7674
7775## ` sf agent create `
7876
79- Create an agent in your org from a local agent spec file.
80-
81- ```
82- USAGE
83- $ sf agent create -o <value> -f <value> -n <value> [--json] [--flags-dir <value>] [--api-version <value>]
84-
85- FLAGS
86- -f, --spec=<value> (required) Path to an agent spec file.
87- -n, --name=<value> (required) API name of the new agent.
88- -o, --target-org=<value> (required) Username or alias of the target org. Not required if the `target-org`
89- configuration variable is already set.
90- --api-version=<value> Override the api version used for api requests made by this command
91-
92- GLOBAL FLAGS
93- --flags-dir=<value> Import flag values from a directory.
94- --json Format output as json.
95-
96- DESCRIPTION
97- Create an agent in your org from a local agent spec file.
98-
99- To generate an agent spec file, run the "agent generate spec" CLI command, which outputs a JSON file with the list of
100- jobs and descriptions that the new agent can perform. Then specify this generated spec file to the --spec flag of this
101- command, along with the name of the new agent.
102-
103- When this command finishes, your org contains the new agent, which you can then edit in the Agent Builder UI. The new
104- agent already has a list of topics and actions that were automatically created from the list of jobs in the provided
105- agent spec file. This command also retrieves all the metadata files associated with the new agent to your local DX
106- project.
107-
108- To open the new agent in your org's Agent Builder UI, run this command: "sf org open agent --name
109- <api-name-of-your-agent>".
110-
111- EXAMPLES
112- Create an agent called "CustomerSupportAgent" in an org with alias "my-org" using the specified agent spec file:
113-
114- $ sf agent create --name CustomerSupportAgent --spec ./config/agentSpec.json --target-org my-org
115- ```
116-
117- _ See code: [ src/commands/agent/create.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1/src/commands/agent/create.ts ) _
118-
119- ## ` sf agent create-v2 `
120-
12177Create an agent in your org using a local agent spec file.
12278
12379```
12480USAGE
125- $ sf agent create-v2 -o <value> --spec <value> [--json] [--flags-dir <value>] [--api-version <value>] [--agent-name
81+ $ sf agent create -o <value> --spec <value> [--json] [--flags-dir <value>] [--api-version <value>] [--agent-name
12682 <value>] [--preview] [--agent-api-name <value>]
12783
12884FLAGS
@@ -161,83 +117,22 @@ DESCRIPTION
161117EXAMPLES
162118 Create an agent called "ResortManager" in an org with alias "my-org" using the specified agent spec file:
163119
164- $ sf agent create-v2 --agent-name ResortManager --spec specs/resortManagerAgent.yaml --target-org my-org
120+ $ sf agent create --agent-name ResortManager --spec specs/resortManagerAgent.yaml --target-org my-org
165121
166122 Preview the creation of an agent called "ResortManager" and use your default org:
167123
168- $ sf agent create-v2 --agent-name ResortManager --spec specs/resortManagerAgent.yaml --preview
124+ $ sf agent create --agent-name ResortManager --spec specs/resortManagerAgent.yaml --preview
169125```
170126
171- _ See code: [ src/commands/agent/create-v2 .ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/create-v2 .ts ) _
127+ _ See code: [ src/commands/agent/create.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/create.ts ) _
172128
173129## ` sf agent generate spec `
174130
175- Generate an agent spec, which is the list of jobs that the agent performs.
176-
177- ```
178- USAGE
179- $ sf agent generate spec -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-t customer|internal]
180- [--role <value>] [--company-name <value>] [--company-description <value>] [--company-website <value>] [-d <value>]
181- [-f <value>]
182-
183- FLAGS
184- -d, --output-dir=<value> [default: config] Directory where the agent spec file is written; can be an
185- absolute or relative path.
186- -f, --file-name=<value> [default: agentSpec.json] Name of the generated agent spec file.
187- -o, --target-org=<value> (required) Username or alias of the target org. Not required if the `target-org`
188- configuration variable is already set.
189- -t, --type=<option> Type of agent to create.
190- <options: customer|internal>
191- --api-version=<value> Override the api version used for api requests made by this command
192- --company-description=<value> Description of your company.
193- --company-name=<value> Name of your company.
194- --company-website=<value> Website URL of your company.
195- --role=<value> Role of the agent.
196-
197- GLOBAL FLAGS
198- --flags-dir=<value> Import flag values from a directory.
199- --json Format output as json.
200-
201- DESCRIPTION
202- Generate an agent spec, which is the list of jobs that the agent performs.
203-
204- When using Salesforce CLI to create an agent in your org, the first step is to generate the local JSON-formatted agent
205- spec file with this command.
206-
207- An agent spec is a list of jobs and descriptions that capture what the agent can do. Use flags such as --role and
208- --company-description to provide details about your company and the role that the agent plays in your company; you can
209- also enter the information interactively if you prefer. When you then execute this command, the large language model
210- (LLM) associated with your org uses the information to generate the list of jobs that the agent most likely performs.
211- We recommend that you provide good details for --role, --company-description, etc, so that the LLM can generate the
212- best and most relevant list of jobs and descriptions. Once generated, you can edit the spec file; for example, you can
213- remove jobs that don't apply to your agent.
214-
215- When your agent spec is ready, you then create the agent in your org by specifying the agent spec file to the
216- --job-spec flag of the "agent create" CLI command.
217-
218- EXAMPLES
219- Create an agent spec for your default org in the default location and use flags to specify the agent's role and your
220- company details:
221-
222- $ sf agent generate spec --type customer --role "Assist users in navigating and managing bookings" \
223- --company-name "Coral Cloud" --company-description "Resort that manages guests and their reservations and \
224- experiences"
225-
226- Create an agent spec by being prompted for role and company details interactively; write the generated file to the
227- "specs" directory and use the org with alias "my-org":
228-
229- $ sf agent generate spec --output-dir specs --target-org my-org
230- ```
231-
232- _ See code: [ src/commands/agent/generate/spec.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1/src/commands/agent/generate/spec.ts ) _
233-
234- ## ` sf agent generate spec-v2 `
235-
236131Generate an agent spec, which is a YAML file that captures what an agent can do.
237132
238133```
239134USAGE
240- $ sf agent generate spec-v2 -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-t customer|internal]
135+ $ sf agent generate spec -o <value> [--json] [--flags-dir <value>] [--api-version <value>] [-t customer|internal]
241136 [--role <value>] [--company-name <value>] [--company-description <value>] [--company-website <value>] [--max-topics
242137 <value>] [--agent-user <value>] [--enrich-logs true|false] [--tone formal|casual|neutral] [--spec <value>]
243138 [--output-file <value>] [--full-interview] [--grounding-context <value> --prompt-template <value>] [--no-prompt]
@@ -305,24 +200,24 @@ EXAMPLES
305200 Generate an agent spec in the default location and use flags to specify the agent properties, such as its role and
306201 your company details; use your default org:
307202
308- $ sf agent generate spec-v2 --type customer --role "Field customer complaints and manage employee schedules." \
203+ $ sf agent generate spec --type customer --role "Field customer complaints and manage employee schedules." \
309204 --company-name "Coral Cloud Resorts" --company-description "Provide customers with exceptional destination \
310205 activities, unforgettable experiences, and reservation services."
311206
312207 Generate an agent spec by being prompted for the required agent properties and generate a maxiumum of 5 topics;
313208 write the generated file to the "specs/resortManagerSpec.yaml" file and use the org with alias "my-org":
314209
315- $ sf agent generate spec-v2 --max-topics 5 --output-file specs/resortManagerAgent.yaml --target-org my-org
210+ $ sf agent generate spec --max-topics 5 --output-file specs/resortManagerAgent.yaml --target-org my-org
316211
317212 Specify an existing agent spec file called "specs/resortManagerAgent.yaml", and then overwrite it with a new version
318213 that contains newly AI-generated topics based on the updated role information passed in with the --role flag:
319214
320- $ sf agent generate spec-v2 --spec specs/resortManagerAgent.yaml --output-file specs/resortManagerAgent.yaml \
321- --role "Field customer complaints, manage employee schedules, and ensure all resort operations are running \
322- smoothly" --target-org my-org
215+ $ sf agent generate spec --spec specs/resortManagerAgent.yaml --output-file specs/resortManagerAgent.yaml --role \
216+ "Field customer complaints, manage employee schedules, and ensure all resort operations are running smoothly" \
217+ --target-org my-org
323218```
324219
325- _ See code: [ src/commands/agent/generate/spec-v2 .ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/generate/spec-v2 .ts ) _
220+ _ See code: [ src/commands/agent/generate/spec.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/generate/spec.ts ) _
326221
327222## ` sf agent generate test-spec `
328223
@@ -345,7 +240,7 @@ EXAMPLES
345240 $ sf agent generate test-spec
346241```
347242
348- _ See code: [ src/commands/agent/generate/test-spec.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/generate/test-spec.ts ) _
243+ _ See code: [ src/commands/agent/generate/test-spec.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/generate/test-spec.ts ) _
349244
350245## ` sf agent preview `
351246
@@ -380,7 +275,7 @@ FLAG DESCRIPTIONS
380275 the API name of the agent? (TBD based on agents library)
381276```
382277
383- _ See code: [ src/commands/agent/preview.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/preview.ts ) _
278+ _ See code: [ src/commands/agent/preview.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/preview.ts ) _
384279
385280## ` sf agent test cancel `
386281
@@ -417,7 +312,7 @@ EXAMPLES
417312 $ sf agent test cancel --job-id 4KBfake0000003F4AQ --target-org my-org
418313```
419314
420- _ See code: [ src/commands/agent/test/cancel.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/cancel.ts ) _
315+ _ See code: [ src/commands/agent/test/cancel.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/cancel.ts ) _
421316
422317## ` sf agent test create `
423318
@@ -453,7 +348,7 @@ FLAG DESCRIPTIONS
453348 More information about a flag. Don't repeat the summary.
454349```
455350
456- _ See code: [ src/commands/agent/test/create.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/create.ts ) _
351+ _ See code: [ src/commands/agent/test/create.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/create.ts ) _
457352
458353## ` sf agent test list `
459354
@@ -482,7 +377,7 @@ EXAMPLES
482377 $ sf agent test list
483378```
484379
485- _ See code: [ src/commands/agent/test/list.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/list.ts ) _
380+ _ See code: [ src/commands/agent/test/list.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/list.ts ) _
486381
487382## ` sf agent test results `
488383
@@ -538,7 +433,7 @@ FLAG DESCRIPTIONS
538433 test results aren't written.
539434```
540435
541- _ See code: [ src/commands/agent/test/results.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/results.ts ) _
436+ _ See code: [ src/commands/agent/test/results.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/results.ts ) _
542437
543438## ` sf agent test resume `
544439
@@ -601,7 +496,7 @@ FLAG DESCRIPTIONS
601496 test results aren't written.
602497```
603498
604- _ See code: [ src/commands/agent/test/resume.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/resume.ts ) _
499+ _ See code: [ src/commands/agent/test/resume.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/resume.ts ) _
605500
606501## ` sf agent test run `
607502
@@ -664,6 +559,6 @@ FLAG DESCRIPTIONS
664559 test results aren't written.
665560```
666561
667- _ See code: [ src/commands/agent/test/run.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.11.1 /src/commands/agent/test/run.ts ) _
562+ _ See code: [ src/commands/agent/test/run.ts] ( https://github.com/salesforcecli/plugin-agent/blob/1.12.0 /src/commands/agent/test/run.ts ) _
668563
669564<!-- commandsstop -->
0 commit comments