inngest-cli

Configure and operate the Inngest CLI Dev Server for local durable workflow development.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/dhanushreddy291/durable-workflow-on-neon-functions --skill inngest-cli-dhanushreddy291
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inngest-cli
Source: https://github.com/dhanushreddy291/durable-workflow-on-neon-functions/tree/main/.agents/skills/inngest-cli
Command: npx skills add https://github.com/dhanushreddy291/durable-workflow-on-neon-functions --skill inngest-cli-dhanushreddy291

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up and debugging Inngest locally involves many moving parts: Dev Server flags, auto-discovery, environment variables, Docker networking, and platform-specific serve endpoint quirks. This Skill consolidates that operational knowledge so you can install, run, test, and self-host Inngest without hunting through documentation. ## Core Features & Use Cases - Dev Server Setup: Install and launch inngest dev with auto-discovery, custom ports, multiple app URLs, and config files (JSON/YAML/TOML). - Local Testing: Send events via SDK or curl, and unit test functions with @inngest/test including step mocking and event mocking. - Docker & Self-Hosting: Run the Dev Server in Docker Compose, or operate a production server with inngest start using Redis, PostgreSQL, and signing keys. - Use Case: Your Express app serves Inngest functions at /api/inngest but the Dev Server shows functionsFound: 0. Use this Skill to verify the serve endpoint with curl, fix the serve() configuration, and set INNGEST_DEV=1 so the SDK stops defaulting to Cloud mode. ## Quick Start Start the Inngest Dev Server with npx and point it at my app's serve endpoint, then help me send a test event to trigger my function.

Frequently Asked Questions about inngest-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start the Inngest Dev Server locally?▼

Run `npx inngest-cli@latest dev` to start the Dev Server with auto-discovery on port 8288. Use `-u http://localhost:3000/api/inngest` to point it at your app's serve endpoint explicitly, or `--no-discovery` to disable scanning.

How do I test Inngest functions locally without the Dev Server?▼

Use the `@inngest/test` package (requires inngest >= 4.0.0) with InngestTestEngine to execute full functions or individual steps. It supports mocking events, step responses, and pause-inducing steps like sleep or waitForEvent.

Why does the Inngest Dev Server show functionsFound: 0?▼

This means your functions are not passed to the `serve()` call or the app is not reachable. Verify the endpoint with `curl -s http://localhost:3000/api/inngest`, confirm all functions are in the serve array, and check the app is running on the correct port.

Does the Inngest CLI work with Docker Compose?▼

Yes, run the inngest/inngest image with `inngest dev -u http://app:3000/api/inngest` alongside your app service. You must set `INNGEST_DEV=1` and `INNGEST_BASE_URL=http://inngest:8288` on the app, since the SDK defaults to Cloud mode.

What is the difference between inngest dev and inngest start?▼

`inngest dev` runs an in-memory local Dev Server for development with no keys required. `inngest start` runs a self-hosted production server requiring `--event-key` and `--signing-key`, with external Redis and PostgreSQL recommended for persistence.

Why does my Inngest SDK connect to Cloud instead of the Dev Server?▼

The TypeScript SDK defaults to Cloud mode when `INNGEST_DEV` is unset. Set `INNGEST_DEV=1` in your environment to enable Dev Mode, which disables signature verification and targets the local Dev Server.