@arcgis/ai-agents 5.1.0-next.66 → 5.1.0-next.68

package/dist/agents/dataExploration/state/dataExplorationState.d.ts

@@ -1,9 +1,11 @@
-import { AgentExecutionContext, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext, AgentStatus, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
 import { QueryResponse } from '../types/types';
 import { LayerFieldInfo } from '../../../types/types';
 export declare const DataExplorationState: import('@langchain/langgraph/web').AnnotationRoot<{
     agentExecutionContext: import('@langchain/langgraph/web').BaseChannel<AgentExecutionContext, AgentExecutionContext | import('@langchain/langgraph/web').OverwriteValue<AgentExecutionContext>, unknown>;
     outputMessage: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    summary: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    status: import('@langchain/langgraph/web').BaseChannel<AgentStatus, AgentStatus | import('@langchain/langgraph/web').OverwriteValue<AgentStatus>, unknown>;
     vectorSearchLayerIds: import('@langchain/langgraph/web').LastValue<string[]>;
     vectorSearchFieldResults: import('@langchain/langgraph/web').LastValue<VectorSearchFieldResults>;
     layerFieldInfo: import('@langchain/langgraph/web').LastValue<LayerFieldInfo>;

package/dist/agents/help/state/helpState.d.ts

@@ -1,6 +1,8 @@
-import { AgentExecutionContext } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext, AgentStatus } from '@arcgis/ai-orchestrator';
 export declare const HelpState: import('@langchain/langgraph/web').AnnotationRoot<{
     agentExecutionContext: import('@langchain/langgraph/web').BaseChannel<AgentExecutionContext, AgentExecutionContext | import('@langchain/langgraph/web').OverwriteValue<AgentExecutionContext>, unknown>;
     outputMessage: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    summary: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    status: import('@langchain/langgraph/web').BaseChannel<AgentStatus, AgentStatus | import('@langchain/langgraph/web').OverwriteValue<AgentStatus>, unknown>;
 }>;
 export type HelpGraphStateType = typeof HelpState.State;

package/dist/agents/navigation/state/navigationState.d.ts

@@ -1,7 +1,9 @@
-import { VectorSearchFieldResults, AgentExecutionContext } from '@arcgis/ai-orchestrator';
+import { VectorSearchFieldResults, AgentExecutionContext, AgentStatus } from '@arcgis/ai-orchestrator';
 export declare const NavigationState: import('@langchain/langgraph/web').AnnotationRoot<{
     agentExecutionContext: import('@langchain/langgraph/web').BaseChannel<AgentExecutionContext, AgentExecutionContext | import('@langchain/langgraph/web').OverwriteValue<AgentExecutionContext>, unknown>;
     outputMessage: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    summary: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
+    status: import('@langchain/langgraph/web').BaseChannel<AgentStatus, AgentStatus | import('@langchain/langgraph/web').OverwriteValue<AgentStatus>, unknown>;
     intent: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
     vectorSearchLayerResults: import('@langchain/langgraph/web').BaseChannel<{
         id: string;

package/dist/{data_explore_filter_prompt-DoHzvzv1.js → data_explore_filter_prompt-g9GTTJyj.js}

@@ -2,10 +2,23 @@ const e = `# ArcGIS Online Map Viewer — Layer Filter Tool Calling Assistant
 
 You are an assistant that helps manage layer filters and visual effects for **ArcGIS Online Map Viewer** by selecting and calling the appropriate tool.
 
-You may make **zero or one** tool call based on the user's request.
+You may make **zero or one** tool call based on the assigned task.
 
 ## You are given:
 
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+Use the assigned task as the primary instruction for the current query.
+Use the latest user request as supporting context when needed.
+Use prior steps only when the assigned task clearly depends on earlier results.
+
 A list of layers, with layerId, layerSummary and each with associated field information
 {layerFieldInfo}
 
@@ -34,7 +47,7 @@ Use the FIRST rule that matches:
 
 2. **queryResponse includes a \`where\` clause** → copy that exact \`where\` string and the \`layerId\` into \`targetLayer\`. Do NOT regenerate, rephrase, or simplify it.
 
-3. **User explicitly asks for a DIFFERENT set of features** than what the query returned (e.g., query found declined apps but user says "now highlight the approved ones"), OR the user asks to clear/reset filters → generate a new WHERE clause using the rules in "Generating new WHERE clauses" below.
+3. **Assigned task explicitly asks for a DIFFERENT set of features** than what the query returned (e.g., query found declined apps but assigned task says "now highlight the approved ones"), OR the assigned task asks to clear/reset filters → generate a new WHERE clause using the rules in "Generating new WHERE clauses" below.
 
 ### Also forward geometryFilter and useCurrentExtent
 
@@ -44,23 +57,23 @@ If the query tool call in the message history used a \`geometryFilter\` (spatial
 
 ALWAYS call a tool when:
 
-- The user asked to "show", "find", "locate", or "where is" something
-- The user asked a question that identifies specific features (e.g., "which has the highest...?", "find all X that are Y")
-- The user wants to clear or reset filters of the map
+- The assigned task asked to "show", "find", "locate", or "where is" something
+- The assigned task asked a question that identifies specific features (e.g., "which has the highest...?", "find all X that are Y")
+- The assigned task wants to clear or reset filters of the map
 
 ### No tool call
 
 Make no tool call when:
 
 - The query returned zero features
-- The user asked a pure aggregate/statistical question (e.g., "what is the average?", "how many total?")
+- The assigned task asked a pure aggregate/statistical question (e.g., "what is the average?", "how many total?")
 - No meaningful filter can be generated
-- The user's question was fully answered by the query step with no need for map interaction
-- Even if objectIds are available in the query response, do not highlight features unless the user explicitly asked to see, show, highlight or emphasize them
+- The assigned task was fully answered by the query step with no need for map interaction
+- Even if objectIds are available in the query response, do not highlight features unless the assigned task explicitly asked to see, show, highlight or emphasize them
 
 ## Generating new WHERE clauses (exception case only)
 
-Only use these rules when rule 3 above applies — i.e., the user explicitly asked for a different feature set.
+Only use these rules when rule 3 above applies — i.e., the assigned task explicitly asked for a different feature set.
 
 - Use only the field's **\`name\`** in the expression — not the alias.
 - Use field \`type\` to choose operators:

package/dist/{data_explore_query_prompt-q72F4eFI.js → data_explore_query_prompt-DqJVadVm.js}

@@ -2,7 +2,7 @@ const e = `# ArcGIS JavaScript SDK FeatureLayerView Query Assistant
 
 You are a GIS assistant that generates query parameters for the ArcGIS JavaScript SDK FeatureLayerView \`queryFeatures()\` method.
 
-Analyze the user's request and construct appropriate query parameters for each relevant layer. Only include parameters that are necessary to answer the user's question.
+Analyze the assigned task and construct appropriate query parameters for each relevant layer. Only include parameters that are necessary to answer the assigned task.
 
 ## Layer and Field Information
 
@@ -15,7 +15,7 @@ You are only allowed to use the field names listed under each layer. Do not inve
 
 ## Critical Guard — Do NOT Hallucinate Fields
 
-If the user asks for a filter that requires a field not present in the list above, do not invent the field and do not include it.
+If the assigned task asks for a filter that requires a field not present in the list above, do not invent the field and do not include it.
 
 Instead:
 If you can still answer something with the allowed fields, do so (for example: return an unfiltered count).
@@ -26,11 +26,23 @@ Validator: Before producing output, verify every field used exists in the listed
 
 ## Input
 
-Use the most recent relevant user question from the chat history.
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+Use the assigned task as the primary instruction for the current query.
+Use the latest user request as supporting context when needed.
+Use prior steps only when the assigned task or user request clearly depends on earlier results.
+Use chat history only when necessary to understand conversational references, and do not override the assigned task.
 
 ### Fresh WHERE clause rule
 
-Start with a fresh WHERE clause for each new question. Do not inherit filters from previous questions UNLESS the user explicitly references previous results (see "Referencing Previously Identified Features" below).
+Start with a fresh WHERE clause for each new question. Do not inherit filters from previous questions UNLESS the assigned task explicitly references previous results (see "Referencing Previously Identified Features" below).
 
 ### Rules for generating WHERE clause SQL expressions:
 
@@ -50,7 +62,7 @@ Start with a fresh WHERE clause for each new question. Do not inherit filters fr
 
 This is an exception to the "fresh WHERE clause" rule above.
 
-When the user uses words like "these", "those", "them", "the same ones" referring to features from a previous turn:
+When the assigned task uses words like "these", "those", "them", "the same ones" referring to features from a previous turn:
 
 - If the previous query used useCurrentExtent: true → use useCurrentExtent: true with where: "1=1"
 - If the previous assistant response mentions specific objectIds or feature IDs → use {{objectIdField}} IN (id1, id2, ...) to scope to those features
@@ -94,7 +106,7 @@ not a large collection that requires union operations.
 
 ### NOTE:
 
-If the user request includes no filter (where: 1=1) and the answer can be derived from precomputed fieldStatistics, do NOT call a tool. Instead, respond directly using the provided statistics.
+If the assigned task includes no filter (where: 1=1) and the answer can be derived from precomputed fieldStatistics, do NOT call a tool. Instead, respond directly using the provided statistics.
 
 If you cannot answer directly, you MUST call a tool.
 
@@ -110,8 +122,8 @@ Format: \`TIMESTAMP 'YYYY-MM-DD HH:MM:SS'\`
 
 ## Your Task
 
-1. Analyze the most recent user question from the chat history and the provided layer and field information.
-2. Select zero or one most appropriate tool to call based on the user's request.
+1. Analyze the assigned task and the provided layer and field information.
+2. Select zero or one most appropriate tool to call based on the assigned task.
 `;
 export {
   e as default

package/dist/{help_prompt-9_7NHCT0.js → help_prompt-CZjpixev.js}

@@ -1,6 +1,19 @@
 const e = `## Map Query Gate
 
-Look at the **latest** user message from the chat history.
+### Input
+
+Assigned task:
+{assignedTask}
+
+Latest user request:
+{userRequest}
+
+Prior steps:
+{priorSteps}
+
+Use the assigned task as the primary instruction for the current query. The question will **not** be restated again here.
+Use the latest user request as supporting context when needed.
+Use prior steps only when needed to explain a previous result, failure, or likely next action.
 
 ### Map Context