fix(forking): hide satisfied dependent configuration - #6723

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 15, 2026 5:13am

PR Summary

Medium Risk
Changes fork-sync UI gating and in-session reconfig state that feeds the sync payload; behavior is well covered by tests but incorrect gating could block sync or send stale dependent IDs.

Overview
Fork sync only surfaces dependent selectors that still need user action, instead of listing every dependent whenever a resource is mapped.

When the parent mapping is unchanged and stored values are already valid, satisfied required and optional dependents stay hidden; workflows that only use the resource with nothing to configure still appear in a muted “nothing to configure there” note. If a child still needs a value, upstream provider fields in the same block are shown too so the user can see and change the scoping context.

Re-picking a provider now clears every transitive descendant in-session (empty overrides), not just direct children, so stale stored IDs do not leak into the sync payload after a parent in the chain changes.

Dependent selector context during collection now respects persisted canonical modes (e.g. advanced projectId), so downstream selectors query with the active value rather than a stale basic-mode field.

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

Greptile Summary

The PR reduces workspace-fork configuration noise while preserving selectors needed to configure required dependent chains.

• Classifies dependent selectors as actionable based on parent resolution, mapping changes, copy state, and missing required values.
• Retains transitive context providers whenever a descendant requires configuration.
• Applies the filtered presentation to top-level block fields and fields nested under Agent tools.
• Adds focused tests for selector visibility and transitive provider inclusion.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Dependent field] --> B{Parent resolved?}
  B -- No --> H[Hide selector]
  B -- Yes --> C{Parent changed or copied?}
  C -- Yes --> S[Show selector]
  C -- No --> D{Required value missing?}
  D -- Yes --> S
  D -- No --> H
  S --> P[Include transitive context providers]

_{Reviews (2): Last reviewed commit: "fix(forking): keep dependent chains conf..." | Re-trigger Greptile}

bugbot run

@greptile

@cursor review