Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 18, 2026 2:15am

@cursor review

@greptile

Greptile Summary

This PR modifies the block protection logic so that only inbound connections to a locked block are protected — outbound connections from a locked block can now be freely added or removed. The change is implemented in two files:

• block-protection-utils.ts: isEdgeProtected now only calls isBlockProtected on the target of an edge, removing the previous || isBlockProtected(edge.source, blocks) check.
• workflow.tsx: All four call sites of isEdgeProtected now have updated comments and notification messages to reflect the new semantics.

The change is logically consistent, minimal, and all four usage points (onEdgesChange, onConnect, handleEdgeDelete, keyboard Delete handler) are updated in sync.

One minor issue found:

• The onConnect notification message was shortened from 'Cannot connect to locked blocks or blocks inside locked containers' to 'Cannot connect to locked blocks'. Since isBlockProtected still protects nodes inside locked containers (via the parent check at block-protection-utils.ts:32), this message is technically inaccurate — users trying to connect to a block inside a locked container will get an unhelpful message suggesting only the target block itself would be the issue.

Confidence Score: 4/5

• Safe to merge with one minor notification message inaccuracy.
• The core logic change is correct and minimal — removing the source-side lock check from isEdgeProtected is the right approach to allow outbound connections from locked blocks. All four call sites are updated consistently. The only issue is the shortened notification message in onConnect that no longer mentions "blocks inside locked containers," even though that case is still blocked. This is a UX/clarity issue, not a functional regression.
• workflow.tsx line 2602 — notification message should be restored to mention locked containers.

Important Files Changed

Flowchart

flowchart TD
    A[User attempts edge operation] --> B{Operation type?}
    B --> |Add connection| C[onConnect called]
    B --> |Remove via ReactFlow| D[onEdgesChange called]
    B --> |Remove via delete button| E[handleEdgeDelete called]
    B --> |Remove via keyboard| F[handleKeyDown Delete/Backspace]

    C --> G[isEdgeProtected check]
    D --> H[isEdgeProtected filter]
    E --> I[isEdgeProtected check]
    F --> J[isEdgeProtected filter]

    G --> K{isBlockProtected target?}
    H --> K
    I --> K
    J --> K

    K --> |target is locked or in locked container| L[Block operation\nShow notification]
    K --> |target is unlocked| M{Source check?}

    M --> |OLD: also check source| N[Block if source locked]
    M --> |NEW: skip source check| O[Allow operation\nEven if source is locked]

    style N fill:#ffcccc
    style O fill:#ccffcc
    style L fill:#fff3cd

_{Last reviewed commit: b64d851}