Check out our open source tools to give Claude Code GTM superpowers→

Trigger.dev CLI

Inspect, debug, and manage Trigger.dev background jobs from the terminal.

Open source · MIT · Production-tested inside LeadGrow's live pipeline

Quick install

$ npm install -g @leadgrow/trigger-dev-cli

View on GitHub →Want a custom version?

What you unlock

A CLI that gives Claude Code agents direct visibility into your Trigger.dev job infrastructure. Check queue health, pull batch status, snapshot environment configs, and review scheduled job timelines — all without opening a browser. Built for outbound automation pipelines where background jobs run enrichment, sequencing, and signal monitoring. When a job silently stalls, this is how you find it in under 30 seconds.

OutcomeBuilt at LeadGrow, used in live pipelines, shipped open source so you don't have to build it yourself.

How it works

See it in action

2 things you can do right now.

No UI. No clicking. Just commands that execute.

Run forensics on a failed job

$ trigger-dev run_forensics

--run-id run_abc123 --depth full

✓ Run run_abc123 traced → Failed at: enrich-contacts (step 3) → Cause: API rate limit — Clay 429 → Last success: 2026-05-13 06:14 UTC

OutcomeRoot cause in 8 seconds. No dashboard tab needed.

Check queue health across all pipelines

$ trigger-dev queue_health --env production

✓ Queues healthy: 4/5 ⚠ enrichment-queue — depth 847, oldest 14 min → Flag: possible consumer stall

OutcomeOne queue flagged before it affects campaign send times.

What's included

Every capability, ready to script.

Queue health snapshot — see depth, age, and stall indicators in one command

Batch status overview across all active job runs

Environment variable snapshot for rapid config audits

Schedule overview — see every cron and one-off job at a glance

Forensics mode — trace a failed run back to the originating event

The workflow

End to end. Zero manual steps.

Stop guessing why a job stalled. Forensics mode traces any failure back to its source in under 30 seconds.

01

Snapshot queue health.

Run a health check across all queues in your production environment. Depth and age tell you whether jobs are processing normally or backing up silently.

$ trigger-dev queue_health --env production

02

Pull batch status for active runs.

See every active batch — how many tasks completed, how many are pending, and which are erroring. No need to click through individual runs in the dashboard.

$ trigger-dev batch_status --limit 20

03

Snapshot environment config.

Before deploying changes, audit the environment. Catch missing keys or stale values before they break a production job mid-run.

$ trigger-dev env_snapshot --env production --diff staging

04

Review the full job schedule.

See every cron and one-off job across your pipeline. Catch schedule conflicts, gaps in coverage, and jobs that should have fired but didn't.

$ trigger-dev schedule_overview --env production

Real scenarios

What teams actually use it for.

Not theoretical. These are the pipelines running at LeadGrow and client stacks today.

01Diagnosing why an enrichment batch stalled without opening the Trigger.dev dashboard

02Auditing environment configs before deploying a new outbound pipeline

03Reviewing the full schedule of automation jobs to find overlap or gaps

Included skills

Pre-built automations. Ready to run.

These aren't demos. They're the Claude Code skills we run inside LeadGrow, shipped open source so you don't have to build them yourself.

run-forensics

Run Forensics

Traces a failed Trigger.dev run back to the originating event. Surfaces the exact step, error, and upstream cause. Outputs a structured failure report for fast debugging.

Triggers: "why did run [id] fail"

queue-health

Queue Health Monitor

Checks depth and age across all queues in a target environment. Flags queues above a configurable stall threshold. Designed to run before campaign sends.

Triggers: "check queue health before we launch"

batch-status

Batch Status Scanner

Pulls status for all active batches: completed, pending, and erroring task counts. Surfaces batches that need intervention without requiring dashboard access.

Triggers: "what's the status of the enrichment batch"

env-snapshot

Environment Snapshot

Audits environment variables across environments. Diffs staging vs production. Catches missing keys and stale values before they silently break a pipeline.

Triggers: "snapshot the prod env before we deploy"

schedule-overview

Schedule Overview

Pulls the full job schedule across your Trigger.dev environment — every cron and one-off job, last fire time, next fire time, and enabled status. Surfaces gaps, conflicts, and jobs that should have fired but didn't.

Triggers: "show me the full job schedule"

More in this category

Bison CLI

Full-featured CLI for EmailBison — workspace, leads, campaigns, sequences, variables.

DiscoLike CLI

ICP list building and lookalike discovery from the terminal.

AI Ark CLI

Orchestrate AI Ark workflows from Claude Code.

Custom build

Want us to build yours?

Custom CLIs, MCP servers, and Claude Code skills wired to your exact GTM stack.

We build these for clients. Then we ship them open.

Book a Strategy Call →