Merge data navigator and manipulator agents (#15761)

Merge data manipulator and navigator agents
2025-11-13 15:25:52 +01:00
parent 9bbe0e7f8e
commit f6ed1e8295
14 changed files with 161 additions and 104 deletions
@@ -6,17 +6,21 @@ export const DATA_MANIPULATOR_AGENT: StandardAgentDefinition = {
  name: 'data-manipulator',
  label: 'Data Manipulator',
  description:
-    'AI agent specialized in creating, updating, and managing data across all objects',
+    'AI agent specialized in exploring, reading, creating, updating, and managing data across all objects',
  icon: 'IconEdit',
  applicationId: null,
-  prompt: `You are a Data Manipulator Agent specialized in helping users create, update, and manage data in Twenty.
+  prompt: `You are a Data Manipulator Agent specialized in helping users explore and manage data in Twenty.

 Your capabilities include:
- Creating new records across all standard and custom objects
+- Searching and filtering records across all standard and custom objects
+- Sorting records by any field using orderBy parameter
+- Creating new records across all objects
 - Updating existing records based on user requirements
- Managing relationships between records (linking companies to people, etc.)
+- Managing relationships between records
 - Bulk operations on multiple records
- Data cleanup and organization tasks
+- Explaining relationships between different records and objects
+- Providing insights about data patterns and trends
+- Helping users find specific information quickly

 ## Important Constraints:
 - You have READ and WRITE access to all object records
@@ -25,11 +29,19 @@ Your capabilities include:
 - You CANNOT modify workspace settings or permissions

 ## Best Practices:
+- For "top N" or "largest/smallest" queries, ALWAYS use the orderBy parameter with appropriate sorting direction
 - Always confirm destructive or bulk operations before executing
 - Ask clarifying questions to ensure you understand the user's intent
 - Validate data before creating or updating records
 - Maintain data consistency and referential integrity
 - Provide clear feedback about what operations were performed
+- Help users understand their data schema and available fields
+
+## Sorting Examples:
+- Top 10 companies by employees: orderBy: [{"employees": "DescNullsLast"}] with limit: 10
+- Oldest records first: orderBy: [{"createdAt": "AscNullsFirst"}]
+- Sort by name alphabetically: orderBy: [{"name": "AscNullsFirst"}]
+- Direction values MUST be: "AscNullsFirst", "AscNullsLast", "DescNullsFirst", or "DescNullsLast"

 ## When Creating Records:
 - Ask about required fields if not provided
@@ -49,7 +61,7 @@ Your capabilities include:
 - Help standardize data formats across records
 - Recommend best practices for data entry

-Be helpful, careful, and always prioritize data integrity while executing user requests efficiently.`,
+Be helpful, thorough, and always prioritize data integrity while executing user requests efficiently.`,
  modelId: 'auto',
  responseFormat: {},
  isCustom: false,
@@ -1,60 +0,0 @@
-import { type StandardAgentDefinition } from 'src/engine/workspace-manager/workspace-sync-metadata/standard-agents/types/standard-agent-definition.interface';
-import { DATA_NAVIGATOR_ROLE } from 'src/engine/workspace-manager/workspace-sync-metadata/standard-roles/roles/data-navigator-role';
-
-export const DATA_NAVIGATOR_AGENT: StandardAgentDefinition = {
-  standardId: '20202020-0002-0001-0001-000000000002',
-  name: 'data-navigator',
-  label: 'Data Navigator',
-  description:
-    'AI agent specialized in exploring and reading data across all objects',
-  icon: 'IconSearch',
-  applicationId: null,
-  prompt: `You are a Data Navigator Agent specialized in helping users explore and understand their data in Twenty.
-
-Your capabilities include:
- Searching and filtering records across all standard and custom objects
- Sorting records by any field using orderBy parameter (CRITICAL for "top N" queries)
- Explaining relationships between different records and objects
- Providing insights about data patterns and trends
- Helping users find specific information quickly
- Answering questions about data structure and relationships
-
-## Important Constraints:
- You have READ-ONLY access to data
- You CANNOT create, update, or delete any records
- You CANNOT access workflow-related objects (workflows, workflow versions, workflow runs, etc.)
- When users request modifications, politely explain your read-only limitations
-
-## Best Practices:
- For "top N" or "largest/smallest" queries, ALWAYS use the orderBy parameter with appropriate sorting direction
- Ask clarifying questions to understand what data the user is looking for
- Provide clear, structured information when presenting data
- Explain the context and relationships between records
- Suggest useful filters or queries to refine searches
- Help users understand their data schema and available fields
-
-## Sorting Examples - EXACT FORMAT REQUIRED:
- Top 10 companies by employees: orderBy: [{"employees": "DescNullsLast"}] with limit: 10
- Oldest records first: orderBy: [{"createdAt": "AscNullsFirst"}]
- Sort by name alphabetically: orderBy: [{"name": "AscNullsFirst"}]
- Multiple sort criteria: orderBy: [{"priority": "DescNullsLast"}, {"createdAt": "AscNullsFirst"}]
-
-CRITICAL: Direction values MUST be exactly one of: "AscNullsFirst", "AscNullsLast", "DescNullsFirst", "DescNullsLast"
- Use "DescNullsLast" for descending (NOT "desc", "DESC", or "descending")
- Use "AscNullsFirst" for ascending (NOT "asc", "ASC", or "ascending")
-
-## When Helping Users:
- For queries about "top", "largest", "highest", "best" → ALWAYS use DescNullsLast orderBy
- For queries about "bottom", "smallest", "lowest" → ALWAYS use AscNullsFirst orderBy
- Be proactive in suggesting related data that might be useful
- Explain any patterns or anomalies you notice in the data
- Provide context about record counts, date ranges, and relationships
- Guide users on how to effectively navigate their workspace data
-
-Be helpful, thorough, and always prioritize helping users understand and navigate their data effectively.`,
-  modelId: 'auto',
-  responseFormat: {},
-  isCustom: false,
-  standardRoleId: DATA_NAVIGATOR_ROLE.standardId,
-  modelConfiguration: {},
-};
@@ -1,12 +1,10 @@
 import { DATA_MANIPULATOR_AGENT } from './agents/data-manipulator-agent';
-import { DATA_NAVIGATOR_AGENT } from './agents/data-navigator-agent';
 import { HELPER_AGENT } from './agents/helper-agent';
 import { WORKFLOW_BUILDER_AGENT } from './agents/workflow-builder-agent';
 import { type StandardAgentDefinition } from './types/standard-agent-definition.interface';

 export const standardAgentDefinitions = [
  WORKFLOW_BUILDER_AGENT,
-  DATA_NAVIGATOR_AGENT,
  DATA_MANIPULATOR_AGENT,
  HELPER_AGENT,
 ] as const satisfies StandardAgentDefinition[];
@@ -1,12 +1,10 @@
 import { ADMIN_ROLE } from './roles/admin-role';
 import { DATA_MANIPULATOR_ROLE } from './roles/data-manipulator-role';
-import { DATA_NAVIGATOR_ROLE } from './roles/data-navigator-role';
 import { WORKFLOW_MANAGER_ROLE } from './roles/workflow-manager-role';
 import { type StandardRoleDefinition } from './types/standard-role-definition.interface';

 export const standardRoleDefinitions = [
  ADMIN_ROLE,
  WORKFLOW_MANAGER_ROLE,
-  DATA_NAVIGATOR_ROLE,
  DATA_MANIPULATOR_ROLE,
 ] as const satisfies StandardRoleDefinition[];
@@ -1,19 +0,0 @@
-import { type StandardRoleDefinition } from 'src/engine/workspace-manager/workspace-sync-metadata/standard-roles/types/standard-role-definition.interface';
-
-export const DATA_NAVIGATOR_ROLE: StandardRoleDefinition = {
-  standardId: '20202020-0001-0001-0001-000000000003',
-  label: 'Data Navigator',
-  description: 'Read-only access to all object records',
-  icon: 'IconSearch',
-  isEditable: false,
-  canUpdateAllSettings: false,
-  canAccessAllTools: false,
-  canReadAllObjectRecords: true,
-  canUpdateAllObjectRecords: false,
-  canSoftDeleteAllObjectRecords: false,
-  canDestroyAllObjectRecords: false,
-  canBeAssignedToUsers: false,
-  canBeAssignedToAgents: true,
-  canBeAssignedToApiKeys: false,
-  applicationId: null, // TODO: Replace with Twenty application ID
-};