@salesforce/plugin-agent 1.11.0 → 1.12.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "commands": {
3
- "agent:create-v2": {
3
+ "agent:create": {
4
4
  "aliases": [],
5
5
  "args": {},
6
6
  "description": "Before you run this command, you must first generate an agent spec file by running the \"agent generate spec\" CLI command, which outputs a YAML file with the agent properties and list of AI-generated topics. Topics define the range of jobs the agent can handle. Then specify the generated agent spec file to this command using the --spec flag, along with the name (label) of the new agent using the --agent-name flag.\n\nWhen this command finishes, your org contains the new agent, which you can then edit in the Agent Builder UI. The new agent's topics are the same as the ones listed in the agent spec file. The agent might also have some AI-generated actions. This command also retrieves all the metadata files associated with the new agent to your local Salesforce DX project.\n\nUse the --preview flag to review what the agent looks like without actually saving it in your org. Rather, the command creates a JSON file with all the agent details in the current directory.\n\nTo open the new agent in your org's Agent Builder UI, run this command: \"sf org open agent --name <api-name-of-your-agent>\".",
@@ -48,36 +48,6 @@
48
48
  "multiple": false,
49
49
  "type": "option"
50
50
  },
51
- "user-id": {
52
- "name": "user-id",
53
- "summary": "ID of a user in your org that is assigned to your agent; determines what your agent can access and do.",
54
- "hasDynamicHelp": false,
55
- "multiple": false,
56
- "type": "option"
57
- },
58
- "enrich-logs": {
59
- "name": "enrich-logs",
60
- "summary": "Adds agent conversation data to event logs so you can view all agent session activity in one place.",
61
- "hasDynamicHelp": false,
62
- "multiple": false,
63
- "options": [
64
- "true",
65
- "false"
66
- ],
67
- "type": "option"
68
- },
69
- "tone": {
70
- "name": "tone",
71
- "summary": "Conversational style of the agent, such as how it expresses your brand personality in its messages through word choice, punctuation, and sentence structure.",
72
- "hasDynamicHelp": false,
73
- "multiple": false,
74
- "options": [
75
- "formal",
76
- "casual",
77
- "neutral"
78
- ],
79
- "type": "option"
80
- },
81
51
  "spec": {
82
52
  "name": "spec",
83
53
  "required": true,
@@ -93,111 +63,16 @@
93
63
  "type": "boolean"
94
64
  },
95
65
  "agent-api-name": {
96
- "hidden": true,
97
66
  "name": "agent-api-name",
98
67
  "summary": "API name of the new agent; if not specified, the API name is derived from the agent name (label); the API name must not exist in the org.",
99
68
  "hasDynamicHelp": false,
100
69
  "multiple": false,
101
70
  "type": "option"
102
71
  },
103
- "primary-language": {
104
- "hidden": true,
105
- "name": "primary-language",
106
- "summary": "Language the agent uses in conversations.",
107
- "default": "en_US",
108
- "hasDynamicHelp": false,
109
- "multiple": false,
110
- "options": [
111
- "en_US"
112
- ],
113
- "type": "option"
114
- },
115
72
  "planner-id": {
73
+ "hidden": true,
116
74
  "name": "planner-id",
117
- "summary": "The GenAiPlanner ID to associate with the agent.",
118
- "hasDynamicHelp": false,
119
- "multiple": false,
120
- "type": "option"
121
- }
122
- },
123
- "hasDynamicHelp": true,
124
- "hiddenAliases": [],
125
- "id": "agent:create-v2",
126
- "pluginAlias": "@salesforce/plugin-agent",
127
- "pluginName": "@salesforce/plugin-agent",
128
- "pluginType": "core",
129
- "state": "beta",
130
- "strict": true,
131
- "summary": "Create an agent in your org using a local agent spec file.",
132
- "enableJsonFlag": true,
133
- "requiresProject": true,
134
- "isESM": true,
135
- "relativePath": [
136
- "lib",
137
- "commands",
138
- "agent",
139
- "create-v2.js"
140
- ],
141
- "aliasPermutations": [],
142
- "permutations": [
143
- "agent:create-v2",
144
- "create-v2:agent"
145
- ]
146
- },
147
- "agent:create": {
148
- "aliases": [],
149
- "args": {},
150
- "description": "To generate an agent spec file, run the \"agent generate spec\" CLI command, which outputs a JSON file with the list of jobs and descriptions that the new agent can perform. Then specify this generated spec file to the --spec flag of this command, along with the name of the new agent.\n\nWhen this command finishes, your org contains the new agent, which you can then edit in the Agent Builder UI. The new agent already has a list of topics and actions that were automatically created from the list of jobs in the provided agent spec file. This command also retrieves all the metadata files associated with the new agent to your local DX project.\n\nTo open the new agent in your org's Agent Builder UI, run this command: \"sf org open agent --name <api-name-of-your-agent>\".",
151
- "examples": [
152
- "Create an agent called \"CustomerSupportAgent\" in an org with alias \"my-org\" using the specified agent spec file:\n<%= config.bin %> <%= command.id %> --name CustomerSupportAgent --spec ./config/agentSpec.json --target-org my-org"
153
- ],
154
- "flags": {
155
- "json": {
156
- "description": "Format output as json.",
157
- "helpGroup": "GLOBAL",
158
- "name": "json",
159
- "allowNo": false,
160
- "type": "boolean"
161
- },
162
- "flags-dir": {
163
- "helpGroup": "GLOBAL",
164
- "name": "flags-dir",
165
- "summary": "Import flag values from a directory.",
166
- "hasDynamicHelp": false,
167
- "multiple": false,
168
- "type": "option"
169
- },
170
- "target-org": {
171
- "char": "o",
172
- "name": "target-org",
173
- "noCacheDefault": true,
174
- "required": true,
175
- "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
176
- "hasDynamicHelp": true,
177
- "multiple": false,
178
- "type": "option"
179
- },
180
- "api-version": {
181
- "description": "Override the api version used for api requests made by this command",
182
- "name": "api-version",
183
- "hasDynamicHelp": false,
184
- "multiple": false,
185
- "type": "option"
186
- },
187
- "spec": {
188
- "char": "f",
189
- "name": "spec",
190
- "required": true,
191
- "summary": "Path to an agent spec file.",
192
- "hasDynamicHelp": false,
193
- "multiple": false,
194
- "type": "option"
195
- },
196
- "name": {
197
- "char": "n",
198
- "name": "name",
199
- "required": true,
200
- "summary": "API name of the new agent.",
75
+ "summary": "An existing GenAiPlanner ID to associate with the agent.",
201
76
  "hasDynamicHelp": false,
202
77
  "multiple": false,
203
78
  "type": "option"
@@ -211,7 +86,7 @@
211
86
  "pluginType": "core",
212
87
  "state": "beta",
213
88
  "strict": true,
214
- "summary": "Create an agent in your org from a local agent spec file.",
89
+ "summary": "Create an agent in your org using a local agent spec file.",
215
90
  "enableJsonFlag": true,
216
91
  "requiresProject": true,
217
92
  "isESM": true,
@@ -295,7 +170,7 @@
295
170
  "preview:agent"
296
171
  ]
297
172
  },
298
- "agent:generate:spec-v2": {
173
+ "agent:generate:spec": {
299
174
  "aliases": [],
300
175
  "args": {},
301
176
  "description": "Before you use Salesforce CLI to create an agent in your org, you must first generate an agent spec with this command. An agent spec is a YAML-formatted file that contains information about the agent, such as its role and company description, and then 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 information. Upon command execution, the large language model (LLM) associated with your org uses the information you provided 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 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 to your agent or change the description of a particular topic.\n\nYou can 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 a custom prompt template that the agent uses, and ground the prompt template to add context and personalization to the agent's prompts.\n\nWhen your agent spec is ready, you then create the agent in your org by running the \"agent create\" CLI command and specifying the spec with the --spec flag.",
@@ -377,21 +252,6 @@
377
252
  "multiple": false,
378
253
  "type": "option"
379
254
  },
380
- "spec": {
381
- "name": "spec",
382
- "summary": "Agent spec file, in YAML format, to use as input to the command.",
383
- "hasDynamicHelp": false,
384
- "multiple": false,
385
- "type": "option"
386
- },
387
- "output-file": {
388
- "name": "output-file",
389
- "summary": "Path for the generated YAML agent spec file; can be an absolute or relative path.",
390
- "default": "config/agentSpec.yaml",
391
- "hasDynamicHelp": false,
392
- "multiple": false,
393
- "type": "option"
394
- },
395
255
  "max-topics": {
396
256
  "name": "max-topics",
397
257
  "summary": "Maximum number of topics to generate in the agent spec; default is 10.",
@@ -399,151 +259,79 @@
399
259
  "multiple": false,
400
260
  "type": "option"
401
261
  },
402
- "prompt-template": {
403
- "name": "prompt-template",
404
- "summary": "API name of a customized prompt template to use instead of the default prompt template.",
262
+ "agent-user": {
263
+ "name": "agent-user",
264
+ "summary": "Username of a user in your org to assign to your agent; determines what your agent can access and do.",
405
265
  "hasDynamicHelp": false,
406
266
  "multiple": false,
407
267
  "type": "option"
408
268
  },
409
- "grounding-context": {
410
- "dependsOn": [
411
- "prompt-template"
412
- ],
413
- "name": "grounding-context",
414
- "summary": "Context information and personalization that's added to your prompts when using a custom prompt template.",
415
- "hasDynamicHelp": false,
416
- "multiple": false,
417
- "type": "option"
418
- }
419
- },
420
- "hasDynamicHelp": true,
421
- "hiddenAliases": [],
422
- "id": "agent:generate:spec-v2",
423
- "pluginAlias": "@salesforce/plugin-agent",
424
- "pluginName": "@salesforce/plugin-agent",
425
- "pluginType": "core",
426
- "state": "beta",
427
- "strict": true,
428
- "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
429
- "enableJsonFlag": true,
430
- "requiresProject": true,
431
- "isESM": true,
432
- "relativePath": [
433
- "lib",
434
- "commands",
435
- "agent",
436
- "generate",
437
- "spec-v2.js"
438
- ],
439
- "aliasPermutations": [],
440
- "permutations": [
441
- "agent:generate:spec-v2",
442
- "generate:agent:spec-v2",
443
- "generate:spec-v2:agent",
444
- "agent:spec-v2:generate",
445
- "spec-v2:agent:generate",
446
- "spec-v2:generate:agent"
447
- ]
448
- },
449
- "agent:generate:spec": {
450
- "aliases": [],
451
- "args": {},
452
- "description": "When using Salesforce CLI to create an agent in your org, the first step is to generate the local JSON-formatted agent spec file with this command.\n\nAn agent spec is a list of jobs and descriptions that capture what the agent can do. Use flags such as --role and --company-description to provide details about your company and the role that the agent plays in your company; you can also enter the information interactively if you prefer. When you then execute this command, the large language model (LLM) associated with your org uses the information to generate the list of jobs that the agent most likely performs. We recommend that you provide good details for --role, --company-description, etc, so that the LLM can generate the best and most relevant list of jobs and descriptions. Once generated, you can edit the spec file; for example, you can remove jobs that don't apply to your agent.\n\nWhen your agent spec is ready, you then create the agent in your org by specifying the agent spec file to the --job-spec flag of the \"agent create\" CLI command.",
453
- "examples": [
454
- "Create an agent spec for your default org in the default location and use flags to specify the agent's role and your company details:\n<%= config.bin %> <%= command.id %> --type customer --role \"Assist users in navigating and managing bookings\" --company-name \"Coral Cloud\" --company-description \"Resort that manages guests and their reservations and experiences\"",
455
- "Create an agent spec by being prompted for role and company details interactively; write the generated file to the \"specs\" directory and use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --output-dir specs --target-org my-org"
456
- ],
457
- "flags": {
458
- "json": {
459
- "description": "Format output as json.",
460
- "helpGroup": "GLOBAL",
461
- "name": "json",
462
- "allowNo": false,
463
- "type": "boolean"
464
- },
465
- "flags-dir": {
466
- "helpGroup": "GLOBAL",
467
- "name": "flags-dir",
468
- "summary": "Import flag values from a directory.",
469
- "hasDynamicHelp": false,
470
- "multiple": false,
471
- "type": "option"
472
- },
473
- "target-org": {
474
- "char": "o",
475
- "name": "target-org",
476
- "noCacheDefault": true,
477
- "required": true,
478
- "summary": "Username or alias of the target org. Not required if the `target-org` configuration variable is already set.",
479
- "hasDynamicHelp": true,
480
- "multiple": false,
481
- "type": "option"
482
- },
483
- "api-version": {
484
- "description": "Override the api version used for api requests made by this command",
485
- "name": "api-version",
269
+ "enrich-logs": {
270
+ "name": "enrich-logs",
271
+ "summary": "Adds agent conversation data to event logs so you can view all agent session activity in one place.",
486
272
  "hasDynamicHelp": false,
487
273
  "multiple": false,
274
+ "options": [
275
+ "true",
276
+ "false"
277
+ ],
488
278
  "type": "option"
489
279
  },
490
- "type": {
491
- "char": "t",
492
- "name": "type",
493
- "summary": "Type of agent to create.",
280
+ "tone": {
281
+ "name": "tone",
282
+ "summary": "Conversational style of the agent, such as how it expresses your brand personality in its messages through word choice, punctuation, and sentence structure.",
494
283
  "hasDynamicHelp": false,
495
284
  "multiple": false,
496
285
  "options": [
497
- "customer",
498
- "internal"
286
+ "formal",
287
+ "casual",
288
+ "neutral"
499
289
  ],
500
290
  "type": "option"
501
291
  },
502
- "role": {
503
- "name": "role",
504
- "summary": "Role of the agent.",
292
+ "spec": {
293
+ "name": "spec",
294
+ "summary": "Agent spec file, in YAML format, to use as input to the command.",
505
295
  "hasDynamicHelp": false,
506
296
  "multiple": false,
507
297
  "type": "option"
508
298
  },
509
- "company-name": {
510
- "name": "company-name",
511
- "summary": "Name of your company.",
299
+ "output-file": {
300
+ "name": "output-file",
301
+ "summary": "Path for the generated YAML agent spec file; can be an absolute or relative path.",
302
+ "default": "config/agentSpec.yaml",
512
303
  "hasDynamicHelp": false,
513
304
  "multiple": false,
514
305
  "type": "option"
515
306
  },
516
- "company-description": {
517
- "name": "company-description",
518
- "summary": "Description of your company.",
519
- "hasDynamicHelp": false,
520
- "multiple": false,
521
- "type": "option"
307
+ "full-interview": {
308
+ "name": "full-interview",
309
+ "summary": "Prompt for both required and optional flags.",
310
+ "allowNo": false,
311
+ "type": "boolean"
522
312
  },
523
- "company-website": {
524
- "name": "company-website",
525
- "summary": "Website URL of your company.",
313
+ "prompt-template": {
314
+ "name": "prompt-template",
315
+ "summary": "API name of a customized prompt template to use instead of the default prompt template.",
526
316
  "hasDynamicHelp": false,
527
317
  "multiple": false,
528
318
  "type": "option"
529
319
  },
530
- "output-dir": {
531
- "char": "d",
532
- "name": "output-dir",
533
- "summary": "Directory where the agent spec file is written; can be an absolute or relative path.",
534
- "default": "config",
320
+ "grounding-context": {
321
+ "dependsOn": [
322
+ "prompt-template"
323
+ ],
324
+ "name": "grounding-context",
325
+ "summary": "Context information and personalization that's added to your prompts when using a custom prompt template.",
535
326
  "hasDynamicHelp": false,
536
327
  "multiple": false,
537
328
  "type": "option"
538
329
  },
539
- "file-name": {
540
- "char": "f",
541
- "name": "file-name",
542
- "summary": "Name of the generated agent spec file.",
543
- "default": "agentSpec.json",
544
- "hasDynamicHelp": false,
545
- "multiple": false,
546
- "type": "option"
330
+ "no-prompt": {
331
+ "name": "no-prompt",
332
+ "summary": "Don't prompt the user to confirm spec file overwrite.",
333
+ "allowNo": false,
334
+ "type": "boolean"
547
335
  }
548
336
  },
549
337
  "hasDynamicHelp": true,
@@ -554,7 +342,7 @@
554
342
  "pluginType": "core",
555
343
  "state": "beta",
556
344
  "strict": true,
557
- "summary": "Generate an agent spec, which is the list of jobs that the agent performs.",
345
+ "summary": "Generate an agent spec, which is a YAML file that captures what an agent can do.",
558
346
  "enableJsonFlag": true,
559
347
  "requiresProject": true,
560
348
  "isESM": true,
@@ -1198,5 +986,5 @@
1198
986
  ]
1199
987
  }
1200
988
  },
1201
- "version": "1.11.0"
989
+ "version": "1.12.0"
1202
990
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-agent",
3
3
  "description": "Commands to interact with Salesforce agents",
4
- "version": "1.11.0",
4
+ "version": "1.12.0",
5
5
  "author": "Salesforce",
6
6
  "bugs": "https://github.com/forcedotcom/cli/issues",
7
7
  "dependencies": {
@@ -9,7 +9,7 @@
9
9
  "@inquirer/prompts": "^7.2.0",
10
10
  "@oclif/core": "^4",
11
11
  "@oclif/multi-stage-output": "^0.7.12",
12
- "@salesforce/agents": "^0.9.0",
12
+ "@salesforce/agents": "^0.9.2",
13
13
  "@salesforce/core": "^8.8.0",
14
14
  "@salesforce/kit": "^3.2.1",
15
15
  "@salesforce/sf-plugins-core": "^12.1.0",
@@ -226,7 +226,7 @@
226
226
  "exports": "./lib/index.js",
227
227
  "type": "module",
228
228
  "sfdx": {
229
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.11.0.crt",
230
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.11.0.sig"
229
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.12.0.crt",
230
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-agent/1.12.0.sig"
231
231
  }
232
232
  }
@@ -4,18 +4,142 @@
4
4
  "definitions": {
5
5
  "AgentCreateResult": {
6
6
  "type": "object",
7
+ "additionalProperties": false,
7
8
  "properties": {
9
+ "previewFilePath": {
10
+ "type": "string"
11
+ },
8
12
  "isSuccess": {
9
13
  "type": "boolean"
10
14
  },
11
15
  "errorMessage": {
12
16
  "type": "string"
17
+ },
18
+ "agentId": {
19
+ "type": "object",
20
+ "properties": {
21
+ "botId": {
22
+ "type": "string"
23
+ },
24
+ "botVersionId": {
25
+ "type": "string"
26
+ },
27
+ "plannerId": {
28
+ "type": "string"
29
+ }
30
+ },
31
+ "required": ["botId", "botVersionId", "plannerId"],
32
+ "additionalProperties": false,
33
+ "description": "If the agent was created with saveAgent=true, these are the IDs that make up an agent; Bot, BotVersion, and GenAiPlanner metadata."
34
+ },
35
+ "agentDefinition": {
36
+ "type": "object",
37
+ "properties": {
38
+ "agentDescription": {
39
+ "type": "string"
40
+ },
41
+ "topics": {
42
+ "type": "array",
43
+ "items": {
44
+ "type": "object",
45
+ "properties": {
46
+ "scope": {
47
+ "type": "string"
48
+ },
49
+ "topic": {
50
+ "type": "string"
51
+ },
52
+ "actions": {
53
+ "type": "array",
54
+ "items": {
55
+ "type": "object",
56
+ "properties": {
57
+ "actionName": {
58
+ "type": "string"
59
+ },
60
+ "exampleOutput": {
61
+ "type": "string"
62
+ },
63
+ "actionDescription": {
64
+ "type": "string"
65
+ },
66
+ "inputs": {
67
+ "type": "array",
68
+ "items": {
69
+ "type": "object",
70
+ "properties": {
71
+ "inputName": {
72
+ "type": "string"
73
+ },
74
+ "inputDataType": {
75
+ "type": "string"
76
+ },
77
+ "inputDescription": {
78
+ "type": "string"
79
+ }
80
+ },
81
+ "required": ["inputName", "inputDataType", "inputDescription"],
82
+ "additionalProperties": false
83
+ },
84
+ "minItems": 1,
85
+ "maxItems": 1
86
+ },
87
+ "outputs": {
88
+ "type": "array",
89
+ "items": {
90
+ "type": "object",
91
+ "properties": {
92
+ "outputName": {
93
+ "type": "string"
94
+ },
95
+ "outputDataType": {
96
+ "type": "string"
97
+ },
98
+ "outputDescription": {
99
+ "type": "string"
100
+ }
101
+ },
102
+ "required": ["outputName", "outputDataType", "outputDescription"],
103
+ "additionalProperties": false
104
+ },
105
+ "minItems": 1,
106
+ "maxItems": 1
107
+ }
108
+ },
109
+ "required": ["actionName", "exampleOutput", "actionDescription", "inputs", "outputs"],
110
+ "additionalProperties": false
111
+ },
112
+ "minItems": 1,
113
+ "maxItems": 1
114
+ },
115
+ "instructions": {
116
+ "type": "array",
117
+ "items": {
118
+ "type": "string"
119
+ }
120
+ },
121
+ "classificationDescription": {
122
+ "type": "string"
123
+ }
124
+ },
125
+ "required": ["scope", "topic", "actions", "instructions", "classificationDescription"],
126
+ "additionalProperties": false
127
+ },
128
+ "minItems": 1,
129
+ "maxItems": 1
130
+ },
131
+ "sampleUtterances": {
132
+ "type": "array",
133
+ "items": {
134
+ "type": "string"
135
+ }
136
+ }
137
+ },
138
+ "required": ["agentDescription", "topics", "sampleUtterances"],
139
+ "additionalProperties": false
13
140
  }
14
141
  },
15
- "required": [
16
- "isSuccess"
17
- ],
18
- "additionalProperties": false
142
+ "required": ["agentDefinition", "isSuccess"]
19
143
  }
20
144
  }
21
- }
145
+ }
@@ -4,21 +4,69 @@
4
4
  "definitions": {
5
5
  "AgentCreateSpecResult": {
6
6
  "type": "object",
7
+ "additionalProperties": false,
7
8
  "properties": {
9
+ "topics": {
10
+ "$ref": "#/definitions/DraftAgentTopics"
11
+ },
12
+ "agentType": {
13
+ "type": "string",
14
+ "enum": ["customer", "internal"],
15
+ "description": "Internal type is copilots; used by customers' employees. Customer type is agents; used by customers' customers."
16
+ },
17
+ "role": {
18
+ "type": "string"
19
+ },
20
+ "companyName": {
21
+ "type": "string"
22
+ },
23
+ "companyDescription": {
24
+ "type": "string"
25
+ },
26
+ "companyWebsite": {
27
+ "type": "string"
28
+ },
29
+ "maxNumOfTopics": {
30
+ "type": "number",
31
+ "description": "The maximum number of topics to create in the spec. Default is 10."
32
+ },
33
+ "promptTemplateName": {
34
+ "type": "string",
35
+ "description": "Developer name of the prompt template."
36
+ },
37
+ "groundingContext": {
38
+ "type": "string",
39
+ "description": "Context info to be used in customized prompt template"
40
+ },
8
41
  "isSuccess": {
9
42
  "type": "boolean"
10
43
  },
11
44
  "errorMessage": {
12
45
  "type": "string"
13
46
  },
14
- "jobSpec": {
47
+ "specPath": {
15
48
  "type": "string"
16
49
  }
17
50
  },
18
- "required": [
19
- "isSuccess"
20
- ],
21
- "additionalProperties": false
51
+ "required": ["agentType", "companyDescription", "companyName", "isSuccess", "role", "topics"]
52
+ },
53
+ "DraftAgentTopics": {
54
+ "type": "array",
55
+ "items": {
56
+ "type": "object",
57
+ "properties": {
58
+ "name": {
59
+ "type": "string"
60
+ },
61
+ "description": {
62
+ "type": "string"
63
+ }
64
+ },
65
+ "required": ["name", "description"],
66
+ "additionalProperties": false
67
+ },
68
+ "minItems": 1,
69
+ "maxItems": 1
22
70
  }
23
71
  }
24
- }
72
+ }