From the experiment

Do coding agents recommend Resend?

Resend is the most chosen email provider, taking 36% of 208 judged email sending sessions. Measured with Claude Code, Codex and Cursor.

Published September 3, 2026 Read as Markdown

Resend is the most chosen email provider, taking 36% of 208 judged email sending sessions. It was also raised as a candidate in 87 further sessions without being chosen.

This page reports what happened when Claude Code, Codex and Cursor had to solve a problem in email sending inside a realistic codebase. Not what a chat assistant says about Resend. What an agent actually installed.

The numbers

CategoryEmail sending
Sessions in the category208
Sessions where Resend was chosen74
Install share36%
Rank in category1 of 6
Codebases it won in6
Raised as a candidate, not chosen87
Chosen when considered46%
Siteresend.com

By agent

The three agents land within 7 points of each other on Resend, which is closer than most products in this experiment manage.

AgentSessionsChose ResendShare
Claude Code652031%
Codex712738%
Cursor722738%

By who was asking

Resend does much better with one kind of buyer than another. It won 45% of sessions asked as senior engineer and 0% of those asked as enterprise team.

Who is askingSessionsChose ResendShare
Senior engineer1647445%
Enterprise team4400%

What Resend was up against

The full ranking in email sending, from the same sessions:

#ProductRuns wonShare
1Resend (this page)7436%
2Postmark5727%
3Azure Communication Services Email2914%
4Amazon SES2412%
5SendGrid2311%
6Generic SMTP10%

What this means

Leading a category is a position to defend rather than a result to celebrate. In our data, leaders lose ground in exactly two situations: when the person asking is an enterprise buyer with procurement constraints, and when a competitor's documentation is easier for an agent to integrate correctly.

The defence is unglamorous. Keep the quickstart running. Keep the version current on the page. Keep the names aligned. Stay in the templates.

Where these numbers come from

The 208 sessions in email sending are part of a published set of 5,292, run with real coding agents inside realistic codebases and judged blind. The full method is on one page: how we measured this.

Every email sending run can be replayed on the board.

If you work on Resend: the judge recorded a reason for every session where it was raised and passed over. Those reasons are in the transcripts.

<!-- generated by scripts/write-data-pages.mjs -->

Common questions

Do coding agents recommend Resend?

Yes. Resend was chosen in 74 of the 208 judged sessions in email sending, a 36% install share, ranking first in its category.

Does Claude Code recommend Resend?

In 20 of the 65 sessions in email sending run with Claude Code, which is 31%.

Do different coding agents treat Resend differently?

Not much. The three agents chose it at similar rates, between 31% and 38% of their runs.

How was this measured?

Real coding agents at pinned versions were run in sandboxes inside 51 realistic codebases and asked to solve real tasks. A simulated project owner approved or questioned each recommendation before any code was written, and a judge from a model family that builds none of the agents read every session blind.

How often is Resend considered but not chosen?

It was raised as a candidate in 87 sessions without being chosen, and chosen in 74. That is a 46% conversion from considered to chosen.

Where this comes from

Armature ran 5,292 judged sessions with Claude Code, Codex and Cursor inside 51 realistic codebases, and published every run. The numbers on this page come from that work.

Read next

All library pages