Inngest vs withHuman

Inngest

Waits are durable and cost nothing while suspended, with runs up to 30 days on Free and 366 on Business. No reviewer inbox, Slack app or email, so the human side is your code.

withHuman

The approval API is small and carefully specified, with a public OpenAPI 3.1 document, mandatory idempotency keys and agent credentials that can never approve. The service is in early access under its own terms, with no status page, published rate limits or changelog, and the open-source repository the site links to returned 404 on 8 October 2026.

Inngest

1. Use step.waitForSignal() when one run waits for one answer, and waitForEvent only when one answer resumes many runs
2. Register the wait before you send the approval request, or check the external state first, since early events are missed
3. Use a unique approval ID per tool call and match on it, so parallel approvals resolve independently
4. Treat null or undefined as a timeout and decide on purpose whether that rejects, approves or escalates
5. Set an event id when sending the answer, so a retried send is dropped within 24 hours

withHuman

1. Send an Idempotency-Key header on POST /api/aap/v1/requests. The call answers 400 without one
2. Read the decision with GET /api/aap/v1/requests/{id}?wait=30s and repeat while status is pending. wait is capped at 30 seconds
3. Set timeout between one second and seven days, and treat expired and cancelled as a refusal
4. Start an approved call within five minutes of decided_at, because the decision carries an expires_at
5. Cancel a request when you stop waiting, so reviewers stop seeing it