@inkeep/agents-run-api 0.10.1 → 0.11.0

package/README.md

@@ -29,18 +29,16 @@ This API handles the execution layer of the Inkeep Agent Framework:
 ## Development
 
 ### Setup
-If you do not have the db setup:
-```bash 
-cd packages/core
-pnpm db:push
-```
-
-Then:
 ```bash
 cd agents-run-api
 pnpm install
 ```
 
+If you do not have the database setup, run migrations from the monorepo root:
+```bash
+pnpm db:migrate
+```
+
 
 ### Environment Variables
 ```env

package/dist/index.cjs

@@ -769,6 +769,7 @@ async function handleMessageSend(c, agent, request) {
       id: task.id,
       tenantId: agent.tenantId,
       projectId: agent.projectId,
+      graphId: graphId || "",
       contextId: effectiveContextId,
       status: "working",
       metadata: {
@@ -6090,7 +6091,7 @@ ${propertiesXml}
 };
 
 // templates/v1/phase2/system-prompt.xml?raw
-var system_prompt_default2 = "<phase2_system_message>\n  <instruction>\n    Generate the final structured JSON response using the configured data components and artifact creation capabilities.\n  </instruction>\n\n  {{ARTIFACTS_SECTION}}\n  {{DATA_COMPONENTS_SECTION}}\n\n  {{ARTIFACT_GUIDANCE_SECTION}}\n\n  {{ARTIFACT_TYPES_SECTION}}\n\n  <requirements>\n    <key_requirements>\n      - Create artifacts from tool results to support your information with citations\n      - Mix artifact creation and references naturally throughout your dataComponents array\n      - Each artifact creation must use EXACT tool_call_id from tool outputs\n      - Use appropriate ArtifactCreate_[Type] components for each artifact type\n      - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details\n    </key_requirements>\n  </requirements>\n</phase2_system_message>";
+var system_prompt_default2 = "<phase2_system_message>\n  <instruction>\n    Generate the final structured JSON response using the configured data components and artifact creation capabilities.\n  </instruction>\n\n  <core_instructions>\n    {{CORE_INSTRUCTIONS}}\n  </core_instructions>\n\n  {{ARTIFACTS_SECTION}}\n  {{DATA_COMPONENTS_SECTION}}\n\n  {{ARTIFACT_GUIDANCE_SECTION}}\n\n  {{ARTIFACT_TYPES_SECTION}}\n\n  <requirements>\n    <key_requirements>\n      - Create artifacts from tool results to support your information with citations\n      - Mix artifact creation and references naturally throughout your dataComponents array\n      - Each artifact creation must use EXACT tool_call_id from tool outputs\n      - Use appropriate ArtifactCreate_[Type] components for each artifact type\n      - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details\n    </key_requirements>\n  </requirements>\n</phase2_system_message>";
 
 // templates/v1/phase2/data-components.xml?raw
 var data_components_default = '<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.\n\n***MANDATORY JSON RESPONSE FORMAT - ABSOLUTELY CRITICAL***:\n- WHEN DATA COMPONENTS ARE AVAILABLE, YOU MUST RESPOND IN JSON FORMAT ONLY\n- DO NOT respond with plain text when data components are defined\n- YOUR RESPONSE MUST BE STRUCTURED JSON WITH dataComponents ARRAY\n- THIS IS NON-NEGOTIABLE - JSON FORMAT IS REQUIRED\n\nCRITICAL JSON FORMATTING RULES - MUST FOLLOW EXACTLY:\n1. Each data component must include id, name, and props fields\n2. The id and name should match the exact component definition\n3. The props field contains the actual component data using exact property names from the schema\n4. NEVER omit the id and name fields\n\nCORRECT: [{\\"id\\": \\"component1\\", \\"name\\": \\"Component1\\", \\"props\\": {\\"field1\\": \\"value1\\", \\"field2\\": \\"value2\\"}}, {\\"id\\": \\"component2\\", \\"name\\": \\"Component2\\", \\"props\\": {\\"field3\\": \\"value3\\"}}]\nWRONG: [{\\"field1\\": \\"value1\\", \\"field2\\": \\"value2\\"}, {\\"field3\\": \\"value3\\"}]\n\nAVAILABLE DATA COMPONENTS: {{DATA_COMPONENTS_LIST}}">\n\n{{DATA_COMPONENTS_XML}}\n\n</data_components_section>';
@@ -6422,7 +6423,7 @@ ${artifact_retrieval_guidance_default}
    * Assemble the complete Phase 2 system prompt for structured output generation
    */
   assemblePhase2Prompt(config) {
-    const { dataComponents, artifactComponents, hasArtifactComponents, hasGraphArtifactComponents, artifacts = [] } = config;
+    const { corePrompt, dataComponents, artifactComponents, hasArtifactComponents, hasGraphArtifactComponents, artifacts = [] } = config;
     let allDataComponents = [...dataComponents];
     if (hasArtifactComponents && artifactComponents) {
       const artifactCreateComponents = ArtifactCreateSchema.getDataComponents(
@@ -6440,6 +6441,7 @@ ${artifact_retrieval_guidance_default}
     const artifactGuidance = this.getStructuredArtifactGuidance(hasArtifactComponents, artifactComponents, shouldShowReferencingRules);
     const artifactTypes = this.getArtifactCreationInstructions(hasArtifactComponents, artifactComponents);
     let phase2Prompt = system_prompt_default2;
+    phase2Prompt = phase2Prompt.replace("{{CORE_INSTRUCTIONS}}", corePrompt);
     phase2Prompt = phase2Prompt.replace("{{DATA_COMPONENTS_SECTION}}", dataComponentsSection);
     phase2Prompt = phase2Prompt.replace("{{ARTIFACTS_SECTION}}", artifactsSection);
     phase2Prompt = phase2Prompt.replace("{{ARTIFACT_GUIDANCE_SECTION}}", artifactGuidance);
@@ -7020,9 +7022,29 @@ var Agent = class {
    * Build adaptive system prompt for Phase 2 structured output generation
    * based on configured data components and artifact components across the graph
    */
-  async buildPhase2SystemPrompt() {
+  async buildPhase2SystemPrompt(runtimeContext) {
     const phase2Config = new Phase2Config();
     const hasGraphArtifactComponents = await this.hasGraphArtifactComponents();
+    const conversationId = runtimeContext?.metadata?.conversationId || runtimeContext?.contextId;
+    const resolvedContext = conversationId ? await this.getResolvedContext(conversationId) : null;
+    let processedPrompt = this.config.agentPrompt;
+    if (resolvedContext) {
+      try {
+        processedPrompt = agentsCore.TemplateEngine.render(this.config.agentPrompt, resolvedContext, {
+          strict: false,
+          preserveUnresolved: false
+        });
+      } catch (error) {
+        logger15.error(
+          {
+            conversationId,
+            error: error instanceof Error ? error.message : "Unknown error"
+          },
+          "Failed to process agent prompt with context for Phase 2, using original"
+        );
+        processedPrompt = this.config.agentPrompt;
+      }
+    }
     const referenceTaskIds = await agentsCore.listTaskIdsByContextId(dbClient_default)({
       contextId: this.conversationId || ""
     });
@@ -7038,6 +7060,7 @@ var Agent = class {
       referenceArtifacts.push(...artifacts);
     }
     return phase2Config.assemblePhase2Prompt({
+      corePrompt: processedPrompt,
       dataComponents: this.config.dataComponents || [],
       artifactComponents: this.artifactComponents,
       hasArtifactComponents: this.artifactComponents && this.artifactComponents.length > 0,
@@ -7767,16 +7790,20 @@ ${output}${structureHintsFormatted}`;
             const phase2TimeoutMs = structuredModelSettings.maxDuration ? structuredModelSettings.maxDuration * 1e3 : CONSTANTS.PHASE_2_TIMEOUT_MS;
             const shouldStreamPhase2 = this.getStreamingHelper();
             if (shouldStreamPhase2) {
+              const phase2Messages = [
+                {
+                  role: "system",
+                  content: await this.buildPhase2SystemPrompt(runtimeContext)
+                }
+              ];
+              if (conversationHistory.trim() !== "") {
+                phase2Messages.push({ role: "user", content: conversationHistory });
+              }
+              phase2Messages.push({ role: "user", content: userMessage });
+              phase2Messages.push(...reasoningFlow);
               const streamResult = ai.streamObject({
                 ...structuredModelSettings,
-                messages: [
-                  {
-                    role: "system",
-                    content: await this.buildPhase2SystemPrompt()
-                  },
-                  { role: "user", content: userMessage },
-                  ...reasoningFlow
-                ],
+                messages: phase2Messages,
                 schema: z5.z.object({
                   dataComponents: z5.z.array(dataComponentsSchema)
                 }),
@@ -7834,14 +7861,18 @@ ${output}${structureHintsFormatted}`;
               textResponse = JSON.stringify(structuredResponse.object, null, 2);
             } else {
               const { withJsonPostProcessing: withJsonPostProcessing2 } = await Promise.resolve().then(() => (init_json_postprocessor(), json_postprocessor_exports));
+              const phase2Messages = [
+                { role: "system", content: await this.buildPhase2SystemPrompt(runtimeContext) }
+              ];
+              if (conversationHistory.trim() !== "") {
+                phase2Messages.push({ role: "user", content: conversationHistory });
+              }
+              phase2Messages.push({ role: "user", content: userMessage });
+              phase2Messages.push(...reasoningFlow);
               const structuredResponse = await ai.generateObject(
                 withJsonPostProcessing2({
                   ...structuredModelSettings,
-                  messages: [
-                    { role: "system", content: await this.buildPhase2SystemPrompt() },
-                    { role: "user", content: userMessage },
-                    ...reasoningFlow
-                  ],
+                  messages: phase2Messages,
                   schema: z5.z.object({
                     dataComponents: z5.z.array(dataComponentsSchema)
                   }),
@@ -9186,6 +9217,7 @@ var ExecutionHandler = class {
           id: taskId,
           tenantId,
           projectId,
+          graphId,
           agentId: currentAgentId,
           contextId: conversationId,
           status: "pending",

package/dist/index.js

@@ -346,6 +346,7 @@ async function handleMessageSend(c, agent, request) {
       id: task.id,
       tenantId: agent.tenantId,
       projectId: agent.projectId,
+      graphId: graphId || "",
       contextId: effectiveContextId,
       status: "working",
       metadata: {
@@ -5623,7 +5624,7 @@ ${propertiesXml}
 };
 
 // templates/v1/phase2/system-prompt.xml?raw
-var system_prompt_default2 = "<phase2_system_message>\n  <instruction>\n    Generate the final structured JSON response using the configured data components and artifact creation capabilities.\n  </instruction>\n\n  {{ARTIFACTS_SECTION}}\n  {{DATA_COMPONENTS_SECTION}}\n\n  {{ARTIFACT_GUIDANCE_SECTION}}\n\n  {{ARTIFACT_TYPES_SECTION}}\n\n  <requirements>\n    <key_requirements>\n      - Create artifacts from tool results to support your information with citations\n      - Mix artifact creation and references naturally throughout your dataComponents array\n      - Each artifact creation must use EXACT tool_call_id from tool outputs\n      - Use appropriate ArtifactCreate_[Type] components for each artifact type\n      - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details\n    </key_requirements>\n  </requirements>\n</phase2_system_message>";
+var system_prompt_default2 = "<phase2_system_message>\n  <instruction>\n    Generate the final structured JSON response using the configured data components and artifact creation capabilities.\n  </instruction>\n\n  <core_instructions>\n    {{CORE_INSTRUCTIONS}}\n  </core_instructions>\n\n  {{ARTIFACTS_SECTION}}\n  {{DATA_COMPONENTS_SECTION}}\n\n  {{ARTIFACT_GUIDANCE_SECTION}}\n\n  {{ARTIFACT_TYPES_SECTION}}\n\n  <requirements>\n    <key_requirements>\n      - Create artifacts from tool results to support your information with citations\n      - Mix artifact creation and references naturally throughout your dataComponents array\n      - Each artifact creation must use EXACT tool_call_id from tool outputs\n      - Use appropriate ArtifactCreate_[Type] components for each artifact type\n      - IMPORTANT: In Text components, write naturally as if having a conversation - do NOT mention components, schemas, JSON, structured data, or any technical implementation details\n    </key_requirements>\n  </requirements>\n</phase2_system_message>";
 
 // templates/v1/phase2/data-components.xml?raw
 var data_components_default = '<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.\n\n***MANDATORY JSON RESPONSE FORMAT - ABSOLUTELY CRITICAL***:\n- WHEN DATA COMPONENTS ARE AVAILABLE, YOU MUST RESPOND IN JSON FORMAT ONLY\n- DO NOT respond with plain text when data components are defined\n- YOUR RESPONSE MUST BE STRUCTURED JSON WITH dataComponents ARRAY\n- THIS IS NON-NEGOTIABLE - JSON FORMAT IS REQUIRED\n\nCRITICAL JSON FORMATTING RULES - MUST FOLLOW EXACTLY:\n1. Each data component must include id, name, and props fields\n2. The id and name should match the exact component definition\n3. The props field contains the actual component data using exact property names from the schema\n4. NEVER omit the id and name fields\n\nCORRECT: [{\\"id\\": \\"component1\\", \\"name\\": \\"Component1\\", \\"props\\": {\\"field1\\": \\"value1\\", \\"field2\\": \\"value2\\"}}, {\\"id\\": \\"component2\\", \\"name\\": \\"Component2\\", \\"props\\": {\\"field3\\": \\"value3\\"}}]\nWRONG: [{\\"field1\\": \\"value1\\", \\"field2\\": \\"value2\\"}, {\\"field3\\": \\"value3\\"}]\n\nAVAILABLE DATA COMPONENTS: {{DATA_COMPONENTS_LIST}}">\n\n{{DATA_COMPONENTS_XML}}\n\n</data_components_section>';
@@ -5955,7 +5956,7 @@ ${artifact_retrieval_guidance_default}
    * Assemble the complete Phase 2 system prompt for structured output generation
    */
   assemblePhase2Prompt(config) {
-    const { dataComponents, artifactComponents, hasArtifactComponents, hasGraphArtifactComponents, artifacts = [] } = config;
+    const { corePrompt, dataComponents, artifactComponents, hasArtifactComponents, hasGraphArtifactComponents, artifacts = [] } = config;
     let allDataComponents = [...dataComponents];
     if (hasArtifactComponents && artifactComponents) {
       const artifactCreateComponents = ArtifactCreateSchema.getDataComponents(
@@ -5973,6 +5974,7 @@ ${artifact_retrieval_guidance_default}
     const artifactGuidance = this.getStructuredArtifactGuidance(hasArtifactComponents, artifactComponents, shouldShowReferencingRules);
     const artifactTypes = this.getArtifactCreationInstructions(hasArtifactComponents, artifactComponents);
     let phase2Prompt = system_prompt_default2;
+    phase2Prompt = phase2Prompt.replace("{{CORE_INSTRUCTIONS}}", corePrompt);
     phase2Prompt = phase2Prompt.replace("{{DATA_COMPONENTS_SECTION}}", dataComponentsSection);
     phase2Prompt = phase2Prompt.replace("{{ARTIFACTS_SECTION}}", artifactsSection);
     phase2Prompt = phase2Prompt.replace("{{ARTIFACT_GUIDANCE_SECTION}}", artifactGuidance);
@@ -6553,9 +6555,29 @@ var Agent = class {
    * Build adaptive system prompt for Phase 2 structured output generation
    * based on configured data components and artifact components across the graph
    */
-  async buildPhase2SystemPrompt() {
+  async buildPhase2SystemPrompt(runtimeContext) {
     const phase2Config = new Phase2Config();
     const hasGraphArtifactComponents = await this.hasGraphArtifactComponents();
+    const conversationId = runtimeContext?.metadata?.conversationId || runtimeContext?.contextId;
+    const resolvedContext = conversationId ? await this.getResolvedContext(conversationId) : null;
+    let processedPrompt = this.config.agentPrompt;
+    if (resolvedContext) {
+      try {
+        processedPrompt = TemplateEngine.render(this.config.agentPrompt, resolvedContext, {
+          strict: false,
+          preserveUnresolved: false
+        });
+      } catch (error) {
+        logger15.error(
+          {
+            conversationId,
+            error: error instanceof Error ? error.message : "Unknown error"
+          },
+          "Failed to process agent prompt with context for Phase 2, using original"
+        );
+        processedPrompt = this.config.agentPrompt;
+      }
+    }
     const referenceTaskIds = await listTaskIdsByContextId(dbClient_default)({
       contextId: this.conversationId || ""
     });
@@ -6571,6 +6593,7 @@ var Agent = class {
       referenceArtifacts.push(...artifacts);
     }
     return phase2Config.assemblePhase2Prompt({
+      corePrompt: processedPrompt,
       dataComponents: this.config.dataComponents || [],
       artifactComponents: this.artifactComponents,
       hasArtifactComponents: this.artifactComponents && this.artifactComponents.length > 0,
@@ -7300,16 +7323,20 @@ ${output}${structureHintsFormatted}`;
             const phase2TimeoutMs = structuredModelSettings.maxDuration ? structuredModelSettings.maxDuration * 1e3 : CONSTANTS.PHASE_2_TIMEOUT_MS;
             const shouldStreamPhase2 = this.getStreamingHelper();
             if (shouldStreamPhase2) {
+              const phase2Messages = [
+                {
+                  role: "system",
+                  content: await this.buildPhase2SystemPrompt(runtimeContext)
+                }
+              ];
+              if (conversationHistory.trim() !== "") {
+                phase2Messages.push({ role: "user", content: conversationHistory });
+              }
+              phase2Messages.push({ role: "user", content: userMessage });
+              phase2Messages.push(...reasoningFlow);
               const streamResult = streamObject({
                 ...structuredModelSettings,
-                messages: [
-                  {
-                    role: "system",
-                    content: await this.buildPhase2SystemPrompt()
-                  },
-                  { role: "user", content: userMessage },
-                  ...reasoningFlow
-                ],
+                messages: phase2Messages,
                 schema: z.object({
                   dataComponents: z.array(dataComponentsSchema)
                 }),
@@ -7367,14 +7394,18 @@ ${output}${structureHintsFormatted}`;
               textResponse = JSON.stringify(structuredResponse.object, null, 2);
             } else {
               const { withJsonPostProcessing } = await import('./json-postprocessor-VOMU4E5L.js');
+              const phase2Messages = [
+                { role: "system", content: await this.buildPhase2SystemPrompt(runtimeContext) }
+              ];
+              if (conversationHistory.trim() !== "") {
+                phase2Messages.push({ role: "user", content: conversationHistory });
+              }
+              phase2Messages.push({ role: "user", content: userMessage });
+              phase2Messages.push(...reasoningFlow);
               const structuredResponse = await generateObject(
                 withJsonPostProcessing({
                   ...structuredModelSettings,
-                  messages: [
-                    { role: "system", content: await this.buildPhase2SystemPrompt() },
-                    { role: "user", content: userMessage },
-                    ...reasoningFlow
-                  ],
+                  messages: phase2Messages,
                   schema: z.object({
                     dataComponents: z.array(dataComponentsSchema)
                   }),
@@ -8705,6 +8736,7 @@ var ExecutionHandler = class {
           id: taskId,
           tenantId,
           projectId,
+          graphId,
           agentId: currentAgentId,
           contextId: conversationId,
           status: "pending",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inkeep/agents-run-api",
-  "version": "0.10.1",
+  "version": "0.11.0",
   "description": "Agents Run API for Inkeep Agent Framework - handles chat, agent execution, and streaming",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -51,7 +51,7 @@
     "traverse": "^0.6.11",
     "ts-pattern": "^5.7.1",
     "zod": "^4.1.5",
-    "@inkeep/agents-core": "^0.10.1"
+    "@inkeep/agents-core": "^0.11.0"
   },
   "optionalDependencies": {
     "keytar": "^7.9.0"

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

@@ -3,6 +3,10 @@
     Generate the final structured JSON response using the configured data components and artifact creation capabilities.
   </instruction>
 
+  <core_instructions>
+    {{CORE_INSTRUCTIONS}}
+  </core_instructions>
+
   {{ARTIFACTS_SECTION}}
   {{DATA_COMPONENTS_SECTION}}