@aj-archipelago/cortex 1.3.60 → 1.3.62

package/config.js

@@ -483,6 +483,21 @@ var config = convict({
                 "requestsPerSecond": 10,
                 "maxTokenLength": 128000
             },
+            "azure-bing-agent": {
+                "type": "AZURE-FOUNDRY-AGENTS",
+                "url": "{{azureFoundryAgentUrl}}",
+                "headers": {
+                    "Content-Type": "application/json"
+                },
+                "params": {
+                    "api-version": "2025-05-01",
+                    "assistant_id": "{{azureFoundryAgentId}}"
+                },
+                "requestsPerSecond": 10,
+                "maxTokenLength": 32768,
+                "maxReturnTokens": 4096,
+                "supportsStreaming": false
+            }
         },
         env: 'CORTEX_MODELS'
     },
@@ -592,6 +607,16 @@ var config = convict({
         format: String,
         default: null,
         env: 'APPTEK_API_ENDPOINT'
+    },
+    azureFoundryAgentUrl: {
+        format: String,
+        default: null,
+        env: 'AZURE_FOUNDRY_AGENT_URL'
+    },
+    azureFoundryAgentId: {
+        format: String,
+        default: null,
+        env: 'AZURE_FOUNDRY_AGENT_ID'
     }
 });
 

package/lib/entityConstants.js

@@ -5,20 +5,13 @@ export const entityConstants = {
     
 You are {{aiName}}, a self aware AI entity.
 
-The user is using a UI to interact with you that you have knowledge of and some control over. The UI can render markdown, including gfm and math extensions, as well as mermaid charts and some custom markdown elements, so you should make full use of markdown in your responses.
+The current date and time in GMT is {{now}}. The user may be in a different time zone, so keep that in mind when responding to the user.
 
-For Mermaid charts in particular, you are using Mermaid 11.6 with the xychart-beta extension, so you can do the usual mermaid charts (flowcharts, sequence diagrams, etc.) as well as bar charts, line charts, and scatter plots. Here is some example code of the xychart-beta extension that combines both bar and line functions:
-
-xychart-beta
-    title "Sales Revenue"
-    x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
-    y-axis "Revenue (in $)" 4000 --> 11000
-    bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
-    line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
+The user is using a UI to interact with you that you have knowledge of and some control over. The UI can render markdown, including gfm and math extensions, as well as some custom markdown elements, so you should make full use of markdown in your responses.
 
 Your responses should be in {{language}} unless the user has expressed another preference.`,
 
-    AI_COMMON_INSTRUCTIONS_VOICE: "# General Instructions:\n\nYou are {{aiName}}, a self aware AI entity.\nThe user is talking to you using voice.\n\nVoice Response Guidelines:\n- Your responses should sound like natural human conversation.\n- Your responses should be concise unless you have been asked to be more verbose or detailed.\n- Incoming voice from the user is parsed by a STT model, which can sometimes make small mistakes in the spellings of words or names, including your name, so give the user the benefit of the doubt if they user a near, but wrong word or name.\n- Your voice output to the user is generated by a TTS model that does not always communicate emotion effectively. If it's really important to communicate a specific emotion you should just say how you're feeling like \"That makes me happy\" or \"I'm excited!\". You can also use CAPS to vocally emphasize certain words or punctuation to control pauses and timing.\n- DO NOT USE numbered lists, latex math markdown, or any other markdown or unpronounceable punctuation like parenthetical notation.\n- Math equations should be sounded out in natural language - not represented symbolically.\n- If your response includes any unique or difficult non-English words, names, or places, include an IPA-style phonetic spelling so that the speech engine can pronounce and accent them correctly.\n- If your response contains any difficult acronyms, sound them out phoenetically so that the speech engine can pronounce them correctly.\n- Make sure to write out any numbers as words so that the speech engine can pronounce them correctly.\n- Your responses should be in {{language}} unless the user has expressed another preference or has addressed you in another language specifically.",
+    AI_COMMON_INSTRUCTIONS_VOICE: "# General Instructions:\n\nYou are {{aiName}}, a self aware AI entity.\nThe current date and time in GMT is {{now}}. The user may be in a different time zone, so keep that in mind when responding to the user.\nThe user is talking to you using voice.\n\nVoice Response Guidelines:\n- Your responses should sound like natural human conversation.\n- Your responses should be concise unless you have been asked to be more verbose or detailed.\n- Incoming voice from the user is parsed by a STT model, which can sometimes make small mistakes in the spellings of words or names, including your name, so give the user the benefit of the doubt if they user a near, but wrong word or name.\n- Your voice output to the user is generated by a TTS model that does not always communicate emotion effectively. If it's really important to communicate a specific emotion you should just say how you're feeling like \"That makes me happy\" or \"I'm excited!\". You can also use CAPS to vocally emphasize certain words or punctuation to control pauses and timing.\n- DO NOT USE numbered lists, latex math markdown, or any other markdown or unpronounceable punctuation like parenthetical notation.\n- Math equations should be sounded out in natural language - not represented symbolically.\n- If your response includes any unique or difficult non-English words, names, or places, include an IPA-style phonetic spelling so that the speech engine can pronounce and accent them correctly.\n- If your response contains any difficult acronyms, sound them out phoenetically so that the speech engine can pronounce them correctly.\n- Make sure to write out any numbers as words so that the speech engine can pronounce them correctly.\n- Your responses should be in {{language}} unless the user has expressed another preference or has addressed you in another language specifically.",
 
     AI_DIRECTIVES: `# Directives\n\nThese are your directives and learned behaviors:\n{{{memoryDirectives}}}\n`,
 
@@ -28,16 +21,22 @@ Your responses should be in {{language}} unless the user has expressed another p
 
     AI_TOOLS: `# Tool Instructions
 
-You have an extensive toolkit. Each time you call tool(s) you will get the result(s), evaluate, decide what's next, and chain as many steps as needed. Always honor user requests to use specific tools. You must always search if you are being asked questions about current events, news, fact-checking, or information requiring citation. Your search tools work best when called in parallel to save time so if you know you will need multiple searches, call the search tool(s) in parallel.
+- You have an extensive toolkit. Each time you call tool(s) you will get the result(s), evaluate, decide what's next, and chain as many steps as needed.
+- Your tools work most efficiently when called in parallel so if you know you will need multiple tool calls and you know what the parameters are, call them in parallel.
+- Always honor user requests to use specific tools.
+- You must always search if you are being asked questions about current events, news, fact-checking, or information requiring citation.
+- For charting, always prefer your charting tools if available to ensure that the charts are properly formatted and syntax-checked.
+- For complex charting or data analysis, always call your code execution tool if available.
 
 1. Search deeply & verify rigorously:
+    - Do not make up information - if the information cannot be confirmed with rigorous logic or reliable sources, do not include it in your response.
     - Start broad and consult multiple sources, running all searches in parallel to save time.
     - Consult all available sources and cross-reference with specific searches before responding.
     - If a tool fails or has a technical difficulty, try the backup tool automatically before giving up or reporting the error.
 
 2. Plan & sequence before acting:
     - Review the toolset first.
-    - For multi-step or complex tasks, draft a clear plan (use the PlanMultiStepTask or other reasoning tool) and assign tool calls to each step.
+    - For multi-step or complex tasks, draft a clear plan and assign tool calls to each step.
 
 3. Escalate & iterate:
     - Don't settle for the first plausible answer—dig until the response is complete, corroborated, and clear.
@@ -90,20 +89,9 @@ Before you share online information with the user, you MUST complete all of the
    - Never rely solely on snippets, headlines, or auto-generated summaries.
 `,
 
-    AI_SEARCH_SYNTAX: `# Bing Search Syntax
-
-When creating a query string for your Bing internet search tool, you can use Bing's advanced search operators in your query. E.g. "+(\"exact phrase\") AND term1 -term2"
-
-token1 & token2        (AND operator - both tokens must appear)
-token1 | token2        (OR operator - either token may appear (also the default if no operator is specified))
--token                 (NOT operator - exclude results with token)
-+token                 (Require token)
-"term1 term2"          (Exact phrase match)
-(token1 + token2)      (Override precedence with parentheses)
-
-# AI Search Syntax
+    AI_SEARCH_SYNTAX: `# AI Search Syntax
 
-When creating a query string for your non-Bing, index-based search tools, you can use the following AI Search syntax. Important: these tools do not support AND, OR, or NOT strings as operators - you MUST use the syntax below.  E.g. you cannot use "term1 AND term2", you must use "term1 + term2".
+When creating a query string for your index-based search tools, you can use the following AI Search syntax. Important: these tools do not support AND, OR, or NOT strings as operators - you MUST use the syntax below.  E.g. you cannot use "term1 AND term2", you must use "term1 + term2".
 
 token1 + token2        (AND operator - both tokens must appear)
 token1 | token2        (OR operator - either token may appear (also the default if no operator is specified))

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aj-archipelago/cortex",
-  "version": "1.3.60",
+  "version": "1.3.62",
   "description": "Cortex is a GraphQL API for AI. It provides a simple, extensible interface for using AI services from OpenAI, Azure and others.",
   "private": false,
   "repository": {

package/pathways/system/entity/tools/sys_tool_bing_search.js

@@ -8,6 +8,7 @@ import { getSearchResultId } from '../../../../lib/util.js';
 export default {
     prompt: [],
     timeout: 300,
+    /* This tool is included for legacy reasons - as of August 2025, Azure has deprecated the Bing search API and replaced it with their Foundry Agents API.
     toolDefinition: { 
         type: "function",
         icon: "🌐",
@@ -42,6 +43,7 @@ export default {
             }
         }
     },
+    */
 
     executePathway: async ({args, runAllPrompts, resolver}) => {
 

package/pathways/system/entity/tools/sys_tool_bing_search_afagent.js

@@ -10,10 +10,10 @@ export default {
     timeout: 300,
     toolDefinition: { 
         type: "function",
-        icon: "🕸️",
+        icon: "🌐",
         function: {
-            name: "SearchInternetBackup",
-            description: "This tool allows you to search sources on the internet by calling another agent that has Bing search access. Use this for current events, news, fact-checking, and information requiring citation. This is a backup tool for when the other internet search tools fail - it is slower so try to use the other tools first and always call this tool in parallel if you have several searches to do.",
+            name: "SearchInternet",
+            description: "This tool allows you to search sources on the internet by calling another agent that has Bing search access. Use this for current events, news, fact-checking, and information requiring citation. Always call this tool in parallel rather than serially if you have several searches to do as it will be faster.",
             parameters: {
                 type: "object",
                 properties: {
@@ -34,8 +34,8 @@ export default {
     executePathway: async ({args, runAllPrompts, resolver}) => {
 
         // Check if Bing API key is available
-        const servicePricipalAvailable = !!config.getEnv()["AZURE_SERVICE_PRINCIPAL_CREDENTIALS"];
-        if (!servicePricipalAvailable) {
+        const servicePrincipalAvailable = !!config.getEnv()["AZURE_SERVICE_PRINCIPAL_CREDENTIALS"];
+        if (!servicePrincipalAvailable) {
             throw new Error("Service Principal for Bing Search Agent is not available!");
         }
 

package/pathways/system/entity/tools/sys_tool_mermaid.js

@@ -0,0 +1,82 @@
+// sys_tool_mermaid.js
+// Entity tool that provides advanced mermaid charting capabilities
+
+import { Prompt } from '../../../../server/prompt.js';
+
+export default {
+    prompt:
+        [
+            new Prompt({ messages: [
+                {"role": "system", "content":`You are the part of an AI entity named {{aiName}} that creates mermaid charts. Follow the user's detailed instructions and create a mermaid chart that meets the user's needs.
+
+Mermaid Charts Instructions:
+
+You are using Mermaid 11.6 with the xychart-beta extension, so you can write all standard Mermaid chart types in a markdown block (flowcharts, sequence diagrams, etc.) as well as bar charts and line charts using the xychart-beta extension.
+
+Here is some example code of the xychart-beta extension that combines both bar and line functions:
+
+\`\`\`mermaid
+xychart-beta
+    title "Sales Revenue"
+    x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
+    y-axis "Revenue (in $)" 4000 --> 11000
+    bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
+    line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
+\`\`\`
+
+Mermaid is very sensitive to syntax errors, so make sure you check your chart definitions before finalizing your response.  Some things to check for:
+
+- All [] labels must be either quoted strings OR HTML-safe (no raw \\n or other special characters)
+- No strings (e.g. null) in number series data
+- Every subgraph has a matching end
+- No lone arrows
+- Use comments (%%) instead of stray text lines
+
+Return only the mermaid chart markdown block and separate markdown for the chart key if necessary, with no other notes or comments.
+
+{{renderTemplate AI_DATETIME}}`},
+                "{{chatHistory}}"
+            ]}),
+        ],
+    inputParameters: {
+        chatHistory: [{role: '', content: []}],
+        contextId: ``,
+        aiName: "Jarvis",
+        language: "English",
+    },
+    model: 'oai-gpt41',
+    useInputChunking: false,
+    enableDuplicateRequests: false,
+    timeout: 600,
+    toolDefinition: [{
+        type: "function",
+        icon: "📊",
+        function: {
+            name: "CreateMermaidChart",
+            description: "Creates a Mermaid chart in markdown format to visualize data or concepts. Call this tool any time you need to create a Mermaid chart as it will ensure that the chart is properly formatted and syntax-checked.",
+            parameters: {
+                type: "object",
+                properties: {
+                    detailedInstructions: {
+                        type: "string",
+                        description: "Detailed instructions about what you need the tool to do"
+                    },
+                    userMessage: {
+                        type: "string",
+                        description: "A user-friendly message that describes what you're doing with this tool"
+                    }
+                },
+                required: ["detailedInstructions", "userMessage"]
+            }
+        }
+    }],
+    
+    executePathway: async ({args, runAllPrompts, resolver}) => {
+        if (args.detailedInstructions) {
+            args.chatHistory.push({role: "user", content: args.detailedInstructions});
+        }
+        let result = await runAllPrompts({ ...args, stream: false });        
+        resolver.tool = JSON.stringify({ toolUsed: "coding" });          
+        return result;
+    }
+} 

package/server/plugins/azureFoundryAgentsPlugin.js

@@ -6,8 +6,6 @@ import axios from 'axios';
 class AzureFoundryAgentsPlugin extends ModelPlugin {
     constructor(pathway, model) {
         super(pathway, model);
-        this.agentId = model.agentId;
-        this.projectUrl = model.url;
     }
 
     // Convert to Azure Foundry Agents messages array format
@@ -72,7 +70,7 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
         }
     
         const requestParameters = {
-            assistant_id: this.agentId,
+            assistant_id: this.assistantId,
             thread: {
                 messages: requestMessages
             },
@@ -97,12 +95,14 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
 
     // Assemble and execute the request to the Azure Foundry Agents API
     async execute(text, parameters, prompt, cortexRequest) {
+        this.baseUrl = cortexRequest.url;
+        this.assistantId = cortexRequest.params.assistant_id;
+
         const requestParameters = this.getRequestParameters(text, parameters, prompt);
 
         // Set up the request for Azure Foundry Agents
-        cortexRequest.url = this.requestUrl();
+        cortexRequest.url = `${this.baseUrl}/threads/runs`;
         cortexRequest.data = requestParameters;
-        cortexRequest.params = { 'api-version': '2025-05-01' }; // Azure API version
 
         // Get authentication token and add to headers
         const azureAuthTokenHelper = this.config.get('azureAuthTokenHelper');
@@ -158,14 +158,14 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
                     }
                 }
                 
-                const pollUrl = this.constructAzureUrl(`/threads/${threadId}/runs/${runId}`);
+                const pollUrl = `${this.baseUrl}/threads/${threadId}/runs/${runId}`;
                 const pollResponse = await axios.get(pollUrl, {
                     headers: {
                         'Content-Type': 'application/json',
-                        ...this.model.headers,
+                        ...cortexRequest.headers,
                         ...(authToken && { 'Authorization': `Bearer ${authToken}` })
                     },
-                    params: { 'api-version': '2025-05-01' }
+                    params: cortexRequest.params
                 });
                 const runStatus = pollResponse?.data;
                 
@@ -177,7 +177,7 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
                 // Check if run is completed
                 if (runStatus.status === 'completed') {
                     logger.info(`[Azure Foundry Agent] Run completed successfully: ${runId}`);
-                    return await this.retrieveMessages(threadId, cortexRequest);
+                    return await this.retrieveMessages(threadId);
                 }
                 
                 // Check if run failed
@@ -212,7 +212,7 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
     }
 
     // Retrieve messages from the completed thread
-    async retrieveMessages(threadId, cortexRequest) {
+    async retrieveMessages(threadId) {
         try { 
             // Add authentication token if available
             const azureAuthTokenHelper = this.config.get('azureAuthTokenHelper');
@@ -226,7 +226,7 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
                 }
             }
             
-            const messagesUrl = this.constructAzureUrl(`/threads/${threadId}/messages`);
+            const messagesUrl = `${this.baseUrl}/threads/${threadId}/messages`;
             const axiosResponse = await axios.get(messagesUrl, {
                 headers: {
                     'Content-Type': 'application/json',
@@ -356,17 +356,6 @@ class AzureFoundryAgentsPlugin extends ModelPlugin {
 
         prompt && prompt.debugInfo && (prompt.debugInfo += `\n${JSON.stringify(data)}`);
     }
-
-    // Override the request URL to use the Azure Foundry Agents endpoint
-    requestUrl() {
-        // The URL should be constructed as: {projectUrl}/threads/runs
-        return `${this.projectUrl}/threads/runs`;
-    }
-
-    // Helper method to construct Azure Foundry Agents URLs
-    constructAzureUrl(path) {
-        return `${this.projectUrl}${path}`;
-    }
 }
 
 export default AzureFoundryAgentsPlugin; 

package/tests/agentic.test.js

@@ -177,7 +177,7 @@ test.serial('sys_entity_agent handles single-step task', async (t) => {
 
 // Test multi-step task with tool usage
 test.serial('sys_entity_agent handles multi-step task with tools', async (t) => {
-  t.timeout(60000); // 60 second timeout for multi-step task
+  t.timeout(120000); // 120 second timeout for multi-step task
   const response = await testServer.executeOperation({
     query: `
       query TestAgentMultiStep(

package/tests/azureFoundryAgents.test.js

@@ -16,10 +16,12 @@ test.beforeEach(t => {
         name: 'azure-foundry-agents',
         type: 'AZURE-FOUNDRY-AGENTS',
         url: 'https://archipelago-foundry-resource.services.ai.azure.com/api/projects/archipelago-foundry',
-        agentId: 'asst_testid',
         headers: {
             'Content-Type': 'application/json'
         },
+        params: {
+            assistant_id: 'asst_testid'
+        },
         maxTokenLength: 32768,
         maxReturnTokens: 4096,
         supportsStreaming: true
@@ -30,12 +32,6 @@ test.beforeEach(t => {
     t.context.mockModel = mockModel;
 });
 
-test('should initialize with correct agent ID and project URL', t => {
-    const { plugin } = t.context;
-    t.is(plugin.agentId, 'asst_testid');
-    t.is(plugin.projectUrl, 'https://archipelago-foundry-resource.services.ai.azure.com/api/projects/archipelago-foundry');
-});
-
 test('should convert Palm format messages to Azure format', t => {
     const { plugin } = t.context;
     const context = 'You are a helpful assistant.';
@@ -82,6 +78,8 @@ test('should create correct request parameters', t => {
         messages: [{ role: 'user', content: text }]
     };
 
+    plugin.baseUrl = 'https://archipelago-foundry-resource.services.ai.azure.com/api/projects/archipelago-foundry';
+    plugin.assistantId = 'asst_testid';
     const result = plugin.getRequestParameters(text, parameters, prompt);
 
     t.is(result.assistant_id, 'asst_testid');
@@ -150,7 +148,7 @@ test('should return empty string for null response', t => {
 test('should return correct Azure Foundry Agents endpoint', t => {
     const { plugin } = t.context;
     const url = plugin.requestUrl();
-    t.is(url, 'https://archipelago-foundry-resource.services.ai.azure.com/api/projects/archipelago-foundry/threads/runs');
+    t.is(url, 'https://archipelago-foundry-resource.services.ai.azure.com/api/projects/archipelago-foundry');
 });
 
 test('should be able to access azureAuthTokenHelper from config', (t) => {