How CodeRabbit launched CodeRabbit Verify on X
Tests pull requests and user journeys before merge and release
What CodeRabbit launched

Introducing CodeRabbit Verify Don't let your users be the first test run! > PR testing: catch broken features before merge > User journeys: confirm critical flows work before each release > Tickets and fixes: get reviewed, tested fixes for reported bugs In public beta now! https://t.co/K8apcvHwcb
Transcript
How LaunchVideo.com rated the launch
LaunchVideo.com rating
About the launch
CodeRabbit Verify is in public beta for teams that already review pull requests in CodeRabbit and need to know whether the application still works after a change. Coding agents have increased the number of features and fixes faster than most teams can click through every affected workflow, and Verify is the check that runs the app before merge or release. It starts the application in an isolated sandbox prepared for the repository, uses it the way a user would (mostly in a browser, and through a CLI or HTTP API when the change calls for that), and reports bugs and blockers with reproduction steps, screenshots, and session recordings. On a pull request, Verify reads the commits along with related source, existing tests, and documentation, then writes scenarios for the behavior those changes affect. Expected results come from intended behavior, documentation, and existing test expectations. A run starts with an @coderabbitai verify comment, or automatically when a pull request opens and, if that option is on, when new commits arrive. Results are posted in a comment on the pull request. For flows the latest change may not even touch, Verify inspects the repository and proposes user journeys in plain English, covering who the user is, the goal, the steps, and the assertions that must hold. Approved journeys can be run on demand, grouped with tags, or scheduled against a branch and test environment. A failed check can be sent to CodeRabbit Agent with the finding, the tested revision, and the supporting evidence, or exported for another coding agent. Scheduled journey runs can open Jira or Linear tickets for new bugs and testing blockers, and a later run that confirms a fix can close the finding and update the linked issue. Pull request runs, full-repository journey runs, and fixes with CodeRabbit Agent are free during the public beta. Verify is available on CodeRabbit Cloud for GitHub Cloud, GitLab.com, and Bitbucket Cloud, and it tests web apps and services. Native mobile apps are not supported.
Tags
Questions
Frequently asked questions
The CodeRabbit launch post reached 1.6M views on X, with 1.1K likes, 176 reposts, 112 comments, 802 bookmarks.
CodeRabbit launched on X on November 18, 2026 with the message "Tests pull requests and user journeys before merge and release".
CodeRabbit Verify is in public beta for teams that already review pull requests in CodeRabbit and need to know whether the application still works after a change.
LaunchVideo.com rated the CodeRabbit launch 4.00 out of 5: hook 3/5, editing / creativity 2/5, copy 5/5, sentiment of launch 5/5, distribution strategy 5/5.







