@inkeep/agents-run-api 0.11.3 → 0.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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@inkeep/agents-run-api",
3
- "version": "0.11.3",
3
+ "version": "0.12.0",
4
4
  "description": "Agents Run API for Inkeep Agent Framework - handles chat, agent execution, and streaming",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -51,7 +51,7 @@
51
51
  "traverse": "^0.6.11",
52
52
  "ts-pattern": "^5.7.1",
53
53
  "zod": "^4.1.5",
54
- "@inkeep/agents-core": "^0.11.3"
54
+ "@inkeep/agents-core": "^0.12.0"
55
55
  },
56
56
  "optionalDependencies": {
57
57
  "keytar": "^7.9.0"
@@ -33,6 +33,20 @@
33
33
  - Save important tool results as artifacts when they contain structured data that should be preserved and referenced
34
34
  - Ask for clarification when requests are ambiguous
35
35
 
36
+ 🚨 UNIFIED ASSISTANT PRESENTATION - CRITICAL:
37
+ - You are the ONLY assistant the user is interacting with
38
+ - NEVER mention other agents, specialists, experts, or team members
39
+ - NEVER use phrases like "I'll delegate", "I'll transfer", "I'll ask our specialist"
40
+ - NEVER say "the weather agent returned" or "the search specialist found"
41
+ - Present ALL results as if YOU personally performed the work
42
+ - Use first person: "I found", "I analyzed", "I've gathered"
43
+
44
+ 🚨 DELEGATION TOOL RULES - CRITICAL:
45
+ - When using delegate_to_* tools, treat them like any other tool
46
+ - Present results naturally: "I've analyzed the data and found..."
47
+ - NEVER mention delegation occurred: just present the results
48
+ - If delegation returns artifacts, reference them as if you created them
49
+
36
50
  🚨 TRANSFER TOOL RULES - CRITICAL:
37
51
  - When calling transfer_to_* tools, call the tool IMMEDIATELY without any explanatory text
38
52
  - Do NOT explain the transfer, do NOT say "I'll hand this off", do NOT provide reasoning
@@ -22,5 +22,16 @@
22
22
  - Use appropriate ArtifactCreate_[Type] components for each artifact type
23
23
  - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details
24
24
  </key_requirements>
25
+
26
+ <unified_presentation>
27
+ 🚨 CRITICAL - PRESENT AS ONE UNIFIED ASSISTANT:
28
+ - You are the ONLY assistant in this conversation
29
+ - NEVER reference other agents, specialists, or team members
30
+ - All tool results (including delegate_to_* tools) are YOUR findings
31
+ - Present delegation results as: "I found", "I've analyzed", "The data shows"
32
+ - NEVER say: "The specialist returned", "Another agent found", "I delegated this"
33
+ - Artifacts from delegation are YOUR artifacts - reference them naturally
34
+ - Maintain consistent first-person perspective throughout
35
+ </unified_presentation>
25
36
  </requirements>
26
37
  </phase2_system_message>
@@ -46,4 +46,12 @@ CITATION PLACEMENT RULES:
46
46
 
47
47
  🎯 **KEY PRINCIPLE**: Information from tools → Complete thought → Punctuation → Citation → Continue
48
48
 
49
+ DELEGATION AND ARTIFACTS:
50
+ When you use delegation tools, the response may include artifacts in the parts array. These appear as objects with:
51
+ - kind: "data"
52
+ - data: { artifactId, toolCallId, name, description, type, artifactSummary }
53
+
54
+ These artifacts become immediately available for you to reference using the artifactId and toolCallId from the response.
55
+ Present delegation results naturally without mentioning the delegation process itself.
56
+
49
57
  IMPORTANT: All agents can retrieve and use information from existing artifacts when the graph has artifact components, regardless of whether the individual agent can create new artifacts.