Eric Allam

we're opening up more roles, hiring remote or in person in London 🇬🇧, building some very cool open source stuff and working on hard/medium/easy problems (we have them all). DM me and please share 🙏

Switching from Node to @bunjavascript gave us a 5x speed boost (28x better max latency) but there was a gotcha… Pending response promises don't resolve on client disconnect. @nodejs handles this automatically. Fix: resolve disconnects with 499. trigger.dev/blog/firebun

@NathanFlurry @triggerdotdev Ah man someone beat us to it! We need to publish a demo

Another cool use case we didn't consider: company started using Secure Exec with @triggerdotdev 👀

🤘 Rivet Secure Exec (V8 isolates): Securely execute Node.js anywhere (Railway, Vercel, Hetzner, Kubernetes) vs 🔥 Firecracker (microVMs): Full Linux operating system, but requires specialized infrastructure

@bmcnew_ @triggerdotdev How about us?

Ran an agent audit on @triggerdotdev

Just launched: our Vercel integration for Trigger. Push code. @vercel deploys your app. @triggerdotdev deploys your tasks. Env vars sync both ways. Your app never goes live with mismatched task versions. ↓

@nicoalbanese10 Have something for this coming soon 👀

Building durable agents with resumable streams, aborting, and persistence is hard

Do you think Claude gives us ratings on how well we are doing this session?

SF is for coding agents, London is for enterprise agents

@wishee0 @boristane he would but unfortunately he's going to use vue

@boristane you better have one heck of a good ui at nominal!!

I need this damn

@loujaybee @claudeai @cursor_ai @DevinAI @ona_hq @modal @Cloudflare @triggerdotdev

Adding a tooling landscape to background-agents.com Ofc @claudeai, @cursor_ai, @DevinAI, @ona_hq, @modal, @Cloudflare - who else?

Query and Dashboards are now live. You have full SQL-powered observability over your Trigger data. You can ask: "Why did failures spike after my last deploy?" "What's the p95 duration for my chat task?" "What are my most expensive runs?" ↓

@InboxZero @triggerdotdev @trigger Ah yea you do need it in the config file, although I usually stick it in .env and use process.env.TRIGGER_PROJECT_REF in the config file. Its only needed there because the CLI uses PATs which is just associated to your user, not a particular project

i did the setup to run Tasks and ended up creating a trigger.config.ts file with this info import { defineConfig } from "@trigger.dev/sdk/v3"; export default defineConfig({ project: "proj_p and maxDuration: 259200, // 3 days (in seconds) btw i'm loving everything! big fan already.

@triggerdotdev why do i need to pass my project id, isn't my Project API Key enough information??? seems kinda silly.

@goldmanem @sequinstream @NotionHQ Congrats guys!

Thrilled to share that @sequinstream has been acquired by @NotionHQ! We completed the deal in August. Since then, we've been weaving our flavor of primitives into Notion's developer tools. More details soon, but I couldn't be more bullish on where this is headed and what it unlocks for builders. Creating Sequin with @accomazzo has been a dream. Stoked we still get to ship together every day. Thank you to our customers, investors, and families 🤙 To get the backstory, read Notion's announcement: notion.com/blog/welcome-s…

@lydiahallie This looks great! Seems to run into permissions issues though, the team agents kept failing because it didn't have permissions, and the leader agent never asked me for permission approval (running 2.1.32 on Opus 4.6)

Docs: code.claude.com/docs/en/agent-…

Claude Code now supports agent teams (in research preview) Instead of a single agent working through a task sequentially, a lead agent can delegate to multiple teammates that work in parallel to research, debug, and build while coordinating with each other. Try it out today by enabling agent teams in your settings.json!

I built a @techmeme killer on crack, with ai / @firecrawl / @iframely / @vercel / @supabase / @triggerdotdev. It's wild, messy, and fun. I'm not going to launch it, but if you want to see it and understanding my building process, check it out here: youtube.com/watch?v=QPAy9R…

Spent the last 48 hours tracking down a massive memory leak in one of our production services. Node.js processes using up to 12-14GB within 5 hours. Went down 6 or 7 rabbit holes trying to recreate the leak locally, disabling various instrumentation, metrics, logging, prepared the service to be safely heapsnapshotted. Of course we created a script to slowly recycle the service every 4 hours before they would crash to buy us some time. Finally decided to look again at our logs and thats when I spotted the dreaded "Failed to convert rust `String` into napi `string`" error coming from a Prisma query. It turned out to be a two stuck processes polling the service every 5 seconds, performing a query that returned too much data to be serialized between the rust and the js layer in Prisma, starting about 2 weeks ago. The first arrow below is when we killed the stuck processes, as you can see memory flatlining. Then a few hours later we re-deployed the service with new tasks and now they are flat and using about 1GB of memory each at max. Few things in life come close to the satisfaction of finally finding and fixing this stupid memory leak

We've just shipped 5 Trigger Skills. Install them and your AI coding assistant will automatically gain in-depth @triggerdotdev knowledge. ✦ 𝚝𝚛𝚒𝚐𝚐𝚎𝚛-𝚜𝚎𝚝𝚞𝚙 ✦ 𝚝𝚛𝚒𝚐𝚐𝚎𝚛-𝚊𝚐𝚎𝚗𝚝𝚜 ✦ 𝚝𝚛𝚒𝚐𝚐𝚎𝚛-𝚝𝚊𝚜𝚔𝚜 ✦ 𝚝𝚛𝚒𝚐𝚐𝚎𝚛-𝚛𝚎𝚊𝚕𝚝𝚒𝚖𝚎 ✦ 𝚝𝚛𝚒𝚐𝚐𝚎𝚛-𝚌𝚘𝚗𝚏𝚒𝚐 🧵 But what are skills?

100% vibe coded a speed reading app yesterday evening. Can finally get round to reading all those articles on my reading list i was probably never gonna read ↓