Pinned Tweet
Stacked PRs from your terminal.
npm i -g mergestorm
mg stack create
mg stack submit
Two layers → chained PRs → land.
mergestorm.ai/cli
A swarm review in three tiers: Haiku agents find, Sonnet agents verify, Opus patches. Fifty or sixty agents sounds like it burns your usage, but because they are Haiku it probably costs less than a single Fable session.
57
Trust your agents more. Let them write the code and let them test it. The worst that happens is something breaks, you find out why, fix it at the core, and keep trusting them.
33
A swarm of 60 Haiku agents gives you a lot of findings, and many are not real. You need a slightly smarter model to verify them. We use about 20 Sonnet agents for that.
29
One of the best uses of a swarm review: a dead code audit. It is low stakes. When the swarm finds a path that is never called, a Sonnet session only has to verify it. Leaner code is easier for your agents to understand.
1
52
Mergestorm retweeted
This launch page took 24 seconds. One message to Breeze, and it's live at its own link. No code, no templates. Free to start.
Vortex now reviews every push on Claude Haiku 5.5: adaptive thinking, 1M-token context, live today.
mergestorm.ai
Surge is in public beta.
On-demand CI runners for GitHub Actions. They start when your jobs queue and scale to zero when CI goes quiet.
One line in your workflow. If Surge is off, jobs fall back to GitHub-hosted runners.
Minutes included with paid plans.
The one line:
runs-on: ${{ vars.CI_SURGE_RUNNER || 'ubuntu-latest' }}
Set while Surge is on, so the job runs there. Unset otherwise, so it runs on GitHub as before.
1
44
How it works and how to set it up: mergestorm.ai/blog/surge-pub…
5
We moved the review fleet to DeepSeek V4.1 Flash.
Vortex is the one to try: it runs on every push, 1 credit, no extra setting. Turn it on, open a PR, and you’ll see the pass.
How we cut over, and how to pick Flash for Tempest: mergestorm.ai/blog/review-fl…
Deploy Vortex: mergestorm.ai
2
88
If you’re using Mergestorm’s Vortex agent to review your PRs, you are already using the all new DeepSeek V4.1 Flash.
Give it a try.
🚀 Introducing DeepSeek-V4.1-Flash: smarter, faster, more efficient.
🔹 Introducing the smallest model in our new architecture family, with native visual understanding.
🔹 Designed for greater capability, faster inference, higher throughput, and scaling to larger models.
1/6
2
110
Your next PR. GPT-6 Astra in the reviewer seat. Try Mergestorm Tempest.
mergestorm.ai
GitHub might be down but Mergestorm has a mayday path built in.
Run your reviews on a local branch. You can use npm mergestorm (the mergestorm cli) to run reviews without touching GitHub.
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will... githubstatus.com/incidents/z…
We ran a blind A/B on real Vortex PR reviews: Claude Haiku 4.5 vs DeepSeek V4 Flash. Same diffs, same prompts.
72 paired runs. DeepSeek was 85.6% cheaper and posted more inlines.
Next: a 4-agent DeepSeek fleet, in parallel. Still cheaper than one Haiku pass.
Small honest study: mergestorm.ai/blog/vortex-ab…
🤖 Made with AI
Mergestorm retweeted
Elevate your PRs with Stacked Layers and Review Units so you can ship production quality code faster.
Perfect for agentic workflows like Cursor
Stacked PRs from your terminal.
npm i -g mergestorm
mg stack create
mg stack submit
Two layers → chained PRs → land.
mergestorm.ai/cli
We’re working on releasing a specialized GitHub PR stacks workflow with our proprietary review unit architecture to elevate your coding review agents.
Our agents are now able to properly review each PR within a stack, then do special seam reviews between each PRs and look at the stack as a whole.
Now you can ship a big feature a set of smaller PRs and get proper review for the whole stack and for individual PRs.








