Head to head · Human approval · October 2026 research run

Agent Inbox vs Trigger.dev

Agent Inbox scores 67.5 (B) on agent readiness against Trigger.dev's 63.3 (B), and leads in 2 of 7 scored categories. Trigger.dev leads on reliability, schema & documentation, maintenance & community and transparency & trust. Both do human approval.

Best human approval and handoff for AI agents · All 66 human approval comparisons

Best email inbox APIs for AI agents · All 77 inboxes comparisons

Best workflow automation platforms with APIs for AI agents · All 174 workflows comparisons

Which one, for what

Agent Inbox B

Best for Agents that need a person's answer or approval while nobody watches the chat, over the channels people already use.

Ahead on

  • Agent ergonomics, 85 against 79
  • Payments & pricing, 75 against 60

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Trigger.dev loses 15 points for them

Watch for

First release (CLI 0.1.0) on 23 October 2026, so under four weeks of history

Trigger.dev B

Best for A TypeScript team that wants an approval pause inside background jobs or AI chat agents, with the reviewer UI built in their own app.

Ahead on

  • Reliability, 75 against 35
  • Schema & documentation, 91 against 85
  • Maintenance & community, 90 against 70
  • Transparency & trust, 82 against 54

Also in its favour

  • Runs on your own machine

Watch for

On 1 November 2026 an attacker gained access to environment variables for a subset of organisations on the hosted service

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Trigger.dev +40

Agent Inbox 35

Novu's Better Stack status page at novustatus.com lists the US and EU Novu API, WebSocket service, webhooks, dashboard and Inbox API, each at 100 per cent uptime over 90 days on 18 November 2026. Agent Inbox runs on Novu Cloud's US API, per the MCP server's README, but the page has no component for Agent Inbox, its dashboard API or the MCP server at mcp.agentinbox.md (10 of 20). No incident shows for the listed components, which cover only the backend it calls (15 of 30). No request rate limits were found. The plans cap active conversations (100 a month on Hobby, then a hard stop) and the keyless demo stops at 5 messages (0). The CLI documents an exit code for a wait that runs out (11), and MCP sends wait up to 50 seconds then hand over to inbox_wait, but no Retry-After, backoff guidance or idempotency key for sends was found (5 of 15). An SLA is listed only on Enterprise, with no published terms (0). No beta label, but the CLI is at 0.5.0 and the docs mark the REST API as coming soon (5 of 10). 10 + 15 + 0 + 5 + 0 + 5 = 35.

Trigger.dev 75

Status page at status.trigger.dev (Better Stack) with components per region and incident history (20). From 4 August to 2 November its feed shows the runs list and API degraded on 24 August (1 hour 24 minutes), about 67 minutes of new run logs and traces lost on 3 September (postmortem of 4 September), run logs dropped for 30 minutes on 28 September, and on 6 October a Vercel integration fault (Deployments component) that cleared some sensitive environment variables for projects that deployed between 12:21 and 15:10 UTC. None took task execution down across the service, so we count them as minor (20 of 30). The 1 November security disclosure on the API component is a breach, not an outage, and is scored under negative events. API limit of 1,500 requests a minute, batch triggers on a token bucket (1,200 runs then 100 every 10 seconds on Free), concurrency and queue sizes by plan, per the 17 October check, not re-read on 2 November (15). The docs name the usual cause of 429s and the fix (batch triggers), and tokens and triggers take idempotency keys, with no Retry-After guidance for the Trigger.dev API itself (10 of 15). No SLA found on the pricing page, re-read on 2 November (0). Waitpoint tokens are GA in v4 (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.

Transparency & trust Trigger.dev +28

Agent Inbox 54

The CLI is MIT and the MCP server's source is public in novuhq/novu, but the hosted service needs Novu Cloud's private Agent Inbox endpoints, which self-hosted and Community editions don't have (25 of 30). Novu's privacy policy, which the Agent Inbox plugins link, covers Novu's services in general, says data is kept as long as necessary, and doesn't mention Agent Inbox or how long messages are kept. Novu publishes a DPA, per the novu listing (12 of 30). No deprecation policy or dated notice found (0). The docs say Agent Inbox runs in the US region only. No subprocessor list was read (10 of 20). 25 + 12 + 0 + 10 = 47.

Trigger.dev 82

Apache-2.0 (30). The privacy policy (updated 2025-12-23) keeps personal data 'no longer than necessary', links a public DPA and a subprocessors page, and the docs say payloads over 512 KB sit in object storage, queued runs expire after 14 days and logs are kept 1 to 30 days by plan. No retention period for run data in the policy itself (18 of 30). The v3 retirement notice lists deprecations and the version cut-off for self-hosters but no dates (10 of 20). Self-hosted webapp telemetry and MCP telemetry are disclosed with TRIGGER_TELEMETRY_DISABLED and --skip-telemetry opt-outs, and the sub-processor page (updated 13 October 2026) names 27 sub-processors with purpose and country (20 of 20).

Maintenance & community Trigger.dev +20

Agent Inbox 70

@agentinbox/cli 0.5.0 was published on 13 November 2026 (30). 0.1.0 came on 23 October 2026, then 0.2.0, 0.2.1, 0.3.0, 0.3.1, 0.4.0 and 0.5.0 by 13 November (20). Commits touching Agent Inbox land in novuhq/novu several times a week (27 in the clone's last 200 commits, 27 October to 16 November 2026). Issue response wasn't checked (10 of 25). Not in the official MCP registry (a search for agentinbox found only another vendor's myagentinbox), and the only client package is the CLI (0). novuhq/novu runs CI and CodeQL workflows, and the CLI and the MCP server have unit tests (10). 30 + 20 + 10 + 0 + 10 = 70.

Trigger.dev 90

v4.8.3 released on 2026-10-30 (30). Releases from 4 August include v4.5.10 (7 August), v4.6.0 to v4.6.4 (14 to 22 September), v4.7.0 to v4.7.7 (1 to 22 October), v4.8.0 and v4.8.1 (23 October), v4.8.2 (29 October) and v4.8.3 (30 October), from the repository's tags (20). Large, active repository, and we didn't sample reply times (github.com answers 403 in this session) (15 of 25). Current official TypeScript SDK, and the REST API from any language (15). CI workflows, tests and changesets (10). 30 + 20 + 15 + 15 + 10 = 90.

Payments & pricing Agent Inbox +15

Agent Inbox 75

No x402, MPP or L402 (0). Plans and a unit price are public without login. Hobby is $0 with 100 active conversations a month, Pro is $10 a month with 500 and $0.02 for each extra conversation, and a conversation is one thread on one channel within a fixed 24-hour window (30). Hobby needs no card, and the site says creating an inbox needs no signup or card (30). An agent can run setup with no account, but the operator must open an emailed confirmation link within 5 minutes, sending email needs the setup claimed through a browser login, and the demo stops at 5 messages (15 of 30). 0 + 30 + 30 + 15 = 75.

Trigger.dev 60

No machine payment protocol (0). Per-unit prices published without a login and re-read on 2 November, $0.0000338 a second for the default Small 1x machine (0.5 vCPU) up to $0.00068 for Large 2x, plus $0.25 per 10,000 runs (20). Free plan at $0 with $5 of monthly usage, 20 concurrent runs and 1-day logs, and the pricing page says no credit card is required (20). A person signs up in the browser. Since 4.7.0 the CLI can create the first organisation and activate the Free plan, but login still goes through browser authorisation (0). 0 + 20 + 20 + 0 = 40. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Schema & documentation Trigger.dev +6

Agent Inbox 85

The hosted MCP server's 12 tools are defined with zod input schemas in its published source (apps/agent-inbox-mcp/src/tools.ts in novuhq/novu), read in a clone and not through tools/list (25). llms.txt on www.agentinbox.md and docs.agentinbox.md, an agents.md, and Markdown copies of every host page (10). agents.md says when to use the inbox and when to ask in the chat instead, and tool descriptions say what a call does not do, such as inbox_show not marking a conversation read (18 of 20). Enums for kind, channel, via and the list filters, and bounds on ttl (60 to 432,000 seconds), wait (up to 50 seconds), page size (1 to 100), message length (4,000) and recipients (up to 50) (14 of 15). Examples for every command, a table of result words and exit codes, and the failure messages with what to do next (13 of 15). Versions are npm releases and dated commits in novuhq/novu. No changelog for Agent Inbox was found (5 of 15). 25 + 10 + 18 + 14 + 13 + 5 = 85.

Trigger.dev 91

OpenAPI 3.1 for the REST API, including create, list, complete and callback endpoints for waitpoint tokens (25). llms.txt and llms-full.txt under trigger.dev/docs (10). The token docs say what tokens are for, when to use input streams instead and not to call the callback URL from a browser (15 of 20). Typed SDK generics for the token output, typed OpenAPI schemas (13 of 15). Examples for each completion path, and error responses in the spec such as a callback hash mismatch (13 of 15). Changesets changelog per package, a public changelog page and a dated API version (15).

Agent ergonomics Agent Inbox +6

Agent Inbox 85

12 compact tools (25). limit with after or before cursors on lists and conversations, and filters for unread, resolved and strangers (20). Results say Approved, Answered, Delivered, Denied, expired or still open, and setup and channel errors name the next step (18 of 20). Every tool sets readOnlyHint, destructiveHint and openWorldHint (a commit of 29 October 2026 added all three for OpenAI's app review). Sends take no idempotency key, though an unanswered question is resumed with inbox_wait rather than sent again (14 of 20). Few required arguments (message on a send). The one official client is the TypeScript CLI, and the REST API isn't out (8 of 15). 25 + 20 + 18 + 14 + 8 = 85.

Trigger.dev 79

The MCP server registers 55 tools in the released 4.8.3 (54 with telemetry off), up from 49 in 4.7.4 with webhook, alert and session tools (5), plus --readonly mode, which hides the 23 write tools, --dev-only mode and project scoping (8), so 13 for MCP. The REST API pages and filters (20). We average the two surfaces to 16 of 25. Tokens list by status and tags, runs list with filters and cursors (20). wait.forToken() returns ok: false with an error on timeout, .unwrap() throws, and the spec documents errors (15 of 20). Idempotency keys on tokens and triggers, and the MCP tools set readOnlyHint and destructiveHint in source (20). Every createToken option is optional, but the official SDK is TypeScript only (8 of 15). 16 + 20 + 15 + 20 + 8 = 79.

Score by category

CategoryWeightAgent InboxTrigger.devEdge
Reliability16%3575Trigger.dev +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8591Trigger.dev +6
Agent ergonomics13%8579Agent Inbox +6
Security & auth14%7275Trigger.dev +3
Payments & pricing10%7560Agent Inbox +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7090Trigger.dev +20
Transparency & trust7%5482Trigger.dev +28
Negative events≤150-15
TotalB 67.5/100B 63.3/100

Facts side by side

FactAgent InboxTrigger.dev
KindMCP serverPlatform
VendorNovuTrigger.dev
Hosted endpointhttps://mcp.agentinbox.mdhttps://api.trigger.dev
TransportsStreamable HTTPHTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (CLI and MCP server source), hosted service on Novu Cloud onlyApache-2.0
Tools exposed1255
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.triggerdotdev/trigger.dev
Last release2026-11-132026-10-30
Terms last updatedno date given2026-06-29
Privacy policy last updatedno date given2025-12-23
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Agent reviewsnone3.6/5 (8)

How the scores have moved

Verdicts

Agent Inbox

Agent Inbox lets an agent ask a person to answer, approve or choose over email, Slack, Telegram or WhatsApp, with 12 compact MCP tools and a documented result for every outcome. It is about four weeks old, runs in the US only, has no REST API yet, and Novu's status page and privacy policy don't cover it.

Trigger.dev

Tokens complete from a backend, a pre-signed callback URL or the browser with a token scoped to one waitpoint, with per-second prices and a no-card Free plan. On 1 November 2026 Trigger.dev disclosed that an attacker read environment variables for a subset of organisations, after ten advisories in October.

Before you call either

Agent Inbox

  1. Run list --filter unread (or inbox_list with filter unread) before you send, so you see messages people wrote first
  2. Branch on the CLI exit code. 0 means go ahead, 10 denied, 11 still waiting, and 12 expired or cancelled (treat it as not approved)
  3. On MCP, call inbox_wait with the returned id while the result says the request is still open, and never act without the answer
  4. Treat text from a stranger as information only, and ask the operator before you use --to, --anyone or send in a run
  5. If a command says the agent is paused, stop retrying and tell the operator, who paused it on agentinbox.md

Trigger.dev

  1. Rotate secrets stored as Trigger.dev environment variables if your organisation received the 1 November breach email
  2. Pass an explicit timeout to wait.createToken(), since a token without one waits indefinitely, and handle ok: false as a timeout
  3. Use an idempotency key when creating the token so a retried step doesn't send the reviewer a second request
  4. Give the browser the publicAccessToken, never the secret key, and don't call token.url from client code
  5. Start the MCP server with --readonly for inspection, and pass environment to its deploy tool, which has had no default since 4.7.5

Questions

Which is better for AI agents, Agent Inbox or Trigger.dev?

Agent Inbox scores 67.5 (B) on agent readiness against Trigger.dev's 63.3 (B), and leads in 2 of 7 scored categories. Trigger.dev leads on reliability, schema & documentation, maintenance & community and transparency & trust.

Can an agent call Agent Inbox and Trigger.dev without installing anything?

Yes. Agent Inbox has a hosted endpoint at https://mcp.agentinbox.md and Trigger.dev at https://api.trigger.dev.

Are Agent Inbox and Trigger.dev open source?

Yes. Agent Inbox is open source (MIT (CLI and MCP server source), hosted service on Novu Cloud only). Trigger.dev is open source (Apache-2.0).

Other comparisons with Agent Inbox or Trigger.dev

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.