v0.5.64: unsubscribe, search improvements, metrics, additional SSO configuration

[waleedlatif1]

• improvement(emails): update unsub page, standardize unsub process (improvement(emails): update unsub page, standardize unsub process #2881)
• feat(mcp): updated mcp subblocks for mcp tools to match subblocks (feat(mcp): updated mcp subblocks for mcp tools to match subblocks #2882)
• feat(notifs): added block name to error notifications (feat(notifs): added block name to error notifications #2883)
• fix(undo-redo): preserve subblock values during undo/redo cycles (fix(undo-redo): preserve subblock values during undo/redo cycles #2884)
• fix(linear): team selector in tool input (fix(linear): team selector in tool input #2886)
• feat(terminal): add fix in copilot for errors (feat(terminal): add fix in copilot for errors #2885)
• feat(search): added operations to search modal in main app, updated retrieval in docs to use RRF (feat(search): added operations to search modal in main app, updated retrieval in docs to use RRF #2889)
• improvement(router): add resizable textareas for router conditions (improvement(router): add resizable textareas for router conditions #2888)
• feat(browseruse): upgraded browseruse endpoints to v2 (feat(browseruse): upgraded browseruse endpoints to v2 #2890)
• improvement(copilot): variables, conditions, router (improvement(copilot): variables, conditions, router #2887)
• feat(settings): add debug mode for superusers (feat(settings): add debug mode for superusers #2893)
• improvement(stats): should track mcp and a2a executions like other trigger types (improvement(stats): should track mcp and a2a executions like other trigger types #2895)
• feat(api): added workflows api route for dynamic discovery (feat(api): added workflows api route for dynamic discovery #2892)
• improvement(kb): migrate manual fetches in kb module to use reactquery (improvement(kb): migrate manual fetches in kb module to use reactquery #2894)
• fix(sso): removed provider specific OIDC logic from SSO registration & deregistration scripts (fix(sso): removed provider specific OIDC logic from SSO registration & deregistration scripts #2896)
• improvement(modal): fixed popover issue in custom tools modal, removed the ability to update if no changes made (improvement(modal): fixed popover issue in custom tools modal, removed the ability to update if no changes made #2897)
• fix(kb): align bulk chunk operation with API response (fix(kb): align bulk chunk operation with API response #2899)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Jan 20, 2026 8:24am

[greptile-apps]

Greptile Summary

This PR combines multiple improvements across email management, search functionality, SSO configuration, metrics tracking, and workflow APIs.

Major Changes:

• Email Unsubscribe System: Standardized unsubscribe process with token-based verification and granular preferences (marketing, updates, notifications)
• Workflow API Discovery: New /api/v1/workflows endpoints for listing and retrieving workflows with input field extraction for dynamic tool integration
• Search Enhancements: Added operation-level search in main app with RRF (Reciprocal Rank Fusion) retrieval for documentation
• SSO Configuration: Removed provider-specific OIDC logic, now uses discovery endpoint for all providers (tested with 10 common OIDC providers)
• Metrics Tracking: Added MCP and A2A execution tracking to user stats for better billing visibility
• Undo/Redo Fix: Preserves subblock values during undo/redo cycles to prevent data loss in function blocks
• Debug Mode: Superuser capability to import workflows for debugging
• UI Improvements: Resizable textareas for router conditions, fixed popover issues in custom tools modal, added block names to error notifications

Browser Use Update: Upgraded to v2 endpoints with documentation updates

Confidence Score: 4/5

• This PR is safe to merge with minor considerations for production SSO configuration
• The PR includes well-tested features with appropriate error handling. The SSO changes remove provider-specific logic and use standard OIDC discovery, which is more maintainable. All critical paths have proper validation. The one consideration is ensuring SSO configuration is thoroughly tested in production environments with real IdPs.
• Pay close attention to SSO registration script when deploying to production - ensure discovery endpoints are accessible

Important Files Changed

Filename	Overview
packages/db/scripts/register-sso-provider.ts	Enhanced OIDC discovery with endpoint fetching, removed provider-specific logic
apps/sim/app/api/v1/workflows/route.ts	New API endpoint for listing workflows with pagination and filtering
apps/sim/app/api/v1/workflows/[id]/route.ts	New API endpoint for fetching individual workflow details with input fields
apps/sim/stores/undo-redo/utils.ts	Added functions to capture subblock values during undo/redo operations
apps/sim/lib/logs/execution/logger.ts	Added MCP and A2A trigger execution tracking to user stats
apps/sim/lib/search/tool-operations.ts	New tool operations index for search modal with verb aliases
apps/sim/hooks/queries/knowledge.ts	Migrated knowledge base queries to React Query, fixed BulkChunkOperationResult interface
apps/sim/lib/messaging/email/unsubscribe.ts	Standardized email unsubscribe system with token verification and preferences

Sequence Diagram

sequenceDiagram
    participant User
    participant UI
    participant API
    participant DB
    participant IdP as Identity Provider

    Note over User,IdP: Workflow API Discovery Flow
    User->>UI: Search for workflow
    UI->>API: GET /api/v1/workflows?workspaceId=X
    API->>DB: Query workflows with permissions
    DB-->>API: Return workflow list
    API-->>UI: Workflows with metadata
    UI->>API: GET /api/v1/workflows/{id}
    API->>DB: Fetch workflow details + blocks
    DB-->>API: Workflow + blocks data
    API->>API: Extract input fields from blocks
    API-->>UI: Workflow with inputs schema
    UI-->>User: Display workflow details

    Note over User,IdP: SSO Registration Flow (Updated)
    User->>API: Run register-sso-provider script
    API->>API: Build config from env vars
    API->>IdP: Fetch /.well-known/openid-configuration
    IdP-->>API: Discovery document with endpoints
    API->>API: Merge user-provided + discovered endpoints
    API->>DB: Insert/update SSO provider
    DB-->>API: Provider registered
    API-->>User: SSO provider configured

    Note over User,DB: Email Unsubscribe Flow
    User->>API: Click unsubscribe link with token
    API->>API: Verify token with email
    API->>DB: Update email preferences
    DB-->>API: Preferences saved
    API-->>User: Unsubscribe confirmed

    Note over User,DB: Undo/Redo Fix
    User->>UI: Edit code in function block
    User->>UI: Delete block
    UI->>UI: Capture subblock values before delete
    UI->>UI: Store in undo history with values
    User->>UI: Undo delete
    UI->>UI: Restore block with preserved values
    UI-->>User: Code restored correctly

Loading

[greptile-apps]

Additional Comments (3)

1. apps/sim/lib/copilot/tools/client/other/search-documentation.ts, line 71-73 (link)

   style: Setting success state twice is redundant. The second call on line 73 can be removed since the state is already set on line 71.

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

2. apps/sim/app/workspace/[workspaceId]/w/[workflowId]/components/panel/components/copilot/components/user-input/utils.ts, line 176-178 (link)

   logic: The blocks context equality check uses some() which returns true if ANY existing blockId matches ANY new blockId, but the function name areContextsEqual suggests exact equality. Consider if this should check for exact array equality instead. Should the blocks context comparison require exact match of all blockIds or is partial overlap the intended behavior?

3. apps/sim/app/workspace/[workspaceId]/w/[workflowId]/hooks/use-scroll-management.ts, line 34 (link)

   style: messages: any[] should be properly typed. Consider using a specific message interface instead of any[]

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

   Context Used: Context from dashboard - TypeScript conventions and type safety (source)

_{169 files reviewed, 10 comments}

_{Edit Code Review Agent Settings | Greptile}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

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

[waleedlatif1]

@greptile