Trigger.dev

@triggerdotdev

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

Your codebase

trigger.dev

Replies Reposts Media

Trigger.dev
@triggerdotdev
Sep 3
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 ↓
2
Trigger.dev
@triggerdotdev
Aug 20
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. ↓
4
Trigger.dev
@triggerdotdev
Aug 18
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
00:00
3
Trigger.dev
@triggerdotdev
Aug 13
𝚌𝚑𝚊𝚝.𝚊𝚐𝚎𝚗𝚝 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 ↓
1
Trigger.dev
@triggerdotdev
Aug 12
SCIM directory sync is live for orgs on SSO. Assign someone to @triggerdotdev in your IdP and they land in your org. Unassign them and their access is gone. Okta, Microsoft Entra, Google Workspace, JumpCloud, OneLogin, and more.
SCIM directory sync for SSO | Changelog
From trigger.dev