Trigger.dev
@triggerdotdev

Build and deploy fully‑managed AI agents and workflows. → trigger.dev → github.com/triggerdotdev → trigger.dev/discord

 Your codebase
trigger.dev
Joined November 2021
597 Photos and videos
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
718
more replies
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
80
Open a project's dev environment and hit "Copy AI agent prompt" to try it. Changelog here: trigger.dev/changelog/ai-age…

Set up Trigger.dev with your AI agent | Changelog

Copy a project-aware prompt that connects your coding agent to Trigger.dev's MCP server, with a CLI fallback and live setup progress.

trigger.dev
74
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. ↓
12
18
963
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
218
Your whole column layout lives in the URL, so you can favorite it to save it or share it with a team mate. Live now: trigger.dev/changelog/runs-c…

Customize the runs list with columns and smart columns | Changelog

Show, hide, and reorder the columns on the runs list, and add smart columns that pull a value out of a run's payload, metadata, or output by JSON path. Your layout lives in the URL, so a view is...

trigger.dev
1
2
130
Trigger.dev retweeted
Arena.ai
@arena
Sep 14
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
46
16,577
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
818
more replies
𝚝𝚛𝚒𝚐𝚐𝚎𝚛 𝚍𝚎𝚙𝚕𝚘𝚢 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
Open the API keys page in any project environment to create your first scoped key. Read the changelog: trigger.dev/changelog/multip…

Multiple API keys per environment | Changelog

Create as many keys as you need per environment, each with its own access scope, optional task restrictions, and an expiration date. Revoke any one instantly without rotating the rest.

trigger.dev
59
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. ↓
1
6
569
The filter is the same shape as 𝚛𝚞𝚗𝚜.𝚕𝚒𝚜𝚝(): status, task, tags, queue, version, region. So after you ship a fix, you replay exactly the runs that failed. No looping over run IDs by hand. Built into @triggerdotdev.
1
1
166
Kick it off, then 𝚛𝚞𝚗𝚜.𝚋𝚞𝚕𝚔.𝚙𝚘𝚕𝚕() waits for it to finish and returns live counts. 𝚛𝚞𝚗𝚜.𝚋𝚞𝚕𝚔.𝚊𝚋𝚘𝚛𝚝() stops one mid-flight. Changelog: trigger.dev/changelog/bulk-a…

Bulk actions from the SDK | Changelog

Cancel or replay runs matching a filter straight from your backend code with runs.bulk.replay() and runs.bulk.cancel(), then poll for progress.

trigger.dev
1
94
Trigger.dev retweeted
colinhacks
@colinhacks
Sep 9
Trigger (@triggerdotdev) is now a platinum sponsor of Zod — thanks @maverickdotdev and team! 🙏
2
55
3,354
Load more