Loading video...

Video Failed to Load

Go Home

Announcing the latest release from Qodo: Modern engineering runs across hundreds of repos, dozens of teams, and AI that writes code faster than anyone can review it. Today, Qodo releases features built for these teams. - Cross Repo Review: Qodo now maps dependencies across your repos and catches breaking...

633,155 views • 3 months ago •via X (Twitter)

11 Comments

Qodo's profile picture
Qodo3 months ago

Read the full break down in a blog post here:

Nikki Siapno's profile picture
Nikki Siapno3 months ago

Cross-repo reviews makes a lot of sense. Great release!

Tech with Mak's profile picture
Tech with Mak3 months ago

Congratulations to the team on shipping these fantastic features, really impressive work!

Raul Junco's profile picture
Raul Junco3 months ago

This is how we get real engineering Context.

Petar Ivanov's profile picture
Petar Ivanov3 months ago

Yesss, this new feature by Qodo is a banger!

Shrey shah's profile picture
Shrey shah3 months ago

Amazing work team!!

Sofia 🌷 💙 ❤️'s profile picture
Sofia 🌷 💙 ❤️3 months ago

Facts!

Shamim Hossain's profile picture
Shamim Hossain3 months ago

That’s great

Lily Anderson's profile picture
Lily Anderson2 months ago

Looks like a powerful update for engineering teams. Cross-repo reviews and dependency awareness can make AI-assisted code reviews much more reliable at scale. 🚀

Victoria Blake's profile picture
Victoria Blake3 months ago

Impressive update from the Qodo team. We'd love to collaborate and help showcase these AI-powered engineering innovations to a broader developer and tech audience. Let's connect. 🚀🤝

安叫兽|Bird🕊️ 🔶 BNB's profile picture
安叫兽|Bird🕊️ 🔶 BNB3 months ago

跨库依赖这块真是大团队的痛点了

Related Videos

A DEVELOPER FOUND SEVEN WAYS TO TAKE DOWN A PRODUCTION DATABASE THAT ALL LOOK EXACTLY LIKE NORMAL, INNOCENT CODE AND ALMOST EVERY TEAM IS SHIPPING AT LEAST ONE OF THEM RIGHT NOW 17 minutes from Josh Berkus, one of the people who actually maintains PostgreSQL, walking through the quiet mistakes that turn a healthy database into a 3am outage. -> The moment it lands, you realize none of these are exotic attacks. They're ordinary-looking decisions -- a query that locks a table, a connection that never closes, a setting no one ever questioned -- that work perfectly until the day they don't, and then they take everything down with them. The scary part isn't that the database breaks. It's how normal the code looks right up until it does. A query that runs in 5ms on your laptop and 5 minutes on prod. A migration that silently locks the whole table. A connection pool that runs dry the moment real traffic shows up. Every one of them passed review. Writing SQL that runs was never the hard part -> writing SQL that survives production is. And now that an AI agent is generating and firing queries at your real database faster than anyone can read them, every one of those seven landmines is one autocomplete away -- and the only person who can stop it is the one who already knows where they're buried. Your database doesn't go down because someone attacked it. It goes down because something that looked completely normal finally caught up with it. Save and Watch it today. You'll see the next outage coming before it lands ↓

slash1s

22,268 views • 4 months ago

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 views • 7 months ago