@arcgis/ai-agents 5.1.0-next.60 → 5.1.0-next.61

package/dist/agents/arcgisKnowledge/state/arcgisKnowledgeState.d.ts

@@ -1,6 +1,6 @@
-import { ChatHistory } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext } from '@arcgis/ai-orchestrator';
 export declare const arcgisKnowledgeState: import('@langchain/langgraph/web').AnnotationRoot<{
-    messages: import('@langchain/langgraph/web').BaseChannel<ChatHistory, ChatHistory | import('@langchain/langgraph/web').OverwriteValue<ChatHistory>, unknown>;
+    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>;
     intent: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
 }>;

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

@@ -1,8 +1,8 @@
-import { ChatHistory, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
 import { QueryResponse } from '../types/types';
 import { LayerFieldInfo } from '../../../types/types';
 export declare const DataExplorationState: import('@langchain/langgraph/web').AnnotationRoot<{
-    messages: import('@langchain/langgraph/web').BaseChannel<ChatHistory, ChatHistory | import('@langchain/langgraph/web').OverwriteValue<ChatHistory>, unknown>;
+    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>;
     vectorSearchLayerIds: import('@langchain/langgraph/web').LastValue<string[]>;
     vectorSearchFieldResults: import('@langchain/langgraph/web').LastValue<VectorSearchFieldResults>;

package/dist/agents/dataExploration/tools/filterTools/setFeatureEffect/adapter.d.ts

@@ -5,6 +5,7 @@ export declare const setFeatureEffectWrapper: ({ targetLayer, geometryFilter, us
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[];
     };
     geometryFilter?: GeometryConfig;
     useCurrentExtent?: boolean;
@@ -15,6 +16,7 @@ export declare const setFeatureEffectTool: import('@langchain/core/tools').Dynam
     targetLayer: z.ZodObject<{
         layerId: z.ZodString;
         where: z.ZodString;
+        objectIds: z.ZodOptional<z.ZodArray<z.ZodNumber>>;
     }, z.core.$strip>;
     geometryFilter: z.ZodOptional<z.ZodUnion<readonly [z.ZodObject<{
         layerId: z.ZodString;
@@ -53,6 +55,7 @@ export declare const setFeatureEffectTool: import('@langchain/core/tools').Dynam
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     includedEffect: string;
     excludedEffect: string;
@@ -77,6 +80,7 @@ export declare const setFeatureEffectTool: import('@langchain/core/tools').Dynam
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     geometryFilter?: {
         layerId: string;

package/dist/agents/dataExploration/tools/filterTools/setFeatureEffect/core.d.ts

@@ -3,4 +3,5 @@ import { default as MapView } from '@arcgis/core/views/MapView.js';
 export declare const setFeatureEffect: (targetLayer: {
     layerId: string;
     where: string;
+    objectIds?: number[];
 }, arcgisMapView: MapView, includedEffect: string, excludedEffect: string, geometryFilter?: GeometryConfig, useCurrentExtent?: boolean) => Promise<string>;

package/dist/agents/dataExploration/tools/filterTools/setFeatureFilter/adapter.d.ts

@@ -5,6 +5,7 @@ export declare const setFeatureFilterWrapper: ({ targetLayer, geometryFilter, }:
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[];
     };
     geometryFilter?: GeometryConfig;
 }, config?: RunnableConfig) => Promise<string>;
@@ -12,6 +13,7 @@ export declare const setFeatureFilterTool: import('@langchain/core/tools').Dynam
     targetLayer: z.ZodObject<{
         layerId: z.ZodString;
         where: z.ZodString;
+        objectIds: z.ZodOptional<z.ZodArray<z.ZodNumber>>;
     }, z.core.$strip>;
     geometryFilter: z.ZodOptional<z.ZodUnion<readonly [z.ZodObject<{
         layerId: z.ZodString;
@@ -47,6 +49,7 @@ export declare const setFeatureFilterTool: import('@langchain/core/tools').Dynam
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     geometryFilter?: {
         layerId: string;
@@ -68,6 +71,7 @@ export declare const setFeatureFilterTool: import('@langchain/core/tools').Dynam
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     geometryFilter?: {
         layerId: string;

package/dist/agents/dataExploration/tools/filterTools/setFeatureFilter/core.d.ts

@@ -3,4 +3,5 @@ import { default as MapView } from '@arcgis/core/views/MapView.js';
 export declare const setFeatureFilter: (targetLayer: {
     layerId: string;
     where: string;
+    objectIds?: number[];
 }, arcgisMapView: MapView, geometryFilter?: GeometryConfig) => Promise<string>;

package/dist/agents/dataExploration/tools/index.d.ts

@@ -301,6 +301,7 @@ export declare const filterTools: (import('@langchain/core/tools').DynamicStruct
     targetLayer: import('zod').ZodObject<{
         layerId: import('zod').ZodString;
         where: import('zod').ZodString;
+        objectIds: import('zod').ZodOptional<import('zod').ZodArray<import('zod').ZodNumber>>;
     }, import('zod/v4/core').$strip>;
     geometryFilter: import('zod').ZodOptional<import('zod').ZodUnion<readonly [import('zod').ZodObject<{
         layerId: import('zod').ZodString;
@@ -339,6 +340,7 @@ export declare const filterTools: (import('@langchain/core/tools').DynamicStruct
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     includedEffect: string;
     excludedEffect: string;
@@ -363,6 +365,7 @@ export declare const filterTools: (import('@langchain/core/tools').DynamicStruct
     targetLayer: {
         layerId: string;
         where: string;
+        objectIds?: number[] | undefined;
     };
     geometryFilter?: {
         layerId: string;

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

@@ -1,6 +1,6 @@
-import { ChatHistory } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext } from '@arcgis/ai-orchestrator';
 export declare const HelpState: import('@langchain/langgraph/web').AnnotationRoot<{
-    messages: import('@langchain/langgraph/web').BaseChannel<ChatHistory, ChatHistory | import('@langchain/langgraph/web').OverwriteValue<ChatHistory>, unknown>;
+    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>;
 }>;
 export type HelpGraphStateType = typeof HelpState.State;

package/dist/agents/layerStyling/state/layerStylingState.d.ts

@@ -1,7 +1,7 @@
-import { ChatHistory, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
+import { AgentExecutionContext, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
 import { LayerFieldInfo } from '../../../types/types';
 export declare const LayerStylingState: import('@langchain/langgraph/web').AnnotationRoot<{
-    messages: import('@langchain/langgraph/web').BaseChannel<ChatHistory, ChatHistory | import('@langchain/langgraph/web').OverwriteValue<ChatHistory>, unknown>;
+    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>;
     vectorSearchLayerIds: import('@langchain/langgraph/web').LastValue<string[]>;
     vectorSearchFieldResults: import('@langchain/langgraph/web').LastValue<VectorSearchFieldResults>;

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

@@ -1,6 +1,6 @@
-import { ChatHistory, VectorSearchFieldResults } from '@arcgis/ai-orchestrator';
+import { VectorSearchFieldResults, AgentExecutionContext } from '@arcgis/ai-orchestrator';
 export declare const NavigationState: import('@langchain/langgraph/web').AnnotationRoot<{
-    messages: import('@langchain/langgraph/web').BaseChannel<ChatHistory, ChatHistory | import('@langchain/langgraph/web').OverwriteValue<ChatHistory>, unknown>;
+    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>;
     intent: import('@langchain/langgraph/web').BaseChannel<string, string | import('@langchain/langgraph/web').OverwriteValue<string>, unknown>;
     vectorSearchLayerResults: import('@langchain/langgraph/web').BaseChannel<{

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

@@ -22,22 +22,31 @@ This is what the query tool returned:
 
 ## Your task
 
-1. Analyze the user's request and the provided layer and field information.
-2. Generate a **single ArcGIS SQL WHERE clause** to match features based on the user's request and intent.
-3. Select the most appropriate tool to call based on the user's request.
+1. Decide whether a tool call is needed (see "When to call a tool" below).
+2. If needed, determine \`targetLayer\` using the priority rules below.
+3. Select the most appropriate tool.
 
-The tool will apply the provided WHERE clause to the layer in the map viewer.
+## How to determine targetLayer (follow in order)
+
+Use the FIRST rule that matches:
+
+1. **queryResponse includes \`objectIds\` and \`objectIdField\`** → pass them as \`targetLayer.objectIds\` array and set \`where\` to \`"1=1"\`. Do NOT construct a WHERE clause with IN(...).
+
+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.
+
+### Also forward geometryFilter and useCurrentExtent
+
+If the query tool call in the message history used a \`geometryFilter\` (spatial/proximity query) or \`useCurrentExtent: true\`, include the same parameters in your tool call. Without them, the filter would apply to the entire layer instead of just the spatially scoped features.
 
 ## When to call a tool
 
-ALWAYS call a tool to visually highlight features on the map when:
+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 rest filters of the map
-
-The purpose is to visually emphasize the relevant features on the map so the user can
-see them.
+- The user wants to clear or reset filters of the map
 
 ### No tool call
 
@@ -47,27 +56,20 @@ Make no tool call when:
 - The user 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
+
+## Generating new WHERE clauses (exception case only)
 
-### Rules for generating Layer Filter expressions:
+Only use these rules when rule 3 above applies — i.e., the user explicitly asked for a different feature set.
 
-- Use only the field’s **\`name\`** in the output expression.
-- Use metadata (\`alias\`, \`description\`, \`statistics\`) only to help understand the user's meaning — not in the syntax.
-- Use field \`type\` to choose appropriate operators:
+- Use only the field's **\`name\`** in the expression — not the alias.
+- Use field \`type\` to choose operators:
   - **String** → \`LIKE '%value%'\`, \`=\`, \`IN (...)\`
   - **Number/Date** → \`=\`, \`<\`, \`>\`, \`BETWEEN\`, etc.
-- Use fields with the **highest \`relevanceScore\`**.
-- DO NOT use subqueries or \`SELECT\` keyword.
+- **Coded-value domain fields** → use the numeric/string **code**, never the domain name.
+- **Range domain fields** → use the listed min/max as valid bounds.
+- DO NOT use subqueries or \`SELECT\`.
 - Combine conditions with \`AND\`, \`OR\`, or \`NOT\` as appropriate.
-- **Coded-value domain fields** → Always use the numeric/string **code** in WHERE clauses, never the domain name. Domain values are listed under each field as \`code=name\` pairs
-- **Range domain fields** → Use the listed min/max as valid bounds for comparisons.
-- If no meaningful layer filter can be generated, do not call a tool.
-
-## Top N / Ranked queries
-
-When the query response includes \`objectIds\` and \`objectIdField\`, use them:
-{{objectIdField}} IN (id1, id2, id3, ...)
-
-This ensures ONLY the exact features from the query get the effect.
 
 ## SQL-92 Date/Time Syntax
 
@@ -96,12 +98,10 @@ Examples:
 Q: "Is well P132_1873 within 300m from a protected area?"
 Target: Protected Areas (what we want to find)
 Geometry: Well (where="ID = 'P132_1873'" - single point)
-Result: Returns which protected areas are nearby
 
 Q: "Find roads within 500m of park X"
 Target: Roads (what we want to find)
 Geometry: Park X (specific location)
-Result: Returns which roads are nearby
 
 Key principle: The geometry layer should be the SIMPLER geometry (ideally a single feature or small set),
 not a large collection that requires union operations.

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

@@ -26,11 +26,15 @@ Validator: Before producing output, verify every field used exists in the listed
 
 ## Input
 
-Use the most recent relevant user question from the chat history. The question will **not** be restated again here. Start with a fresh WHERE clause for each question - do not inherit filters from previous questions unless user explicitly asks to combine them.
+Use the most recent relevant user question from the chat history.
 
-### Rules for generating where clause SQL expressions:
+### Fresh WHERE clause rule
 
-- Use only the field’s **\`name\`** in the output expression.
+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).
+
+### Rules for generating WHERE clause SQL expressions:
+
+- Use only the field's **\`name\`** in the output expression.
 - Use metadata (\`alias\`, \`description\`, \`statistics\`) only to help understand the user's meaning — not in the syntax.
 - Use field \`type\` to choose appropriate operators:
   - **String** → \`LIKE '%value%'\`, \`=\`, \`IN (...)\` (prefer \`LIKE\` over \`=\`)
@@ -42,6 +46,16 @@ Use the most recent relevant user question from the chat history. The question w
 - **Range domain fields** → Use the listed min/max as valid bounds for comparisons.
 - If no meaningful layer filter can be generated, do not call a tool.
 
+## Referencing Previously Identified Features
+
+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:
+
+- 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
+- If neither is available, use the same WHERE clause and layer from the previous query turn to re-select the same features
+
 ### Mixed Questions
 
 If a question has both aggregate and display components (e.g., "How many wells have depth > 100? Show them"):

package/dist/index.d.ts

@@ -1,7 +1,5 @@
 export * from './agents/navigation';
 export * from './agents/dataExploration';
-export * from './agents/layerFilter';
-export * from './agents/layerQuery';
 export * from './agents/layerStyling';
 export * from './agents/help';
 export * from './agents/arcgisKnowledge';