Back to Signal Feed
CodeTracked since May 21, 2026

Open SWE Review now requires explicit repo enablement before reviewer webhooks run

The PR introduces an opt-in repository gate for Open SWE Review: a new `enabled_review_repos` list in the LangGraph Store is checked via `_is_repo_enabled_for_review` at reviewer webhook entry points, and only repositories that satisfy both this list and the existing env allowlist can trigger review actions.

enabled_review_reposOpen SWE ReviewLangGraph Store_is_repo_enabled_for_review

What Happened

  • The PR introduces an opt-in repository gate for Open SWE Review: a new `enabled_review_repos` list in the LangGraph Store is checked via `_is_repo_enabled_for_review` at reviewer webhook entry points, and only repositories that satisfy both this list and the existing env allowlist can trigger review actions.
  • The PR introduces an opt-in repository gate for Open SWE Review: a new `enabled_review_repos` list in the LangGraph Store is checked via `_is_repo_enabled_for_review` at reviewer webhook entry points, and only repositories that satisfy both this list and the existing env allowlist can trigger review actions.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a repository-level activation control for reviewer execution so review automation is no longer implicitly global; the new setting adds an explicit checklist gate in runtime to stop webhook review processing unless a repo is explicitly enabled in dashboard-backed config.

Why Track This

Why It Matters

Operators and repository admins will see automatic review automation go quiet in repos that are not explicitly enabled, so they can no longer assume every project gets SWE feedback by default after this change. The implementation adds a LangGraph-backed config check (`enabled_review_repos`) to every reviewer webhook chokepoint via `_is_repo_enabled_for_review`, requiring an explicit on-switch in addition to the environment allowlist; teams should monitor rollout for unintended gaps in coverage right after deployment and verify all previously reviewed repos are manually re-enabled before relying on automation.

Impact

Operators and repository admins will see automatic review automation go quiet in repos that are not explicitly enabled, so they can no longer assume every project gets SWE feedback by default after this change. The implementation adds a LangGraph-backed config check (`enabled_review_repos`) to every reviewer webhook chokepoint via `_is_repo_enabled_for_review`, requiring an explicit on-switch in addition to the environment allowlist; teams should monitor rollout for unintended gaps in coverage right after deployment and verify all previously reviewed repos are manually re-enabled before relying on automation.

What To Watch Next

  • Watch whether enabled_review_repos becomes a repeated pattern.
  • Track follow-up changes around AI Code Review.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: post_deploy_feedback_silence, manual_enablement_workflow_required.
Open Topic TimelineOpen Technical EventOpen Original Sourcepost_deploy_feedback_silence / manual_enablement_workflow_required / allowlist_config_drift / missing_backfill_for_existing_repos

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

langchain-ai/open-swe PR #1319: feat: restructure Open SWE Review tab + wire create_prs

Added per-repository enablement (`enabled_review_repos`) that is AND-combined with existing env allowlist checks to decide whether Open SWE Review webhook processing should run.