@aj-archipelago/cortex 1.4.2 → 1.4.4

package/helper-apps/cortex-file-handler/tests/containerParameterFlow.test.js

@@ -71,11 +71,14 @@ test.after.always(async (t) => {
 
 // Test container parameter validation
 test("should validate container names correctly", (t) => {
+  // Get current container names
+  const currentContainers = AZURE_STORAGE_CONTAINER_NAMES;
+  
   // Test with valid container names from configuration
-  AZURE_STORAGE_CONTAINER_NAMES.forEach(containerName => {
+  currentContainers.forEach(containerName => {
     t.true(isValidContainerName(containerName), `${containerName} should be valid`);
   });
-
+  
   // Test with invalid container names
   const invalidNames = ["invalid-container", "", null, undefined, "nonexistent"];
   invalidNames.forEach(name => {

package/helper-apps/cortex-file-handler/tests/storage/StorageFactory.test.js

@@ -123,19 +123,27 @@ test("should get azure provider with specific container name", async (t) => {
     return;
   }
 
-  const factory = new StorageFactory();
-  
-  // Mock the blobHandler constants for this test
-  const mockConstants = {
-    AZURE_STORAGE_CONTAINER_NAMES: ["container1", "container2", "container3"],
-    DEFAULT_AZURE_STORAGE_CONTAINER_NAME: "container1",
-    isValidContainerName: (name) => ["container1", "container2", "container3"].includes(name)
-  };
+  // Save original env value
+  const originalEnv = process.env.AZURE_STORAGE_CONTAINER_NAME;
   
-  // Test with valid container name
-  const provider = await factory.getAzureProvider("container2");
-  t.truthy(provider);
-  t.is(provider.containerName, "container2");
+  try {
+    // Set test container names in environment
+    process.env.AZURE_STORAGE_CONTAINER_NAME = "container1,container2,container3";
+    
+    const factory = new StorageFactory();
+    
+    // Test with valid container name
+    const provider = await factory.getAzureProvider("container2");
+    t.truthy(provider);
+    t.is(provider.containerName, "container2");
+  } finally {
+    // Restore original env
+    if (originalEnv) {
+      process.env.AZURE_STORAGE_CONTAINER_NAME = originalEnv;
+    } else {
+      delete process.env.AZURE_STORAGE_CONTAINER_NAME;
+    }
+  }
 });
 
 test("should throw error for invalid container name", async (t) => {
@@ -159,21 +167,25 @@ test("should cache providers by container name", async (t) => {
     return;
   }
 
-  const factory = new StorageFactory();
-  
-  // Mock valid container names for testing
+  // Save original env value
   const originalEnv = process.env.AZURE_STORAGE_CONTAINER_NAME;
-  process.env.AZURE_STORAGE_CONTAINER_NAME = "test1,test2,test3";
   
   try {
-    const provider1 = await factory.getAzureProvider("test1");
-    const provider2 = await factory.getAzureProvider("test1");
-    const provider3 = await factory.getAzureProvider("test2");
+    // Set test container names in environment
+    process.env.AZURE_STORAGE_CONTAINER_NAME = "container1,container2,container3";
+    
+    const factory = new StorageFactory();
+    
+    const provider1 = await factory.getAzureProvider("container1");
+    const provider2 = await factory.getAzureProvider("container1");
+    const provider3 = await factory.getAzureProvider("container2");
     
     // Same container should return same instance
     t.is(provider1, provider2);
     // Different container should return different instance
     t.not(provider1, provider3);
+    t.is(provider1.containerName, "container1");
+    t.is(provider3.containerName, "container2");
   } finally {
     // Restore original env
     if (originalEnv) {

package/lib/entityConstants.js

@@ -26,6 +26,7 @@ Your responses should be in {{language}} unless the user has expressed another p
 - 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.
+- For data processing requests (e.g. tell me how many articles were published in the last 30 days), or deep file analysis (chart the trends in this spreadsheet, etc.), you should call your code execution tool to perform the task - especially if the task requires a lot of data, deep analysis, complex filtering, or precision calculations. For simpler things (e.g. make me a chart of the population of the world in the last 100 years) you might find it faster to search for the data and then just call your charting tool to generate the chart.
 - You must always search if you are being asked questions about current events, news, fact-checking, or information requiring citation.
 - Do not make up information - if information cannot be confirmed with rigorous logic or reliable sources, do not include it in your response.
 - Start searches broad and consult multiple sources, running all searches in parallel to save time.
@@ -123,6 +124,8 @@ Privacy is critical. If asked to forget or delete something, always comply affir
 
     AI_STYLE_OPENAI: "oai-gpt5-chat",
     AI_STYLE_OPENAI_RESEARCH: "oai-gpt5",
+    AI_STYLE_OPENAI_LEGACY: "oai-gpt41",
+    AI_STYLE_OPENAI_LEGACY_RESEARCH: "oai-o3",
     AI_STYLE_ANTHROPIC: "claude-4-sonnet-vertex",
     AI_STYLE_ANTHROPIC_RESEARCH: "claude-41-opus-vertex",
     AI_STYLE_XAI: "xai-grok-4-fast-reasoning",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aj-archipelago/cortex",
-  "version": "1.4.2",
+  "version": "1.4.4",
   "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": {
@@ -33,7 +33,7 @@
   "type": "module",
   "homepage": "https://github.com/aj-archipelago/cortex#readme",
   "dependencies": {
-    "@aj-archipelago/merval": "^1.0.2",
+    "@aj-archipelago/merval": "^1.0.3",
     "@aj-archipelago/subvibe": "^1.0.12",
     "@apollo/server": "^4.7.3",
     "@apollo/server-plugin-response-cache": "^4.1.2",

package/pathways/system/entity/sys_entity_agent.js

@@ -333,12 +333,13 @@ export default {
         ];
 
         // set the style model if applicable
-        const { aiStyle, AI_STYLE_ANTHROPIC, AI_STYLE_OPENAI, AI_STYLE_ANTHROPIC_RESEARCH, AI_STYLE_OPENAI_RESEARCH, AI_STYLE_XAI, AI_STYLE_XAI_RESEARCH, AI_STYLE_GOOGLE, AI_STYLE_GOOGLE_RESEARCH } = args;
+        const { aiStyle, AI_STYLE_ANTHROPIC, AI_STYLE_OPENAI, AI_STYLE_ANTHROPIC_RESEARCH, AI_STYLE_OPENAI_RESEARCH, AI_STYLE_OPENAI_LEGACY, AI_STYLE_OPENAI_LEGACY_RESEARCH, AI_STYLE_XAI, AI_STYLE_XAI_RESEARCH, AI_STYLE_GOOGLE, AI_STYLE_GOOGLE_RESEARCH } = args;
 
         // Create a mapping of AI styles to their corresponding models
         const styleModelMap = {
             "Anthropic": { normal: AI_STYLE_ANTHROPIC, research: AI_STYLE_ANTHROPIC_RESEARCH },
             "OpenAI": { normal: AI_STYLE_OPENAI, research: AI_STYLE_OPENAI_RESEARCH },
+            "OpenAI_Legacy": { normal: AI_STYLE_OPENAI_LEGACY, research: AI_STYLE_OPENAI_LEGACY_RESEARCH },
             "XAI": { normal: AI_STYLE_XAI, research: AI_STYLE_XAI_RESEARCH },
             "Google": { normal: AI_STYLE_GOOGLE, research: AI_STYLE_GOOGLE_RESEARCH }
         };

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

@@ -48,7 +48,7 @@ export default {
         icon: "🤖",
         function: {
             name: "CodeExecution",
-            description: "This tool allows you to engage an agent to write and execute code to perform a task on your behalf. Use when explicitly asked to run or execute code, or when a coding agent is needed to perform specific tasks - examples include data analysis, file manipulation, or other tasks that require code execution. With this tool you can also access internal databases and query them directly. This will start a background task and return - you will not receive the response immediately.",
+            description: "This tool allows you to asynchronously engage an agent to write and execute code to perform a task on your behalf. Use when explicitly asked to run or execute code, or when a coding agent is needed to perform specific tasks - examples include data analysis, file manipulation, or other tasks that require code execution. With this tool you can read and write files and also access internal databases and query them directly. This will start a background task and return - you will not receive the response immediately.",
             parameters: {
                 type: "object",
                 properties: {
@@ -66,7 +66,7 @@ export default {
                     },
                     codingTaskKeywords: {
                         type: "string",
-                        description: "Keywords for Azure Cognitive Search to help the coding agent find relevant code snippets"
+                        description: "Keywords for the coding agent's internal Azure Cognitive Search index to help the coding agent find relevant code snippets"
                     }
                 },
                 required: ["codingTask", "userMessage", "codingTaskKeywords"]