In case you missed it, here are some of the things we shipped in March: → Native @vercel integration → Query & Dashboards (ask in English, get SQL) → 5x throughput from a Bun rewrite → New MCP tools, TTL defaults, 𝚜𝚢𝚗𝚌𝚂𝚞𝚙𝚊𝚋𝚊𝚜𝚎𝙴𝚗𝚟𝚅𝚊𝚛𝚜 Full recap ↓

→ Our @vercel integration is live. Push code, tasks deploy automatically. Env vars sync both ways. Atomic deployments gate Vercel's promotion until your tasks are ready, so your app never goes live with a mismatched task version. No 𝚝𝚛𝚒𝚐𝚐𝚎𝚛.𝚍𝚎𝚟 𝚍𝚎𝚙𝚕𝚘𝚢, no CI/CD workflow.

→ Query. Ask "what are my p95 durations for the chat task?" and the AI writes the TRQL, runs it on ClickHouse, renders the chart. Or write the SQL yourself.

→ Dashboards Every project ships with a pre-built one: run volume, success rates, failures, costs, versions. Build custom ones on top with big numbers, charts, and tables. Filters apply across every widget at once.

→ v4.4.2 - v4.4.4: • batch trigger concurrency bumps. • 𝚜𝚢𝚗𝚌𝚂𝚞𝚙𝚊𝚋𝚊𝚜𝚎𝙴𝚗𝚟𝚅𝚊𝚛𝚜 pulls your Supabase connection strings in so you stop copy-pasting • Test page generates example payloads with AI (uses your 𝚜𝚌𝚑𝚎𝚖𝚊𝚃𝚊𝚜𝚔 schema if you have one, infers from past runs if you don't) • Dev CLI auto-cancels in-flight runs on exit • 11 new MCP tools including 𝚚𝚞𝚎𝚛𝚢, 𝚜𝚝𝚊𝚛𝚝_𝚍𝚎𝚟_𝚜𝚎𝚛𝚟𝚎𝚛, 𝚐𝚎𝚝_𝚜𝚙𝚊𝚗_𝚍𝚎𝚝𝚊𝚒𝚕𝚜. Your coding agent can now actually debug your runs. • Task-level and global TTL defaults • Multi-provider object storage for large run outputs

New on the blog: 1. We replaced Node.js with Bun in one of our most latency-sensitive services. 2,099 → 10,700 req/s. 5x throughput. Also found a Bun memory leak along the way (which was then swiftly patched by @jarredsumner at @bunjavascript). trigger.dev/blog/firebun

2. Deep dive on how TRQL works: the SQL-like language behind Query. Users write familiar SQL, but the ANTLR grammar physically can't express 𝙸𝙽𝚂𝙴𝚁𝚃 or 𝙳𝙴𝙻𝙴𝚃𝙴. Every query has its tenant filter injected at compile time. trigger.dev/blog/how-trql-…

3. Plus 10 Claude Code tips most people miss. --𝚏𝚘𝚛𝚔-𝚜𝚎𝚜𝚜𝚒𝚘𝚗 for context pre-warming. --𝚏𝚛𝚘𝚖-𝚙𝚛 to resume the agent that wrote your PR. ! for inline shell output. 𝙲𝚝𝚛𝚕+𝙶 to compose prompts in your editor. trigger.dev/blog/10-claude…