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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 16, 2026 1:55am

PR Summary

Medium Risk
Medium risk because it changes core workflow execution cancellation semantics (pub/sub subscription, backstop checks, wait-loop waking) and threads abort signals through tool HTTP execution across many callers, which could alter timing and error paths.

Overview
Improves workflow cancellation responsiveness by replacing periodic Redis polling in ExecutionEngine with a shared pub/sub cancellation channel plus a one-time Redis durable backstop check at engine start; all cancellation sources now funnel through signalCancelled() to immediately wake waitForAny/AllExecutions, and the engine unsubscribes on completion.

Refactors executeTool to an options-object API ({ skipPostProcess, executionContext, signal }) and updates block handlers, Copilot tool execution, and all LLM providers to use it; the optional signal is now propagated into internal fetches, SSRF-protected external fetches, and MCP tool calls so in-flight tool HTTP can be aborted. Adds/updates unit tests to cover pub/sub wakeups, unsubscribe cleanup, backstop behavior, and caller-signal abort propagation.

^{Reviewed by Cursor Bugbot for commit d5f86b2. Configure here.}

Greptile Summary

This PR replaces 500 ms Redis-polling cancellation with a unified pub/sub + durable-backstop model, threads AbortSignal from LLM provider tool-call loops all the way through executeTool into internal fetch/secureFetchWithPinnedIP/MCP HTTP calls, and migrates executeTool to an options-object signature across 14 providers, 5 handlers, and the copilot integration.

• Cancellation architecture: signalCancelled() unifies all three sources (AbortSignal, pub/sub event, Redis backstop); abortPromise wakes waitForAnyExecution and waitForAllExecutions races immediately on cancel.
• Signal threading: request.abortSignal is now forwarded to every executeTool call inside Anthropic and OpenAI (Responses) tool loops, and executeToolRequest chains the signal into its per-attempt AbortController with correct caller-vs-timeout discrimination.
• Signature migration: executeTool(id, params, options?) replaces the old positional overload; all call sites in providers, handlers, and copilot fallback are updated.

Confidence Score: 5/5

Safe to merge; the core cancellation path (pub/sub wake → abortPromise → engine returns) is correct and well-tested.

The two observations are bounded edge-cases that don't affect the primary cancellation flow. All three previously-identified issues are confirmed fixed. 125 targeted tests pass and TSC is clean.

engine.ts waitForAllExecutions and tools/index.ts retry-sleep signal handling are worth a second look before adding more complex parallel/Response-block workflows.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client
    participant CancelAPI
    participant PubSub as PubSubChannel
    participant Redis
    participant Engine as ExecutionEngine
    participant Provider as LLM Provider
    participant ET as executeTool
    participant Fetch as HTTP Fetch

    Client->>CancelAPI: POST /cancel
    CancelAPI->>Redis: "SET execution:cancel:{id}"
    CancelAPI->>PubSub: "publish({executionId})"
    PubSub-->>Engine: subscribe callback fires
    Engine->>Engine: signalCancelled()
    Note over Engine: abortPromise resolves
    Engine->>Engine: waitForAnyExecution wakes
    Engine-->>Client: status cancelled
    Provider->>ET: executeTool with signal
    ET->>Fetch: fetch with chained signal
    Fetch--xProvider: AbortError

_{Reviews (2): Last reviewed commit: "chore(tests): rename stale 'cancellation..." | Re-trigger Greptile}

@greptile

@cursor review