@lota-sdk/core 0.1.38 → 0.1.40
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.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@lota-sdk/core",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.40",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"main": "./src/index.ts",
|
|
6
6
|
"types": "./src/index.ts",
|
|
@@ -32,7 +32,7 @@
|
|
|
32
32
|
"@chat-adapter/slack": "^4.23.0",
|
|
33
33
|
"@chat-adapter/state-ioredis": "^4.23.0",
|
|
34
34
|
"@logtape/logtape": "^2.0.5",
|
|
35
|
-
"@lota-sdk/shared": "0.1.
|
|
35
|
+
"@lota-sdk/shared": "0.1.40",
|
|
36
36
|
"@mendable/firecrawl-js": "^4.18.0",
|
|
37
37
|
"@surrealdb/node": "^3.0.3",
|
|
38
38
|
"ai": "^6.0.141",
|
|
@@ -14,6 +14,7 @@ import type { PrepareStepFunction, StopCondition, ToolLoopAgent, ToolSet, UIMess
|
|
|
14
14
|
import type { CoreWorkstreamProfile } from '../config/agent-defaults'
|
|
15
15
|
import {
|
|
16
16
|
agentDisplayNames,
|
|
17
|
+
agentRoster,
|
|
17
18
|
buildAgentTools,
|
|
18
19
|
createAgent,
|
|
19
20
|
getLeadAgentId,
|
|
@@ -911,7 +912,7 @@ export async function prepareWorkstreamRunCore(params: WorkstreamRunCoreParams):
|
|
|
911
912
|
} else {
|
|
912
913
|
// Multi-agent orchestration for group workstreams
|
|
913
914
|
const wsMembers = (workstream as { members?: string[] }).members ?? []
|
|
914
|
-
const members = wsMembers.length > 0 ? wsMembers : [
|
|
915
|
+
const members = wsMembers.length > 0 ? wsMembers : [...agentRoster]
|
|
915
916
|
const fallbackAgentId = coreWorkstreamProfile?.config.agentId ?? defaultLeadAgentId
|
|
916
917
|
|
|
917
918
|
const recentContext = currentMessages
|
|
@@ -65,9 +65,11 @@ Format: {"agentId":"<id>","routingContext":"<1-sentence instruction>"}`
|
|
|
65
65
|
const CHECK_SYSTEM_PROMPT = `You decide if another team member should also respond after the previous agent.
|
|
66
66
|
|
|
67
67
|
Rules:
|
|
68
|
-
-
|
|
69
|
-
-
|
|
70
|
-
-
|
|
68
|
+
- Add another agent if the user's message has a clearly separate dimension not yet covered.
|
|
69
|
+
- If the user explicitly addressed multiple agents (e.g. "CTO: ... CMO: ..."), each addressed agent MUST respond.
|
|
70
|
+
- If the previous agent deferred to another specialist, that specialist SHOULD respond.
|
|
71
|
+
- Do NOT add agents for agreement or acknowledgement only.
|
|
72
|
+
- Reply with ONLY a JSON object, no other text.
|
|
71
73
|
|
|
72
74
|
Format: {"done":true} or {"done":false,"agentId":"<id>","routingContext":"<1-sentence>"}`
|
|
73
75
|
|