[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-3876":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":39,"readmeContent":40,"aiSummary":41,"trendingCount":16,"starSnapshotCount":16,"syncStatus":42,"lastSyncTime":43,"discoverSource":44},3876,"trigger.dev","triggerdotdev\u002Ftrigger.dev","triggerdotdev","Trigger.dev – build and deploy fully‑managed AI agents and workflows","https:\u002F\u002Ftrigger.dev\u002Fchangelog",null,"TypeScript",15304,1301,49,290,0,19,89,422,93,44.34,"Apache License 2.0",false,"main",[26,27,28,29,30,31,32,33,34,35,36,37,38],"ai","ai-agent-framework","ai-agents","automation","background-jobs","mcp","mcp-server","nextjs","orchestration","scheduler","serverless","workflow-automation","workflows","2026-06-12 02:00:55","\u003Cdiv align=\"center\">\n\n![Trigger.dev logo](https:\u002F\u002Fcontent.trigger.dev\u002Fgithub-header-banner.jpg)\n\n### Build and deploy fully‑managed AI agents and workflows\n\n[Website](https:\u002F\u002Ftrigger.dev) | [Docs](https:\u002F\u002Ftrigger.dev\u002Fdocs) | [Issues](https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Ftrigger.dev\u002Fissues) | [Example projects](https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Fexamples) | [Feature requests](https:\u002F\u002Ftriggerdev.featurebase.app\u002F) | [Public roadmap](https:\u002F\u002Ftriggerdev.featurebase.app\u002Froadmap) | [Self-hosting](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fself-hosting\u002Foverview) \n\n[![Open Source](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FOpen%20Source-%E2%9D%A4-red.svg)](https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Ftrigger.dev)\n[![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-Apache%202.0-blue.svg)](https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Ftrigger.dev\u002Fblob\u002Fmain\u002FLICENSE)\n[![npm](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002F@trigger.dev\u002Fsdk.svg?label=npm)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@trigger.dev\u002Fsdk)\n[![SDK downloads](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fdm\u002F@trigger.dev\u002Fsdk.svg?label=SDK%20downloads)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@trigger.dev\u002Fsdk)\n\n[![Twitter Follow](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002Ftriggerdotdev?style=social)](https:\u002F\u002Ftwitter.com\u002Ftriggerdotdev)\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F1066956501299777596?logo=discord&logoColor=white&color=7289da)](https:\u002F\u002Fdiscord.gg\u002FnkqV9xBYWy)\n[![Ask DeepWiki](https:\u002F\u002Fdeepwiki.com\u002Fbadge.svg)](https:\u002F\u002Fdeepwiki.com\u002Ftriggerdotdev\u002Ftrigger.dev)\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002Ftriggerdotdev\u002Ftrigger.dev?style=social)](https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Ftrigger.dev)\n\n\u003C\u002Fdiv>\n\n## About Trigger.dev\n\nTrigger.dev is the open-source platform for building AI workflows in TypeScript. Long-running tasks with retries, queues, observability, and elastic scaling.\n\n## The platform designed for building AI agents\n\nBuild [AI agents](https:\u002F\u002Ftrigger.dev\u002Fproduct\u002Fai-agents) using all the frameworks, services and LLMs you're used to, deploy them to Trigger.dev and get durable, long-running tasks with retries, queues, observability, and elastic scaling out of the box.\n\n- **Long-running without timeouts**: Execute your tasks with absolutely no timeouts, unlike AWS Lambda, Vercel, and other serverless platforms.\n\n- **Durability, retries & queues**: Build rock solid agents and AI applications using our durable tasks, retries, queues and idempotency.\n\n- **True runtime freedom**: Customize your deployed tasks with system packages – run browsers, Python scripts, FFmpeg and more.\n\n- **Human-in-the-loop**: Programmatically pause your tasks until a human can approve, reject or give feedback.\n\n- **Realtime apps & streaming**: Move your background jobs to the foreground by subscribing to runs or streaming AI responses to your app.\n\n- **Observability & monitoring**: Each run has full tracing and logs. Configure error alerts to catch bugs fast.\n\n## Key features:\n\n- **[JavaScript and TypeScript SDK](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftasks\u002Foverview)** - Build background tasks using familiar programming models\n- **[Long-running tasks](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fruns\u002Fmax-duration)** - Handle resource-heavy tasks without timeouts\n- **[Durable cron schedules](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftasks\u002Fscheduled#scheduled-tasks-cron)** - Create and attach recurring schedules of up to a year\n- **[Trigger.dev Realtime](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Frealtime\u002Foverview)** - Trigger, subscribe to, and get real-time updates for runs, with LLM streaming support\n- **[Build extensions](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fconfig\u002Fextensions\u002Foverview#build-extensions)** - Hook directly into the build system and customize the build process. Run Python scripts, FFmpeg, browsers, and more.\n- **[React hooks](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ffrontend\u002Freact-hooks#react-hooks)** - Interact with the Trigger.dev API on your frontend using our React hooks package\n- **[Batch triggering](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftriggering#tasks-batchtrigger)** - Use batchTrigger() to initiate multiple runs of a task with custom payloads and options\n- **[Structured inputs \u002F outputs](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftasks\u002FschemaTask#schematask)** - Define precise data schemas for your tasks with runtime payload validation\n- **[Waits](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fwait)** - Add waits to your tasks to pause execution for a specified duration\n- **[Preview branches](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fdeployment\u002Fpreview-branches)** - Create isolated environments for testing and development. Integrates with Vercel and git workflows\n- **[Waitpoints](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fwait-for-token#wait-for-token)** - Add human-in-the-loop judgment at critical decision points without disrupting workflow\n- **[Concurrency & queues](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fqueue-concurrency#concurrency-and-queues)** - Set concurrency rules to manage how multiple tasks execute\n- **[Multiple environments](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fhow-it-works#dev-mode)** - Support for DEV, PREVIEW, STAGING, and PROD environments\n- **[No infrastructure to manage](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fhow-it-works#trigger-dev-architecture)** - Auto-scaling infrastructure that eliminates timeouts and server management\n- **[Automatic retries](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ferrors-retrying)** - If your task encounters an uncaught error, we automatically attempt to run it again\n- **[Checkpointing](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fhow-it-works#the-checkpoint-resume-system)** - Tasks are inherently durable, thanks to our checkpointing feature\n- **[Versioning](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fversioning)** - Atomic versioning allows you to deploy new versions without affecting running tasks\n- **[Machines](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fmachines)** - Configure the number of vCPUs and GBs of RAM you want the task to use\n- **[Observability & monitoring](https:\u002F\u002Ftrigger.dev\u002Fproduct\u002Fobservability-and-monitoring)** - Monitor every aspect of your tasks' performance with comprehensive logging and visualization tools\n- **[Logging & tracing](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Flogging)** - Comprehensive logging and tracing for all your tasks\n- **[Tags](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftags#tags)** - Attach up to ten tags to each run, allowing you to filter via the dashboard, realtime, and the SDK\n- **[Run metadata](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fruns\u002Fmetadata#run-metadata)** - Attach metadata to runs which updates as the run progresses and is available to use in your frontend for live updates\n- **[Bulk actions](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fbulk-actions)** - Perform actions on multiple runs simultaneously, including replaying and cancelling\n- **[Real-time alerts](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Ftroubleshooting-alerts#alerts)** - Choose your preferred notification method for run failures and deployments\n\n## Write tasks in your codebase\n\nCreate tasks where they belong: in your codebase. Version control, localhost, test and review like you're already used to.\n\n```ts\nimport { task } from \"@trigger.dev\u002Fsdk\";\n\n\u002F\u002F1. You need to export each task\nexport const helloWorld = task({\n  \u002F\u002F2. Use a unique id for each task\n  id: \"hello-world\",\n  \u002F\u002F3. The run function is the main function of the task\n  run: async (payload: { message: string }) => {\n    \u002F\u002F4. You can write code that runs for a long time here, there are no timeouts\n    console.log(payload.message);\n  },\n});\n```\n\n## Deployment\n\nUse our SDK to write tasks in your codebase. There's no infrastructure to manage, your tasks automatically scale and connect to our cloud. Or you can always self-host.\n\n## Environments\n\nWe support `Development`, `Staging`, `Preview`, and `Production` environments, allowing you to test your tasks before deploying them to production.\n\n## Full visibility of every job run\n\nView every task in every run so you can tell exactly what happened. We provide a full trace view of every task run so you can see what happened at every step.\n\n![Trace view image](https:\u002F\u002Fcontent.trigger.dev\u002Ftrace-view.png)\n\n# Getting started\n\nThe quickest way to get started is to create an account and project in our [web app](https:\u002F\u002Fcloud.trigger.dev), and follow the instructions in the onboarding. Build and deploy your first task in minutes.\n\n### Useful links:\n\n- [Quick start](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fquick-start) - get up and running in minutes\n- [How it works](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fhow-it-works) - understand how Trigger.dev works under the hood\n- [Guides and examples](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fguides\u002Fintroduction) - walk-through guides and code examples for popular frameworks and use cases\n\n## Self-hosting\n\nIf you prefer to self-host Trigger.dev, you can follow our [self-hosting guides](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fself-hosting\u002Foverview):\n\n- [Docker self-hosting guide](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fself-hosting\u002Fdocker) - use Docker Compose to spin up a Trigger.dev instance\n- [Kubernetes self-hosting guide](https:\u002F\u002Ftrigger.dev\u002Fdocs\u002Fself-hosting\u002Fkubernetes) - use our official Helm chart to deploy Trigger.dev to your Kubernetes cluster\n\n## Support and community\n\nWe have a large active community in our official [Discord server](https:\u002F\u002Ftrigger.dev\u002Fdiscord) for support, including a dedicated channel for self-hosting.\n\n## Development\n\nTo setup and develop locally or contribute to the open source project, follow our [development guide](.\u002FCONTRIBUTING.md).\n\n## Meet the Amazing People Behind This Project:\n\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftriggerdotdev\u002Ftrigger.dev\u002Fgraphs\u002Fcontributors\">\n  \u003Cimg src=\"https:\u002F\u002Fcontrib.rocks\u002Fimage?repo=triggerdotdev\u002Ftrigger.dev\" \u002F>\n\u003C\u002Fa>\n","Trigger.dev 是一个用于构建和部署全托管AI代理和工作流的开源平台。它支持使用TypeScript编写长时间运行的任务，具有自动重试、队列管理、可观测性和弹性伸缩等核心功能。该平台允许开发者利用熟悉的框架和服务创建AI代理，并提供无超时限制的执行环境，确保任务的稳定性和可靠性。此外，Trigger.dev 还支持自定义系统包，实现浏览器操作、Python脚本执行等功能，并且能够将后台任务与前端应用实时连接起来，便于进行人工干预或监控。适用于需要构建复杂AI驱动的工作流以及希望提高自动化流程可靠性的场景。",2,"2026-06-11 02:56:51","top_language"]