Last week we shipped 9! 🚢🚢🚢🚢🚢🚢🚢🚢🚢@vercel_changes and two conferences! Too many amazing features for one tweet, but if I have to pick one 🚢to highlight it's the partners in @vercel Agent Marketplace. We are honored to be working with: @coderabbitai @CorridorSecure @SourceryAI @braintrustdata_ @onkernel @mixedbreadai @KubiksAI @chatbase @browser_use and @descopeinc vercel.com/changelog/introdu…

Sourcery's code reviews and security analysis are now available for any team building with @vercel as part of their AI Agent marketplace! See how Sourcery can help catch bugs, fix security vulnerabilities, and more for any of your Vercel projects - vercel.com/marketplace/sourc…

How does GPT-5 stack up when it comes to code reviews? We ran OpenAI's new family of models through our code review benchmark to see how they stacked up 1. GPT-5 - 8.17/10 2. Claude Sonnet 4 - 8.03/10 3. GPT-5 Mini - 7.71/10 4. GPT-4.1- 7.66/10 5. GPT-5 Nano - 6.74/10

Code quality matters to coding agents. Even if they're getting better at dealing with larger and larger codebases, more complex code makes them worse. Here are a few of out findings of how quality impacts agent performance -> sourcery.ai/blog/does-bad-co…

AI is shifting the bottleneck in software engineering — From code authors to code reviewers. 🧵

cursor with slack integration has made cursor so productive that code review has become the bottleneck.

Getting too many alerts from Sentry? Let Sentinel make it simple. Sentry can show lots of errors — and not all of them matter. @SourceryAI Sentinel is like a smart teammate. It reads every Sentry alert and tells you: What the issue is Why it happened If it’s safe to ignore And even fixes it if possible It works with Sentry, GitHub, and Slack — so everything stays in one place. When a new alert comes in, Sentinel explains it right inside the Slack thread. No more digging or guessing. It also checks your past 50 issues and keeps an eye on new ones too. Perfect for fast-moving teams that want fewer bugs and more focus. 👉 Try it: sourcery.ai/production-issue… 🔥 On Product Hunt: producthunt.com/posts/source… #BugFixing #SlackBots #GitHub #Sentry #DevTools

Too many Sentry alerts? Here's a smarter way to deal with them. Sentry can get noisy with errors and alerts. But not every alert needs your time. @SourceryAI Sentinel acts like a non-stop helper. It checks every Sentry alert and tells you: - What went wrong - Why it happened - If you can ignore it - And if it’s easy, it fixes it It connects with Sentry, GitHub, and Slack, so you manage everything in one place. New alert? Sentinel explains it directly in the Slack thread. No searching, no guessing. It also reviews your last 50 issues and keeps watching for new ones. Great for fast-moving teams that want to stop wasting time chasing bugs. Try today: sourcery.ai/production-issue… Check them out on Product Hunt: producthunt.com/posts/source… #BugFixing #SlackBots #GitHub #Sentry #DevTools

Been pretty quiet on here lately - we've been working on Sentinel - an agent that hooks in to Sentry and Slack to analyse and fix your production issues as they come in. producthunt.com/posts/source…

I just got an instant code review from @SourceryAI, and it was brilliant! It's free for open source and has a free trial for private code. Check it out sourcery.ai

A sneak peak at our new product for fixing production issues. Automatically investigate and fix Sentry issues as they pop up. Sentinel is currently in a closed beta, but we'll likely be opening up more access soon

We've been working to make our review comments smarter. They'll now adapt to positive or negative reactions you give them or the comments you make. Plus you can add in your own custom review instructions to tailor the reviews.

Did you know that code review times have a correlation with developer happiness and retention? The state of devops report shows that faster reviews have a big impact on burnout ⏬, and an increase on job satisfaction 🔼 and productivity 🔼

A quick look at a new tool we've been working on. Helping to fix CI failures where we can.

How much time per week are you spending on fixing CI failures? We're working on some extensions to our code reviews/GitHub integrations in this area and we're trying to better understand what other teams are running into

We've been playing around with an internal tool to turn daily data from commits and PRs into an automated daily standup If you want to try out an early version let us know