trigger.dev

Cloud platform for hosting code that runs on schedules, webhooks, and other event triggers. Used by Nate Herk as the trigger layer for claude-agent-sdk / Claude Code agents — the piece Anthropic’s Managed Agents conspicuously lacks. Open source with a hosted plan; cheaper than building agents inside Managed Agents for use cases that require a heartbeat.

Stub page — first appearance in the wiki via Nate Herk’s Managed Agents review. Will grow as more sources reference it.

Why it appears in the wiki

Nate Herk’s structural argument in the Managed Agents review: “I’d just rather use trigger.dev because it lets me host my code on the cloud, set up crons and things like that, and delegate to different scripts. It’s also a lot cheaper than Managed Agents.” The wiki tracks trigger.dev as the canonical external trigger primitive that closes the gap left by Managed Agents until/unless Anthropic ships a native cron.

Pattern

1. Build an agent locally with Claude Code using the Claude Agent SDK
2. Deploy the agent script to trigger.dev
3. Configure a trigger.dev schedule (cron, webhook, event) that invokes the script

This gives you Managed Agents-style “agent runs in the cloud” without paying $0.08/hr per session, and with native triggers.

See Also

• managed-agents — the Anthropic product that lacks the trigger primitive trigger.dev provides
• claude-code — the local build environment for the agents trigger.dev runs
• loop — Claude Code’s local-only equivalent (laptop-bound)
• Nate Herk — primary source
• Source: I Tested Claude’s New Managed Agents