v0.5.79: longer MCP tools timeout, optimize loop/parallel regeneration, enrich.so integration

[waleedlatif1]

• improvement(ratelimits, sockets): increase across all plans, reconnecting notif for sockets (improvement(ratelimits, sockets): increase across all plans, reconnecting notif for sockets #3096)
• fix(mcp): pass timeout to SDK callTool to override 60s default (fix(mcp): pass timeout to SDK callTool to override 60s default #3101)
• fix(workflow): optimize loop/parallel regeneration and prevent duplicate agent tools (fix(workflow): optimize loop/parallel regeneration and prevent duplicate agent tools #3100)
• feat(tools): added enrich so (feat(tools): added enrich so #3103)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Feb 1, 2026 5:20am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR bundles four separate improvements into version 0.5.79:

Enrich.so Integration (#3103)

• Added comprehensive B2B data enrichment integration with 30 new tools covering person/profile enrichment, email finding, phone lookup, email verification, IP/company lookup, company enrichment, people/company search, LinkedIn posts/activities, and utility functions
• All tools properly use user-only visibility for API keys per security guidelines
• Includes block configuration, tool definitions, type definitions, and documentation

MCP Timeout Fix (#3101)

• Increased MCP tool execution timeout from SDK default 60s to 10 minutes (600000ms) to handle long-running operations
• Prevents premature timeouts for complex MCP tool operations

Workflow Performance Optimization (#3100)

• Removed unused addBlock method (135 lines)
• Optimized loop/parallel block regeneration to only run when structure-affecting changes occur (adding loop/parallel containers or their children)
• Edge operations now skip regeneration since edges don't affect loop/parallel structure (determined by parentId)
• Prevents duplicate agent tools during regeneration

Rate Limits & Socket Improvements (#3096)

• Increased rate limits for all tiers: free async 200, pro sync 150/async 1000, team sync 300/async 2500, enterprise sync 600/async 5000
• Added isReconnecting state to socket provider for better UX during connection issues
• Improved socket reconnection event handling using Manager-level events
• Added workflowId to subblock/variable update payloads with validation to prevent workflow ID mismatches

Confidence Score: 5/5

• Safe to merge with no critical issues found
• All changes are well-structured improvements with clear benefits: performance optimization removes unused code and prevents unnecessary regeneration, MCP timeout fix addresses a real limitation, socket changes improve reliability, rate limit increases provide better user experience, and Enrich.so integration follows established patterns with proper security (user-only API keys)
• No files require special attention

Important Files Changed

Filename	Overview
apps/sim/lib/mcp/client.ts	Increased MCP tool timeout from 60s to 10 minutes (600000ms) to handle long-running operations
apps/sim/stores/workflows/workflow/store.ts	Removed unused addBlock method and optimized loop/parallel regeneration to only run when needed, improving performance
apps/sim/lib/core/rate-limiter/types.ts	Increased rate limits across all subscription tiers (free: 50→50 sync, 200 async; pro: 150 sync, 1000 async; team: 300 sync, 2500 async; enterprise: 600 sync, 5000 async)
apps/sim/app/workspace/providers/socket-provider.tsx	Added reconnecting state tracking and improved error handling for socket disconnections
apps/sim/socket/handlers/subblocks.ts	Added workflowId to payload and validation to prevent workflow ID mismatches during subblock updates
apps/sim/socket/handlers/variables.ts	Added workflowId to payload and validation to prevent workflow ID mismatches during variable updates
apps/sim/blocks/blocks/enrich.ts	Added Enrich.so block configuration with 30 operations for B2B data enrichment
apps/sim/tools/enrich/email_to_profile.ts	Implements email to LinkedIn profile enrichment with proper API key visibility as user-only

Sequence Diagram

sequenceDiagram
    participant Client as Frontend Client
    participant Socket as Socket Provider
    participant Handler as Socket Handler
    participant Store as Workflow Store
    participant DB as Database

    Note over Client,DB: Subblock/Variable Update Flow (with workflowId validation)
    
    Client->>Socket: emitSubblockUpdate(blockId, subblockId, value, operationId, workflowId)
    Socket->>Handler: socket.emit('subblock-update', {workflowId, blockId, ...})
    Handler->>Handler: Validate sessionWorkflowId vs payloadWorkflowId
    alt Workflow ID mismatch
        Handler->>Socket: emit('operation-failed', {operationId, error})
        Socket->>Client: Operation failed notification
    else Valid workflow ID
        Handler->>Handler: Queue update for coalescing
        Handler->>DB: Flush batched update
        DB-->>Handler: Update success
        Handler->>Socket: emit('operation-confirmed', {operationId})
        Handler->>Client: Broadcast update (except sender)
    end

    Note over Store: Loop/Parallel Optimization
    
    Client->>Store: batchAddBlocks(blocks, edges)
    Store->>Store: Check if blocks affect loop/parallel structure
    alt Affects structure (loop/parallel container or child)
        Store->>Store: generateLoopBlocks() / generateParallelBlocks()
    else Only edges or unrelated blocks
        Store->>Store: Skip regeneration (reuse existing)
    end
    Store-->>Client: State updated

    Note over Client,Handler: MCP Tool Execution
    
    Client->>Handler: Execute MCP tool
    Handler->>Handler: client.callTool(params, undefined, {timeout: 600000})
    Note right of Handler: 10 min timeout instead of 60s default
    Handler-->>Client: Tool result

Loading

[greptile-apps]

_{8 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}