Skip to content
RRAECHLY
WarmupRead only

warmup_stats

Warmup overview: per-mailbox progress, thread and reply counts, pool accounts.

Say this to your assistant

Show warmup stats and point out any mailbox where replies are not coming back.

What it does

The honest scoreboard. For each mailbox you get where it is in the ramp, how many warmup threads went out and — the number that actually matters — how many replies came back in.

Sent-versus-received is the diagnostic. A mailbox showing high sends and zero inbound is not warming; it is talking to itself. In practice that pattern means the inbound path is broken, and no amount of additional volume will fix it.

This is also where you confirm the warmup pool is healthy. Warmup needs at least one active pool account to have anywhere to send.

Read it weekly rather than daily. Warmup progress is slow by construction, so day-to-day movement is noise, and checking constantly tends to produce the impulse to intervene — usually by raising a limit, which is the one action guaranteed to make things worse. Week over week, the reply count should be climbing alongside sends.

Parameters

None. Call it with an empty object — there is nothing to configure.

* required · Maps to GET /api/warmup/stats

What comes back

Per-mailbox warmup progress, thread and reply counts, and pool account status.

The thing people get wrong

Sends going up is not progress. Replies coming back is progress — a rising send count with a flat reply count is the signature of a broken inbound path.

Use it with

More warmup tools

See all 22 tools and the connection string on the MCP server page.

Run warmup_stats yourself.

Connect the MCP server to Claude, Claude Code or Cursor and the whole toolset shows up in the conversation.