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

$ npx -y @mvanhorn/printing-press install trigger-dev

View on GitHub →Want a custom version?

What you unlock

A Go CLI for the Trigger.dev Management REST API — 48 endpoints across runs, queues, deployments, schedules, batches, waitpoints, and environment variables, plus TRQL queries and dashboards. Built for Claude Code agents that run background jobs for enrichment, sequencing, and signal monitoring. When a run stalls, list the failures, pull the trace, and replay it — without opening a browser. Agent mode emits clean JSON for piping straight into a pipeline.

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.

Surface every failed run in one query

$ trigger-dev-pp-cli runs list

--filter status=FAILED --json

--select id,task,status

✓ 2 failed runs → run_abc123 enrich-contacts FAILED → run_def456 send-batch FAILED

OutcomeEvery failure, surfaced in one query. No dashboard tab needed.

Trace a failed run to its root cause

$ trigger-dev-pp-cli runs retrieve-trace

--run-id run_abc123 --json

✓ Trace: 7 spans → Failed at step 3: enrich-contacts → Cause: Clay API 429 rate limit

OutcomeRoot cause in the span tree. 8 seconds, keyboard only.

What's included

Every capability, ready to script.

48 Management API endpoints across runs, queues, deployments, schedules, batches, and env vars

TRQL queries and dashboards via query execute for run-history analytics

Per-run trace and event retrieval — the exact failing step and upstream cause

Replay and cancel runs individually or filtered in bulk

Agent mode (--agent): JSON, compact, no prompts — built for Claude Code

The workflow

End to end. Zero manual steps.

Stop guessing why a job stalled. List → trace → replay traces any failure to its source and recovers it. 48 Management API endpoints, all scriptable.

01

Snapshot queue depth.

List every run queue with its concurrency limit and current depth. Spot a backing-up consumer before it delays a campaign send — no dashboard required.

$ trigger-dev-pp-cli queues list --json

--select name,concurrency,length

02

Find the failing runs.

Filter runs by status with pagination and field selection built in. Get exactly the runs you care about as clean JSON, ready to pipe downstream.

$ trigger-dev-pp-cli runs list

--filter status=FAILED --json

03

Trace the root cause.

Pull the full span tree and event log for any run. The exact failing step, the error, and the upstream cause — no dashboard archaeology.

$ trigger-dev-pp-cli runs retrieve-trace

--run-id run_abc123 --json

04

Replay once it's fixed.

Push the corrected run back through. Replay a single failure or filter and batch them. The pipeline recovers without a redeploy.

$ trigger-dev-pp-cli runs replay --run-id run_abc123

Real scenarios

What teams actually use it for.

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

01Tracing why an enrichment run failed without opening the Trigger.dev dashboard

02Auditing env vars across environments before deploying a pipeline

03Querying run history with TRQL to report job pass rates and throughput

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

Lists failed runs, then pulls the trace and events for each. Surfaces the exact step, error, and upstream cause as a structured report. Built on runs list + runs retrieve-trace.

Triggers: "why did run [id] fail"

queue-health

Queue Health Monitor

Lists every run queue with depth and concurrency limit. Flags queues above a configurable stall threshold. Built on queues list — designed to run before campaign sends.

Triggers: "check queue health before we launch"

batch-status

Batch Status Scanner

Pulls results for active batches: completed, pending, and errored items. Built on batches retrieve-results. Surfaces batches that need intervention without dashboard access.

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

env-audit

Env Audit

Lists environment variables across environments and diffs them. Catches missing keys and stale values before they silently break a pipeline. Built on envvars list.

Triggers: "audit the prod env before we deploy"

schedule-overview

Schedule Overview

Lists every cron schedule with its state, next fire time, and timezone. Surfaces deactivated jobs, gaps, and conflicts across your Trigger.dev environment. Built on schedules list.

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 →