"We move way faster than our competitors" Tey said, "thanks to CodeRabbit." "If you're building a SaaS product in today's day and age and you're not using a code-review agent like CodeRabbit, you're wasting your team's time." Need we say more? Full @dubdotco case study below 👇

Every moved line shows up as a delete on the left and an identical add on the right. The actual change is buried somewhere there. That’s why we added a semantic diff view in CodeRabbit Review.

3am Datadog alert in Slack. CodeRabbit Agent for Slack triggers off the bot message and digs in. On-call wakes up to answers, not alerts.

We've been using Agent to automate several of our engineering workflows internally. Here are 4 engineering workflows that give you an hour back.  + Hourly stale PR Nudges + Weekly Production Ship Report + Pylon -> Datadog -> PR + Monday morning catch-up

Most teams who adopt coding agents hit the same wall. The first demos look great but then production reality shows up. Sure, the model can code but the workflow needs to catch up. Here's what the workflow looks like when it actually works 👇 coderabbit.link/agentic-sdl...

Who's blocked? Which PRs are rotting? Why? CodeRabbit Agent for Slack tells you. Every hour (if you want it to).

Stop reverse-engineering PRs to review them. CodeRabbit walkthroughs now explain how the change was built and route it to the right reviewers. coderabbit.link/explainable...

Introducing Triggers. The rabbit's listening. Run automations or wire trigger-based workflows.

Within the next 12 months, most developers are not going to be looking at the code at all. At least, that's what CodeRabbit's Director of AI, David Loker, predicts. Here's why👇

Experience the full Agentic SDLC workflow, right in Slack, with CodeRabbit Agent for Slack. ✅ Pylon ticket received ✅ DataDog investigation complete ✅ Linear issue assigned ✅ Fix PR created & merged ✅ Happy customer This is just one of many use cases 😏

Most teams want a capable teammate in Slack. A teammate that takes real work off their plate without forcing everyone to pivot between tools! CodeRabbit Agent for Slack isn't just a "coding assistant," so here's how to get the most out of it 👇

Your agent writes faster than any engineer on the team. But it also starts cold every morning. It has no memory of your architecture calls, your deprecations, or the Slack thread where you decided to kill the old auth service... until now. www.coderabbit.ai/blog/policy...

Navigate your PRs easily. No matter if they include massive diffs and heavy refactors. Built for humans. Readable by agents.

Hit a merge conflict? Don't switch branches. @​coderabbitai fix merge conflict Available on GitHub and GitLab.

That cleanup pass you'll "get to later"? You won't. @​coderabbitai simplify Clean your code, without doing the refactor yourself.

We had a great time meeting everyone at GCP Next in Vegas last week! Till next time 🤙

CodeRabbit is now in Slack Your team's second brain - built for agentic SDLC workflows 60 seconds, here's how it works

Go into a project without a plan and you'll spend more time fighting problems than building. Here's the story of how we built a planning layer on Claude to fix that. 👇

The CodeRabbit team has landed in Vegas for Google Cloud Next 2026 🗣️ Come find us this Wed-Fri at booth 5302! ☁️🐰

Developers when they see the CodeRabbit Codex Plugin

The faster your engineers ship with AI, the more code review becomes the bottleneck! freee saw it coming before it became a crisis 🚨 > 54% acceptance rate on critical issues > 32.8 weeks of reviewer time saved > Reduced manual code-review burden → www.coderabbit.ai/case-studie...

When your vibe-coded app is functional but ugly af

We just shipped the PR Usage-Based Add-On so you can keep shipping without worrying about hitting limits! Use more when you need it. Pay only for what you use. Opt in from the CodeRabbit dashboard.

How do you scale an open-source project to over a million downloads a day? 🤔 We sit down with Bill Easton, core maintainer of FastMCP and Director of Product at Elastic, to dive deep into the Model Context Protocol (MCP) ecosystem. Full video in the comments! 👇

CodeRabbit already tells you what to fix. Now it fixes it too. @​coderabbitai autofix All unresolved findings, implemented. Commit to your branch or open a stacked PR.

Introducing CodeRabbit Ads! 🎉 To offset the growing cost of tokens, we are introducing ads to our free tier. What this means: > Free users will see ads of differing size based on the size of the PR. > Clicking an ad will give you a free review!

Join CodeRabbit’s VP of AI, David Loker, for a live look at how our Agent Orchestration works and what builders can learn from the architecture! > AI’s Hidden Quality Tax > Intent vs Execution Gap > CodeRabbit: Plan -> Code -> Review Register below!

Same PR comments every sprint? We just shipped Custom Finishing Touch recipes. Give it a try!

We just hit 200k installs on GitHub! Thats enough to fill Webley Stadium...twice! 🎉⚽

🤫

From predicting the next line to opening pull requests autonomously, the history of AI coding agents isn't just autocomplete getting smarter! It's the systematic decomposition of software engineering into machine-operable layers And we've covered the whole arc 👇

Introducing CodeRabbit Plan. Hand those prompts to whatever coding agent you use and start building!

🎙️ Our VP of AI David Loker are speaking today at GTC26! Session S81612: Practical Context Engineering; Eliminate Bugs With High-Signal AI Code Reviews → Fix 50% more bugs → Ship 50% faster → Real context-engineering playbook → 11:00 - 11:40 PDT

We benchmarked Gemini 3.1 Pro for PR review against our internal CodeRabbit baseline. Result: > Fewer comments. > Higher signal-to-noise. > But slightly fewer bugs detected. Let's get into it. 🧵

Do you catch unwanted merge changes at the speed this video got recorded? No? Then your main branch deserves better. Check out CodeRabbit Pre-Merge checks. Because “we’ll fix it in the next PR” has cost humanity enough. Keep main sacred.

Vibe coding started as Andrej Karpathy's term for surrendering to AI and watching code appear. A year later, it's become shorthand for everything AI-generated, including using AI on production environments at work. The word evolved. The risks did too.

Every AI code review benchmark published so far has one thing in common: they were all made by vendors. And somehow, their own tool always wins. That just changed with the first independent benchmark.

Open source maintainers aren't drowning in bad code. They're drowning in code that *looks* correct. Clean formatting, passing tests... but subtly wrong in ways that take 10x longer to catch than to generate. AI slop is quietly exhausting the people who keep OSS alive! 👇

Join CodeRabbit & friends tonight for a night of OpenClaw fun! 📍 Convex HQ, SF 🕙 1730 PST They'll be food, drinks, API credits, and some cool stickers! Registration link below!

Fixing code review issues shouldn’t feel like Groundhog Day. CodeRabbit’s latest QOL update, “Fix All Issues with AI Agents”, lets you resolve all PR issues in a single AI run. Copy once, run once, ship faster.

New CodeRabbit quality of life improvement dropped 🫳🏼 Fixing PR issues with AI agents shouldn’t take 20 copy-pastes. Now it doesn’t. Copy one prompt → run the agent → done. Less friction. More shipping. 🐰

In a galaxy not that far away...

There’s a big gap between “add dark mode” tickets and the real work of tracing files, patterns, and past decisions in your codebase. CodeRabbit Issue Planner turns Linear issues into reviewable Coding Plans rooted in your actual repo! 👇

Developers are dead? That’s what a lot of people are saying these days. But AI coding agents aren’t killing software engineering. They’re killing the version of the job centered on typing syntax all day. We wrote about it.

When AI code goes sideways, it’s rarely because the model “wasn’t smart enough.” It’s because the agent had no idea what you really wanted, so it confidently optimizes the wrong thing for your product and codebase. That’s why we built CodeRabbit Issue Planner!

Open source quietly powers everything from your terminal to your favorite frameworks, yet maintainers are often underfunded. In 2025, CodeRabbit distributed over $600,000 directly to OSS maintainers, and we’re just getting started!

We're excited to be sponsoring a fireside chat at ClawCon with the ClawFather himself, @steipete! Bring your setup, swap workflows, and see how other folks are putting their 🦞 to work! 📍Frontier Tower, 995 Market St, San Francisco 📝 Register through the link below!

Take one day to build a better version of the software you already use! Better GitHub? Better Slack? Better Mail? Better...CodeRabbit? (😬) Join us and a bunch of our friends at Y Combinator SF for Better Hack! 📍 Feb 7, 9am–9pm. 🚨 Limited to 100 people / 25 teams!