Trigger.dev

This account is verified because it's an official organization on X. Learn more

@triggerdotdev

Build and deploy durable AI agents and workflows.
→ trigger.dev
→ github.com/triggerdotdev
→ trigger.dev/discord

Your codebase trigger.dev Joined November 2021

106 Following 9.2K Followers 1.6K Posts

Latest posts 5

Trigger.dev @triggerdotdev 2d

We’ve published our report on the November 1st security incident
trigger.dev/blog/security-…

trigger.dev Security incident report: Sunday November 1st | Trigger.dev On November 1, 2026, we became aware of a security incident which impacted some of our customers. This included unauthorized access to environment variables.

Trigger.dev @triggerdotdev 6d

There has been a security incident at Trigger.

We have emailed the owners of all impacted accounts.

We’ll be providing more information but for now the focus is on giving the impacted account owners what they need to mitigate.

trigger.dev/blog/security-…

Trigger.dev @triggerdotdev Oct 30

We upgraded our Bun runtime to Bun 1.4 and took Node.js out of the image entirely.

Memory per container dropped 41%, cold starts are 18% faster and the image is 25% smaller.

@jarredsumner and the @bunjavascript team are still cooking.

tgr.dev/uv7Lfki

trigger.dev The Bun runtime, now even bunnier | Changelog Bun 1.4.4, a 25% smaller deploy image, checkpoints that work end to end, and a retirement date for the old Bun runtime.

Trigger.dev @triggerdotdev Oct 30

We just added two new CLI commands to help agents build webhooks with Trigger while keeping webhook secrets out of their context

Two terminal commands from Trigger.dev 4.8.3. First: a Stripe CLI command creates a webhook endpoint, pipes the output through jq to extract the secret, and pipes it into npx trigger.dev@latest webhooks set-secret stripe --env prod. Second: npx trigger.dev@latest webhooks generate-secret github --env prod --to-env GITHUB_WEBHOOK_SECRET.

Trigger.dev @triggerdotdev Oct 29

This week we added webhooks support for the second time. @maverickdotdev wrote up the technical choices we made
tgr.dev/IJuegql

trigger.dev How we built webhooks (the second time) | Trigger.dev Provider verification as data instead of code, filter strings that TypeScript checks for you, and a delivery pipeline that stays durable from the provider's request to your run.