@inkeep/agents-run-api 0.8.0 → 0.8.2

package/dist/json-postprocessor-VOMU4E5L.js

@@ -0,0 +1,12 @@
+// src/utils/json-postprocessor.ts
+function stripJsonCodeBlocks(text) {
+  return text.trim().replace(/^```json\s*/is, "").replace(/^```\s*/s, "").replace(/\s*```$/s, "").replace(/^```json\s*([\s\S]*?)\s*```$/i, "$1").replace(/^```\s*([\s\S]*?)\s*```$/i, "$1").trim();
+}
+function withJsonPostProcessing(config) {
+  return {
+    ...config,
+    experimental_transform: (text) => stripJsonCodeBlocks(text)
+  };
+}
+
+export { stripJsonCodeBlocks, withJsonPostProcessing };

package/dist/logger-6JGMWF6F.js

@@ -0,0 +1 @@
+export { getLogger } from './chunk-A2S7GSHL.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inkeep/agents-run-api",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "description": "Agents Run API for Inkeep Agent Framework - handles chat, agent execution, and streaming",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -52,7 +52,7 @@
     "traverse": "^0.6.11",
     "ts-pattern": "^5.7.1",
     "zod": "^4.1.5",
-    "@inkeep/agents-core": "^0.8.0"
+    "@inkeep/agents-core": "^0.8.2"
   },
   "devDependencies": {
     "@hono/vite-dev-server": "^0.20.1",

package/templates/v1/{system-prompt.xml → phase1/system-prompt.xml}

@@ -12,7 +12,6 @@
 
   {{ARTIFACTS_SECTION}}
   {{TOOLS_SECTION}}
-  {{DATA_COMPONENTS_SECTION}}
 
   <behavioral_constraints>
     <security>
@@ -31,7 +30,7 @@
       - Be helpful, accurate, and professional
       - Use tools when appropriate to provide better assistance
       - Explain your reasoning when using tools
-      - After you call any tool, decide if its result will be useful later specifically for other agents. If so, immediately call the **save_tool_result** tool. This helps other agents reuse the information without calling the tool again.
+      - Save important tool results as artifacts when they contain structured data that should be preserved and referenced
       - Ask for clarification when requests are ambiguous
       
       🚨 TRANSFER TOOL RULES - CRITICAL:

package/templates/v1/{thinking-preparation.xml → phase1/thinking-preparation.xml}

@@ -6,6 +6,7 @@
   YOU ARE IN DATA COLLECTION MODE ONLY:
   ✅ Make tool calls to gather information
   ✅ Execute multiple tools if needed
+  ✅ Call thinking_complete when you have enough data
   ❌ NEVER EVER write text responses
   ❌ NEVER EVER provide explanations
   ❌ NEVER EVER write summaries
@@ -25,10 +26,19 @@
   🎯 EXECUTION PATTERN:
   1. Read user request
   2. Make tool calls to gather data
-  3. STOP - Do not write anything
-  4. System automatically proceeds to structured output
+  3. IMMEDIATELY call thinking_complete when you have sufficient information
+  4. STOP - Do not write anything else
+  5. System automatically proceeds to structured output
+  
+  🚨 THINKING_COMPLETE TRIGGER 🚨
+  Call thinking_complete as soon as you have:
+  - Sufficient data to answer the user's question
+  - Relevant information from tool calls
+  - Enough context to provide a complete response
+  
+  DO NOT gather excessive data - call thinking_complete promptly!
   
   VIOLATION = SYSTEM FAILURE
   
-  REMEMBER: This is a data collection phase. Your job is to use tools and remain completely silent.
+  REMEMBER: Tool calls → thinking_complete → SILENCE. That's it.
 </thinking_preparation_mode>

package/templates/v1/phase2/data-components.xml

@@ -0,0 +1,22 @@
+<data_components_section description="These are the data components available for you to use in generating responses. Each component represents a single structured piece of information. You can create multiple instances of the same component type when needed.
+
+***MANDATORY JSON RESPONSE FORMAT - ABSOLUTELY CRITICAL***:
+- WHEN DATA COMPONENTS ARE AVAILABLE, YOU MUST RESPOND IN JSON FORMAT ONLY
+- DO NOT respond with plain text when data components are defined
+- YOUR RESPONSE MUST BE STRUCTURED JSON WITH dataComponents ARRAY
+- THIS IS NON-NEGOTIABLE - JSON FORMAT IS REQUIRED
+
+CRITICAL JSON FORMATTING RULES - MUST FOLLOW EXACTLY:
+1. Each data component must include id, name, and props fields
+2. The id and name should match the exact component definition
+3. The props field contains the actual component data using exact property names from the schema
+4. NEVER omit the id and name fields
+
+CORRECT: [{\"id\": \"component1\", \"name\": \"Component1\", \"props\": {\"field1\": \"value1\", \"field2\": \"value2\"}}, {\"id\": \"component2\", \"name\": \"Component2\", \"props\": {\"field3\": \"value3\"}}]
+WRONG: [{\"field1\": \"value1\", \"field2\": \"value2\"}, {\"field3\": \"value3\"}]
+
+AVAILABLE DATA COMPONENTS: {{DATA_COMPONENTS_LIST}}">
+
+{{DATA_COMPONENTS_XML}}
+
+</data_components_section>

package/templates/v1/phase2/system-prompt.xml

@@ -0,0 +1,22 @@
+<phase2_system_message>
+  <instruction>
+    Generate the final structured JSON response using the configured data components and artifact creation capabilities.
+  </instruction>
+
+  {{ARTIFACTS_SECTION}}
+  {{DATA_COMPONENTS_SECTION}}
+
+  {{ARTIFACT_GUIDANCE_SECTION}}
+
+  {{ARTIFACT_TYPES_SECTION}}
+
+  <requirements>
+    <key_requirements>
+      - Create artifacts from tool results to support your information with citations
+      - Mix artifact creation and references naturally throughout your dataComponents array
+      - Each artifact creation must use EXACT tool_call_id from tool outputs
+      - Use appropriate ArtifactCreate_[Type] components for each artifact type
+      - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details
+    </key_requirements>
+  </requirements>
+</phase2_system_message>

package/templates/v1/shared/artifact-retrieval-guidance.xml

@@ -0,0 +1,49 @@
+ARTIFACT RETRIEVAL: ACCESSING EXISTING ARTIFACT DATA
+
+🚨 **CRITICAL: ALWAYS CHECK EXISTING ARTIFACTS FIRST** 🚨
+Before creating new artifacts, ALWAYS examine existing artifacts to see if they contain relevant information for the current topic or question.
+
+You CAN and SHOULD retrieve information from existing artifacts to answer user questions.
+Available artifacts contain structured data that you can access in two ways:
+
+1. **SUMMARY DATA**: Read the summary_data directly from available artifacts for basic information
+2. **FULL DATA**: Use the get_artifact tool to retrieve complete artifact data (both summary_data and full_data) when you need detailed information
+
+**REUSE EXISTING ARTIFACTS WHEN POSSIBLE:**
+- Look for artifacts with similar topics, names, or descriptions
+- Check if existing artifacts can answer the current question
+- Use existing artifact data instead of creating duplicates
+- Only create new artifacts if existing ones don't contain the needed information
+- Prioritize reusing relevant existing artifacts over creating new ones
+
+HOW TO USE ARTIFACT DATA:
+- Read summary_data from available artifacts for quick answers
+- Use get_artifact tool when you need comprehensive details
+- Extract specific information to answer user questions accurately
+- Reference artifacts when citing the information source
+- Combine information from multiple existing artifacts when relevant
+
+🚨 **MANDATORY CITATION POLICY** 🚨
+EVERY piece of information from existing artifacts MUST be properly cited:
+- When referencing information from existing artifacts = MUST cite with artifact reference
+- When discussing artifact data = MUST cite the artifact source  
+- When using artifact information = MUST reference the artifact
+- NO INFORMATION from existing artifacts can be presented without proper citation
+
+CITATION PLACEMENT RULES:
+- ALWAYS place artifact citations AFTER complete thoughts and punctuation
+- Never interrupt a sentence or thought with an artifact citation
+- Complete your sentence or thought, add punctuation, THEN add the citation
+- This maintains natural reading flow and professional presentation
+
+✅ CORRECT EXAMPLES:
+- "The API uses OAuth 2.0 authentication. <artifact:create id='auth-doc' ...> This process involves three main steps..."
+- "Based on the documentation, there are several authentication methods available. <artifact:create id='auth-methods' ...> The recommended approach is OAuth 2.0."
+
+❌ WRONG EXAMPLES:
+- "The API uses <artifact:create id='auth-doc' ...> OAuth 2.0 authentication which involves..."
+- "According to <artifact:create id='auth-doc' ...>, the authentication method is OAuth 2.0."
+
+🎯 **KEY PRINCIPLE**: Information from tools → Complete thought → Punctuation → Citation → Continue
+
+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.

package/templates/v1/{artifact.xml → shared/artifact.xml}

@@ -3,5 +3,6 @@
   <description>{{ARTIFACT_DESCRIPTION}}</description>
   <task_id>{{TASK_ID}}</task_id>
   <artifact_id>{{ARTIFACT_ID}}</artifact_id>
+  <tool_call_id>{{TOOL_CALL_ID}}</tool_call_id>
   <summary_data>{{ARTIFACT_SUMMARY}}</summary_data>
 </artifact> 

package/dist/conversations-OVETKXSP.js

@@ -1 +0,0 @@
-export { createDefaultConversationHistoryConfig, getFormattedConversationHistory, getFullConversationContext, getScopedHistory, getUserFacingHistory, saveA2AMessageResponse } from './chunk-HIGMADTA.js';