River
- Company
- Shopify
- Approach type
- Agent
- Work
- Coding
- Human involvement
- Unknown
- Invocation
- Interactive
- Interfaces
- Slack
- Deployment stage
- Deployed
- Evidence strength
- Detailed primary
- Entry reviewed
Purpose
River is Shopify’s internal Slack agent for investigating questions and making code changes in public threads.
How it works
Representative workflow: public Slack question → collaborative investigation or code change. Research details
An employee mentions River in a public Slack channel.
River reads files, runs tests and queries, and posts findings; it can open pull requests.
Colleagues add constraints and redirect the work within the same thread.
Where people stay involved
Each scope pairs its normal attention boundary with supporting evidence. See the supervision definitions for the level mapping and limits.
Unreported: The source describes a colleague optionally redirecting a public thread, but does not require continuous steering or a universal PR approval checkpoint.
public Slack question → collaborative investigation or code change
Unknown · Level unknown
Catalog interpretation: Unclassified for public Slack question → collaborative investigation or code change; human attention boundary: unknown.
Observed in 2026
Implementation details
- Model
- Not reportedNot documented for this subject in the reviewed source.
- Harness
- An agent profile on Aquifer.
- Sandbox
- Not reportedNot documented for this subject in the reviewed source.
- Tool access
- Code, tests, data warehouse and production traces.
- Knowledge
- World monorepo, skills and shared Slack transcripts.
- Context management
- Not reportedNot documented for this subject in the reviewed source.
- Credentials
- Not reportedNot documented for this subject in the reviewed source.
- Interfaces
- slack
Validation and failure handling
Unreported: The reviewed source does not report a distinct validation process for this subject.
Reported observations
The catalog records what the sources report, with the scope and the denominator of every figure. A qualification below limits the figure it sits under.
Adoption output · Reported measurement · River: 59,918 sessions across 5,170 Slack channels in a reported 30-day period; 3,536 River-coauthored PRs merged.
59,918 sessions across 5,170 Slack channels in a reported 30-day period; 3,536 River-coauthored PRs merged.
- Reported by
- Shopify
- Scope
- River: 59,918 sessions across 5,170 Slack channels in a reported 30-day period; 3,536 River-coauthored PRs merged.
- Method
- river_sessions domain table written by River each session
The source does not report the denominator of this figure.
Lessons
Unreported: The reviewed source does not document this for the named subject.
Sources and research details
Citations link to the original publisher. Each source also keeps a preserved copy in the repository, so a changed or removed page stays checkable.
Question coverage and scope
- purpose
- Reported
- workflow
- Reported
- human involvement
- Unreported: The source describes a colleague optionally redirecting a public thread, but does not require continuous steering or a universal PR approval checkpoint.
- implementation
- Reported
- validation
- Unreported: The reviewed source does not report a distinct validation process for this subject.
- observations
- Reported
- lessons
- Unreported: The reviewed source does not document this for the named subject.
Research details for every claim on this page
- Summary
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Harness
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Tool access
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Knowledge
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Interfaces
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Receive a request
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Investigate and act
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Continue collaboratively
- Statement type
- Fact
- Provenance
- Reported
- Confidence
- High
- Confidence reason
- A linked first-party source states the claim.
- SupportsUnder the RiverPart II: River only works in the open; At scale; River is one profile
- Key observation
- Statement type
- Metric
- Provenance
- Reported
- Confidence
- Medium
- Confidence reason
- Self-reported by the source; no independent verification.
- Reported by
- Shopify
- Scope
- River: 59,918 sessions across 5,170 Slack channels in a reported 30-day period; 3,536 River-coauthored PRs merged.
- Denominator
- Not reported
- Method
- river_sessions domain table written by River each session
- Observation date
- Not reported
- SupportsUnder the RiverAt scale: recent 30-day river_sessions domain-table counts
- Operating model assessment
- Statement type
- Inference
- Provenance
- Catalog judgment
- Confidence
- Unverified
- Confidence reason
- The source describes a colleague optionally redirecting a public thread, but does not require continuous steering or a universal PR approval checkpoint.
- Observation date
- 2026
- SupportsUnder the RiverRiver only works in the open: well-going thread includes a colleague redirect and continued collaboration