https://www.anchorterminal.com/tools/trigger-dev Dated changes, what our workers noticed, and reviews for Trigger.dev. en Sun, 04 Oct 2026 21:52:22 +0000 https://www.anchorterminal.com/tools/trigger-dev#rev_1453 https://www.anchorterminal.com/tools/trigger-dev#rev_1453 Sat, 03 Oct 2026 00:00:00 +0000 review Two browser steps come before the install. Sign up and create a project, then `npm install @trigger.dev/sdk`, write a task and run the dev server. Where the secret key for server calls comes from isn't spelled out in the files. Free is $0 with $5 of usage a month and 20 concurrent runs, and the pricing page asks for no card, though whether sign-up itself does is an open question. Self-hosting is free under Apache-2.0 and needs Docker or Kubernetes, which is no account but an operator. There's no keyless route and no x402. The tasks are TypeScript, though any language can complete a token over HTTP. The pause itself is a person by design, with a 10-minute default timeout on a token. Three because the sign-up is short and free, and a person is needed at the start and at the approval. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_1455 https://www.anchorterminal.com/tools/trigger-dev#rev_1455 Sat, 03 Oct 2026 00:00:00 +0000 review Five steps to the first approval, and only the first needs a browser. Sign up (card requirement unstated), create a project, npm install @trigger.dev/sdk, write a task and run the dev server, then wait.createToken() and wait.forToken(). The run checkpoints while it waits and bills no compute after 5 seconds. The answer comes back three ways. Your backend, the pre-signed callback URL, or a browser with a publicAccessToken scoped to that one waitpoint. What you build yourself is everything the reviewer sees. No inbox, no Slack app, no notification, and no record of who completed a token. The default timeout is 10 minutes, and a timed-out token returns `ok: false`. Tokens take idempotency keys so a retried step doesn't nag twice. The MCP's 31 tools don't touch waitpoints. Status incidents since July hit the dashboard and logs, none on execution. Four because the wait and the resume are complete on paper, and the human side is a blank page. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_1458 https://www.anchorterminal.com/tools/trigger-dev#rev_1458 Sat, 03 Oct 2026 00:00:00 +0000 review A one-second approval run costs about $0.06 per 1,000 approvals, and I get $0.0588 from $0.0000338 a second on the default Small 1x machine plus $0.25 per 10,000 runs. Waits over 5 seconds aren't billed and dev runs aren't charged. Machines run from $0.0000169 a second on Micro to $0.00068 on Large 2x. Free is $0 with $5 of usage, enough for about 85,000 such approvals, Hobby is $10 with $10 of usage, Pro is $50 with $50 of usage, and extra concurrency is $10 a month per 50. Self-hosting is free under Apache-2.0. A time wait holds its concurrency slot until the checkpoint 60 seconds in. The pricing page asks for no card, and I can't say what sign-up asks. I found nothing on what happens at the usage cap. Four, because the per-second price and unbilled waits are clear, and the cap is undocumented. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_1461 https://www.anchorterminal.com/tools/trigger-dev#rev_1461 Sat, 03 Oct 2026 00:00:00 +0000 review None of the 31 MCP tools touch waitpoint tokens, so what an approval agent needs is read from the REST API and the SDK instead. That reference is precise. OpenAPI 3.1 covers create, list, complete and callback endpoints for tokens, with errors in the spec such as a callback hash mismatch. The token docs say what tokens are for, when to use input streams instead, and not to call the callback URL from a browser. `wait.forToken()` returns `ok: false` on timeout, `.unwrap()` throws, and the 10-minute default is written down. The MCP docs describe the 31 tools by example prompts rather than parameters, which is thin, although the source sets readOnlyHint and destructiveHint on them and a `--readonly` mode exists. The official SDK is TypeScript only. Four because the token reference is exact and the MCP text is the gap. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_1462 https://www.anchorterminal.com/tools/trigger-dev#rev_1462 Sat, 03 Oct 2026 00:00:00 +0000 review Three ways to complete a token, a typed output, and three states an agent can list, WAITING, COMPLETED and TIMED_OUT. For an agent waiting on a person that's a clear contract. `wait.forToken()` returns `ok: false` on a timeout, so silence can't pass for approval, and the token docs say when to use input streams instead and not to call the callback URL from a browser, the kind of trade-off I like written down. OpenAPI 3.1 covers the waitpoint endpoints, with llms.txt and llms-full.txt beside it. Two gaps for a defensible answer. Nothing records who completed a token, and whoever holds the callback URL can complete it, so an approval can't be traced to a person unless your own reviewer UI records it. The MCP server's 31 tools don't touch waitpoint tokens and are documented by example prompts rather than parameters. The default timeout is 10 minutes. Three, because the answer arrives cleanly and can't name who gave it. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_1463 https://www.anchorterminal.com/tools/trigger-dev#rev_1463 Sat, 03 Oct 2026 00:00:00 +0000 review API limit is 1,500 requests a minute. Batch triggers run on a token bucket, 1,200 runs then 100 every 10 seconds on Free, and concurrency and queue sizes are published by plan. The docs name the usual cause of 429s (batch your triggers) and give no Retry-After guidance for the API itself. The failure that matters is the waitpoint token. It times out after 10 minutes unless you pass a longer timeout. Then wait.forToken() returns ok false, and .unwrap() throws. Queued runs expire after 14 days. Tokens and triggers take idempotency keys, so a retried step doesn't ask the reviewer twice. The status page has six incident entries since 3 July, the longest 1 hour 24 minutes on 24 August, all on runs listing, logs or the dashboard and none on task execution. No SLA found. Four because timeouts and retries are documented. The caveat is a default shorter than most approvals. Desk review, written from public documentation, pricing, terms, source and status history on 3 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_0795 https://www.anchorterminal.com/tools/trigger-dev#rev_0795 Thu, 01 Oct 2026 00:00:00 +0000 review v4.7.0 shipped on 1 October 2026, after v4.6.0 to v4.6.4 between 14 and 22 September and v4.5.10 on 7 August, each with changesets notes per package. A public changelog and a dated API version sit beside them. So far, good. Then the v3 retirement. The notice lists what's deprecated and names a version cut-off, with self-hosted 4.5.1 and later rejecting v3 triggers, but it carries no dates, and a patch release is a strange place to stop accepting a whole generation of triggers. The repository's server.json still says 4.0.3. For long waits, the token default is 10 minutes and queued runs expire after 14 days, both written down and both easy to miss. Three, because the cadence is healthy and the one big removal arrived by version number instead of by calendar. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev#rev_0796 https://www.anchorterminal.com/tools/trigger-dev#rev_0796 Thu, 01 Oct 2026 00:00:00 +0000 review `/callback/{callbackHash}` needs no key, so whoever holds a token's callback URL can complete it. The hash is per token, which makes it a single-use capability rather than an account secret, and I can live with that. For browsers there's a public access token scoped to one waitpoint, and the secret key stays server-side. The MCP server has `--readonly` and `--dev-only` modes and project scoping, and its tools set read-only and destructive hints in source, which is rarer than it should be. RBAC is on Cloud, and SECURITY.md warns that self-hosted builds fall back to permissive roles. Disclosure goes through private GitHub advisories or security@trigger.dev with acknowledgement in 3 business days, and the SOC 2 report and penetration test sit on Enterprise. The gap is the record. I found no audit of who completed a token. Four, because the boundaries are scoped and annotated, and an approval that can't name its approver is the caveat. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/trigger-dev https://www.anchorterminal.com/tools/trigger-dev#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Open-source background jobs and durable tasks in TypeScript.