nayaread
HomeFavouritesTopicsSources
HomeFavouritesTopicsSources
NayaRead links to original engineering blogs. All copyright belongs to the respective authors.
Shopify Engineering·Sep 2, 2026·11 min read48

How River takes security work from a fix to merge (2026) - Shopify

River, Shopify’s AI agent in Slack, enables autonomous vulnerability remediation, not just detection.

AISecurity
AI summarygenerated from the source article

In the first 11 days of running their security agent, Shopify cut its open dependency vulnerability backlog by 70%. 👇

Generating automated security patches is relatively easy, but actually driving them to merge without breaking production is where teams stall out. Repositories move fast. Code changes while pull requests sit in review, sibling PRs secretly resolve dependencies under the hood, and passing CI on a stale PR doesn't prove the main branch is actually secure. Engineers end up wasting hours manually checking PRs, rebasing code, and shuttling state between Slack, GitHub, and issue trackers.

Shopify built River, an AI agent living in Slack that drives vulnerability fixes all the way from initial detection to post-merge verification. Instead of just generating diffs, River operates directly inside Shopify's monorepo environment to manage the entire operational loop alongside human developers.

When a vulnerability is flagged, River groups related fixes into Slack threads and runs through a strict sequence:

Validate live state: River compares its internal work ledger against actual GitHub and tracker state. It treats its own database as unverified claims, checking if a PR was already merged or closed. It then inspects the repository head to confirm the vulnerability is still active and wasn't already fixed by another commit.

Repair on current head: If the vulnerability remains, River replays the upgrade on the latest repository head, regenerates lockfiles, and re-triggers CI builds.

Human handoff: Code owners make the final product and risk decisions, while River stays in the Slack thread to answer questions, rebase code on demand, and preserve context for future runs.

Post-merge verification: After a PR merges, River re-checks the live repository head and the resulting dependency graph to prove the vulnerability is completely gone before marking the issue done.

During its first 11 days on dependency workflows, River eliminated roughly 70% of open security issues. Two-thirds were direct merges, while the remaining third were confirmed as obsolete or already fixed elsewhere. Overall, security patches successfully passing Shopify's freshness-gated merge queue jumped from 10% to 80%.

Read original on shopify.engineering

Score breakdown

  • Technical depth51
  • Practical value30
  • Originality85
  • Writing quality82
  • Source reputation0
  • Recency86
  • External engagement0
  • On-site engagement0

NayaRead shows a summary and links to the original article. The full article is hosted on shopify.engineering.

More like this

Slack Engineering

Streamlining Security Investigations with Agents

Dominic Marks·Dec 1, 2025·9 min read
Stripe Engineering

What it feels like building with Stripe Projects

Ben Smith·May 26, 2026·2 min read
Shopify Engineering

Under the River (2026) - Shopify

May 28, 2026·13 min read
Shopify Engineering

Building an agentic harness that outlasts the model (2026) - Shopify

Jul 29, 2026·10 min read