Trigger.dev

Four ways to receive (`.𝚠𝚊𝚒𝚝`, `.𝚘𝚗`, `.𝚘𝚗𝚌𝚎`, `.𝚙𝚎𝚎𝚔`). Backend and frontend senders. All typed end to end. Read the full changelog here: trigger.dev/changelog/inpu…

Send from React in a few lines. `𝚞𝚜𝚎𝙸𝚗𝚙𝚞𝚝𝚂𝚝𝚛𝚎𝚊𝚖𝚂𝚎𝚗𝚍` wires up any button, form, or chat input to a running task. Typed all the way from the click to the task.

You can now chat with your running tasks. Input streams: send typed data INTO a @triggerdotdev task while it's executing. - Cancel signals for AI generations - Course-correct agents mid-run - Approval gates that free compute while they wait Shipped in v4.4.2 ↓

. @mattaitken from @triggerdotdev talking durable agents - @aiDotEngineer Europe

📝Detailed write up of how we ditched git worktrees in favor of @gitbutler and how we use it with agents here: trigger.dev/blog/parallel-…

That's March. Full changelog here: trigger.dev/changelog

3. Plus 10 Claude Code tips most people miss. --𝚏𝚘𝚛𝚔-𝚜𝚎𝚜𝚜𝚒𝚘𝚗 for context pre-warming. --𝚏𝚛𝚘𝚖-𝚙𝚛 to resume the agent that wrote your PR. ! for inline shell output. 𝙲𝚝𝚛𝚕+𝙶 to compose prompts in your editor. trigger.dev/blog/10-claude…

In case you missed it, here are some of the things we shipped in March: → Native @vercel integration → Query & Dashboards (ask in English, get SQL) → 5x throughput from a Bun rewrite → New MCP tools, TTL defaults, 𝚜𝚢𝚗𝚌𝚂𝚞𝚙𝚊𝚋𝚊𝚜𝚎𝙴𝚗𝚟𝚅𝚊𝚛𝚜 Full recap ↓

@AdelDodas @Hookdeck @AnthropicAI

@triggerdotdev @Hookdeck @AnthropicAI At this point you don't need Zapier or any other automated workflows, you can literally build it on Trigger.

GitHub sends a webhook. 60 seconds later, Claude has reviewed your PR diff, labeled your issue, and posted a deploy summary to Slack. Built with @HookDeck + @triggerdotdev + @AnthropicAI↓

@HookDeck wrote the full walkthrough: both routing patterns, deployment scripts, the Hookdeck transform code, everything. Fork it and have AI-powered GitHub automation running in ~15 minutes: hookdeck.com/webhooks/platf…

Two routing architectures: One Hookdeck connection → router task dispatches child tasks via 𝚝𝚊𝚜𝚔𝚜.𝚝𝚛𝚒𝚐𝚐𝚎𝚛() with 𝚒𝚍𝚎𝚖𝚙𝚘𝚝𝚎𝚗𝚌𝚢𝙺𝚎𝚢: ${𝚍𝚎𝚕𝚒𝚟𝚎𝚛𝚢𝙸𝚍}-${𝚝𝚊𝚜𝚔𝙸𝚍}. Simple. Or: three connections filtering on 𝚇-𝙶𝚒𝚝𝙷𝚞𝚋-𝙴𝚟𝚎𝚗𝚝 header → tasks directly. Per-event retry policies, independent pause/replay, separate delivery metrics.