Unblocked has become an indispensable part of our engineering workflow at Drata. What sets it apart is its deep integration with our internal ecosystem - it seamlessly connects our codebase, Slack conversations, Notion docs, Jira tickets, and GitHub activity into a unified knowledge layer.
The real magic happens when you need to understand why something was built a certain way. Instead of hunting through Slack threads, digging through old PRs, and cross-referencing design docs, Unblocked surfaces the context instantly. It's particularly brilliant at:
Following our company-specific coding patterns and suggesting code that matches our style
Tracing decision history across multiple platforms
Understanding code dependencies and architectural relationships
Helping with brainstorming sessions where institutional knowledge matters
We've also noticed it getting smarter over time, which gives us confidence in the product direction.
Congrats on the launch — love the context-first layer powering smarter AI code reviews.
Thanks, @zeiki_yu ! Context makes for great code reviews, just like if a Sr. engineer reviews your diff
We've been on the beta for this for several months, and it has been great. False positive rate is near zero, "oh wow, good catch by Unblocked" rate is at least 1 per day. It is much quieter - in the best possible way - than competing tools we've tried, it is almost always right (for us, in our codebase), and it provides actionable feedback. We were delighted when we realized it was sometimes intentionally tagging folks in comments who have worked and commented a lot on code near the change(s) under review, but hadn't otherwise been notified about a PR. This is the most thoughtful, human-friendly UX I've encountered in any AI-enabled tool.
@mfwalters thank you so much Matt, means a ton that you and the team are getting value and took time to post a note here.
We'll keep shipping great product for you and the team 😁
Unblocked
@mfwalters Thanks Matt that means a ton from someone who witnessed our progress in real-time 🥹.
@mfwalters , we appreciate the kind words and all the input and feedback your team has shared along the way!
Pulling in larger codebase/product/org context makes so much sense. Can't wait to try this out!
@mattfogel thanks! We'd greatly value your feedback on the product considering you've shipped at every scale of company size 😁
@vouchy there's tons of times at previous companies where I've worked on something that shipped only to find out that a late night Slack thread conversation had decided we should no longer do it. Teams are even more dynamic these days with claude code helping to push up PRs so getting the business logic and intent of a code change right is even more important.
@dennispilarinos Congrats on the launch Dennis! How does this handle ambiguous situations where the “right” answer depends on team context or judgment?
Hard part with AI PR review is staying quiet. Only comment when issues are found in Unblocked Code Review is a good default. How do you decide when to chime in, and can teams cap comments per PR? That's the restraint that earns trust.