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

Your codebase
Trigger.dev retweeted
This was one of the first PRs I opened after joining @triggerdotdev. Apart from saving a ton of CPU on our servers, the upgrades to TS7 and Zod4 have made our typechecks nice and speedy. Theoretically lower LSP memory usage too, but these days I don't keep neovim open long enough to find out...
We (finally) upgraded to Zod 4.5 (from 3.x!) and our worker CPU demand plummeted, our batch throughput increased by 14% and our task trigger p99 dropped by 18%. Aaaand in unrelated news… We're now the platinum sponsor for Zod! Zod is one of those bits that we use and love and rely on every day and that's why we wanted to support the work @colinhacks is doing. Full write-up here: tgr.dev/igN16BI
2
8
286
We (finally) upgraded to Zod 4.5 (from 3.x!) and our worker CPU demand plummeted, our batch throughput increased by 14% and our task trigger p99 dropped by 18%. Aaaand in unrelated news… We're now the platinum sponsor for Zod! Zod is one of those bits that we use and love and rely on every day and that's why we wanted to support the work @colinhacks is doing. Full write-up here: tgr.dev/igN16BI
7
57
6,418
Trigger.dev retweeted
Today is my first day at @triggerdotdev and I'm hoping it won't also be my last day after posting this pic
21
3
116
2,819
Come work with Jack: trigger.dev/careers
After a few months surfing in Sri Lanka, playing badminton in Malaysia and living on a farm in Cornwall.. I'm starting a new job tomorrow and it's the most excited I've been for a new job: - I was a customer of theirs and love the product - Have been friends with the team for years - The whole team is really talented and really nice - I'll be in-person in London - it's a devtool They're growing really fast already but my job is gonna be to help increase that slope pic related: I gatecrashed their offsite in Lisbon last week 😆
2
6
2,027
Trigger.dev retweeted
This was a fun one! excited to have the @triggerdotdev team here on @PlanetScale
This summer we upgraded our 56TB Postgres database with (almost) no downtime. And we moved all new runs to @planetscale Metal. This post covers everything we did and everything we learned along the way. tgr.dev/LuKQYce
2
1
17
1,726
Trigger.dev retweeted
pscale metal 🤝 fast growing agent infra Everyone I know who has tried trigger loves it, super happy that we get to play a small part of that.
This summer we upgraded our 56TB Postgres database with (almost) no downtime. And we moved all new runs to @planetscale Metal. This post covers everything we did and everything we learned along the way. tgr.dev/LuKQYce
1
23
1,723
Trigger.dev retweeted
i've just vibecoded Senja $29 automation in 1 hour 🤯 → nudges my customers after 14, 30 and 60 days → review form per product → fully customizable we're living in the future (built with @triggerdotdev)
1
2
9
824
New projects in @triggerdotdev now open with a "Copy AI agent prompt" button. Paste it into Claude Code or Cursor and your agent goes from an empty repo to a task that's registered and verified in the dashboard. How it works ↓
13
20
823
The MCP server is useful after setup too. Ask your agent to filter runs, explain a failure from its trace, deploy, or query runs and LLM usage with TRQL, all from your editor.
1
81
You can now show, hide, or reorder columns on the @triggerdotdev runs list. You can also add smart columns that pull a single value straight out of a run and display it for every row. ↓
13
18
1,023
Setup a Smart column to point at a run's payload, metadata, or output with a JSON path: $.𝚘𝚛𝚍𝚎𝚛.𝚝𝚘𝚝𝚊𝚕 as a number $.𝚌𝚞𝚜𝚝𝚘𝚖𝚎𝚛𝙸𝚍 as text $.𝚜𝚝𝚊𝚝𝚞𝚜 as a badge Give it a label and it fills in down the whole list.
3
6
265
Trigger.dev retweeted
Arena Conversations: @petergostev sat down with @mattaitken, founder and CEO of @triggerdotdev, to discuss building infrastructure for long-running agents, including retries, API reliability, and why customers are switching frontier models faster than ever. Watch the full episode at the link below.
6
6
47
16,635
Every environment in @triggerdotdev used to authenticate with a single secret key. Now each environment can hold as many keys as you want. Every service, CI job, and integration gets its own scoped credential. ↓
5
1
11
852
𝚝𝚛𝚒𝚐𝚐𝚎𝚛 𝚍𝚎𝚙𝚕𝚘𝚢 can authenticate with a Deploy-only key set as 𝚃𝚁𝙸𝙶𝙶𝙴𝚁_𝚂𝙴𝙲𝚁𝙴𝚃_𝙺𝙴𝚈. The full key value shows once at creation, then it's hashed at rest. The dashboard only ever displays an obfuscated suffix.
1
63