Founder at https://xitter.cf/t.co/UUeydPyIis (YC X25) AI code reviews for complex codebases

San Francisco
Joined July 2013
How @better_auth uses @cubic_dev_ to keep 130 k weekly deployments secure.
5
4
28
5,286
🚀
this but it’s @cubic_dev_ running for free on my @abodefyi open source repo with claude auto actioning every comment can truly let it rip
3
250
OpenAI 🤝 Browser-use docs.browser-use.com/open-so…
Browser and computer use got waaaay easier in the latest @OpenAIDevs Python and Node.js SDKs 🧵
1
3
1
20
3,887
i gave 3 AI code reviewers the same 5 bugs. all of them were cross-file bugs. Qodo: 5/5 Cubic: 5/5 CodeRabbit: 4/5 the interesting part: the bug was often in one file, but the damage showed up somewhere else. so just reading the changed code isn’t enough. here’s what i found ↓
21
2
25
659
🧊
What I like about the AmpCode experience: - it notes the CI checks - it accounts for the Cubic PR review bot - calls out the changes in brief - presents the significant code change to draw attention to for a human - adds tests this should be the baseline for any coding agent, fr
1
148
🧊
We ran a very thorough comparison of a custom solution with a bunch of skills in a remote Claude code env and Cubic on over 100 PRs Cubic caught incomparably more issues by a mile
3
226
Paul retweeted
We ran a very thorough comparison of a custom solution with a bunch of skills in a remote Claude code env and Cubic on over 100 PRs Cubic caught incomparably more issues by a mile
1
2
2
3
508
we merged 4x more commits last week than we did a month ago (thanks opus 5.5). our dev setup and CI couldn't keep up, so we reworked both: • lint: 4x faster • memory per agent session: half • CI setup step: 50x faster • CI type check: 10x faster we often run 10+ agents at once locally, and each one runs its own lint, type checks and tests. from time to time, several agents would run these at the same time and block each other. a 64 GB MBP would run out of memory and crash. so most of the work was making things faster and lighter, or getting rid of them we revamped our local setup to make checks faster and use less memory: • oxlint and oxfmt instead of eslint and prettier, and type-aware lint only runs in CI. linting a changed file went from over 10s to a few seconds • a hook formats every file an agent edits, so agents don't have to take a turn to format it • typescript 7's native LSP instead of tsserver. each agent session uses about half the memory • agents run one check script after each change. it installs missing packages and env files first, then lints, type-checks and runs the tests for what changed • only 3 type checks or big test runs can run at once across all worktrees, so they don't slow each other down we revamped our CI to make it faster: • every CI job installs pnpm before it can install our packages. the standard github action for this (pnpm/action-setup) installs pnpm through npm, and that hung for 3-7 min on most of our test jobs. we now download the pnpm binary from github releases, which takes about 4s • our type check needs about 9.5 GB of memory. github's standard runners have 8 GB, so it ran out of memory and took 206s. on a 16 GB machine it takes 20s • vercel builds type-check with typescript 7 (85s to 45s), and previews only build for PRs that change the database if you're running lots of agents, look at what they're waiting on. for us it was mostly lint, type checks and CI setup
43
29
9
685
78,037
Started a trial of @cubic_dev_ on Friday. Easily the most capable code review tool we’ve tried. And pretty predictable pricing tool. Purchasing for the whole team on Monday shall be an easy decision to justify.
1
2
3
121
100% of the PRs at @daytonaio are agent-generated. And no, it hasn't affected the code review cycle one bit.
8
2
46
7,066
This has veen been a game-changer for us and our beta-testers. Excited to have it out in the world
GitHub notifications are easy to miss, so cubic now brings the PR updates that matter into Slack: → reviews, comments and cubic's results, as they happen → a private channel for any PR, with its author and reviewers → a heads-up when the overnight scan finds a bug in your code
7
861
Men only want one thing... Optimizing latency of AI agents
8
2
4
105
28,063
Nobody at @daytonaio writes code manually anymore. But everyone commits PRs.
15
2
2
63
6,158
We couldn't get @Steven_Ballmer to launch @simdotai's latest features, so I had to do it myself...
4
6
52
4,272
I love seeing @cubic_dev_ customers winning
Introducing Alexandria. We raised a $75M Series B led by Smash Capital to build the world’s largest knowledge library for superintelligence. Supercharge your agents with instant access to the most powerful data sets & providers. firecrawl.dev/alexandria
1
1
23
1,338
Introducing Superset for iPhone. Remotely control agents running on your computer. Review and ship PRs from your pocket.
85
41
54
477
291,623
Introducing Sim Search Agents can now use your credentials to build an agentic knowledge graph to do your high-context work. Full context building and adaptive learning. Live right now in Sim!
71
102
19
467
102,261
Paul retweeted
introducing ═══════════ 𝚌𝚏𝚘.𝚊𝚒 ═════════════ tl;dr 1/ runway is now cfo.ai 2/ you can hire @arithecfo and he can start TODAY 3/ you can give @arithecfo a test drive by replying to this thread with any ridiculous thing you want him to model for you, and he'll come back to you with a beautiful, detailed, fully wired financial model ... in 30 minutes or less now, story time: 🧵 1/n
161
64
28
683
289,693
Paul retweeted
Introducing cross-repo reviews in @cubic_dev_. During beta, customers fixed over 1,200 bugs flagged by cross-repo reviews. cubic checks how changes affect related repos, using the relevant branch or open PR. Findings appear in your original review. Available on every plan.
2
1
7
415
Replying to @adrianthedev
I use three Agentic PR reviewers all as reviewers that my agent then addresses. If I could only choose one it would be Cubic. @cubic_dev_ @QodoAI @devindesktop
1
2
5
174