Trigger.dev (@triggerdotdev) header
Trigger.dev (@triggerdotdev) profile picture

Trigger.dev

@triggerdotdev

Build and deploy durable AI agents and workflows. → https://xitter.twitterapi.xyz/t.co/glJGy69WV0 → https://xitter.twitterapi.xyz/t.co/TJuSGuixlj → https://xitter.twitterapi.xyz/t.co/v5HnGSxBNb

 Your codebase
trigger.dev
Joined November 2021
  • Tweets1.6K
  • Following106
  • Followers9.2K
We now have support for OIDC workload identity. Here's what it is and the benefits of it. tgr.dev/SVBoaqY
Passport-stamp style cover for How OIDC workload identity works

ALT Passport-stamp style cover for How OIDC workload identity works

1
5
570
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.

ALT 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.

1
8
1,214
Replying to @_nibsy
@_nibsy
1
110
We're live on Product Hunt: Webhooks for your AI agents
12
4
1
30
2,559
Happy Friday
1
2
2
18
1,221
Next week we're launching our all time most requested feature 👀
A dark card titled Feature requests showing the number one entry with its title blurred out and 199 upvotes, on a purple gradient background.

ALT A dark card titled Feature requests showing the number one entry with its title blurred out and 199 upvotes, on a purple gradient background.

1
1
1
15
1,344
Replying to @_nibsy
@_nibsy
1
98
Replying to @jacksbridger
@jacksbridger
4
114
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 ↓
Image from Trigger.dev (@triggerdotdev)
13
21
925
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.
Image from Trigger.dev (@triggerdotdev)
3
7
325
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
19
1,097
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. ↓
Image from Trigger.dev (@triggerdotdev)
5
1
11
902
You can run bulk cancel and replay straight from the SDK. Point 𝚛𝚞𝚗𝚜.𝚋𝚞𝚕𝚔.𝚛𝚎𝚙𝚕𝚊𝚢() or 𝚛𝚞𝚗𝚜.𝚋𝚞𝚕𝚔.𝚌𝚊𝚗𝚌𝚎𝚕() at a filter and it hits every matching run, from a handful to millions. ↓
Image from Trigger.dev (@triggerdotdev)
1
6
637
New in @triggerdotdev: the health report. One command tells you if your project is actually healthy: – is work starting? – are runs succeeding? – is your telemetry fresh? 𝚝𝚛𝚒𝚐𝚐𝚎𝚛 𝚛𝚎𝚙𝚘𝚛𝚝 𝚑𝚎𝚊𝚕𝚝𝚑 ↓
Image from Trigger.dev (@triggerdotdev)
3
3
10
1,190
Define your prompts in code. Override them live when you need to. On @triggerdotdev a prompt is an id, a model, typed variables, and a template, and every deploy creates a new version. Override the text or model from the dashboard, no redeploy ↓
Image from Trigger.dev (@triggerdotdev)
3
9
1,163
The MCP server for @triggerdotdev does a lot more than deploy and trigger tasks now. Your coding assistant can chat with your deployed agents, manage prompt versions, and pull a health report. All from Claude Code or Cursor. ↓
Image from Trigger.dev (@triggerdotdev)
4
1
1
17
1,979
You could always see what a task did. Now you can see what it spent. Every LLM call your @triggerdotdev tasks make becomes a span in the trace. One flag, 𝚎𝚡𝚙𝚎𝚛𝚒𝚖𝚎𝚗𝚝𝚊𝚕_𝚝𝚎𝚕𝚎𝚖𝚎𝚝𝚛𝚢, on any Vercel AI SDK call. Nothing to install. Whole AI bill, or any single call, in the trace ↓
4
1
10
1,414
Every turn is a span in the dashboard: the prompts, the responses, the tool calls, how long each took. An AI metrics dashboard ships with every project too: spend, tokens, latency percentiles, cost by model. No instrumentation to write.
1
3
120
𝚌𝚑𝚊𝚝.𝚊𝚐𝚎𝚗𝚝 is a chat backend where every conversation runs on its own real machine. It boots on the first message, runs as long as the work takes, and keeps its memory between turns. Here's how one is put together, with @triggerdotdev ↓
Image from Trigger.dev (@triggerdotdev)
1
5
9
1,073
Load more