inngest-cli

Configure and operate the Inngest CLI Dev Server for local development, testing, and self-hosted deployment.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/firstaxel/neon --skill inngest-cli-firstaxel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inngest-cli
Source: https://github.com/firstaxel/neon/tree/main/.agents/skills/inngest-cli
Command: npx skills add https://github.com/firstaxel/neon --skill inngest-cli-firstaxel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires inngest-cli, @inngest/test.

What problem does it solve? Setting up and debugging the Inngest CLI and Dev Server involves many flags, environment variables, and platform-specific gotchas that are easy to misconfigure, causing functions to go undiscovered or sync to the wrong environment. ## Core Features & Use Cases - Local Dev Server Setup: Start inngest dev with auto-discovery, custom ports, multiple app URLs, and configuration files for local development. - Testing & Debugging: Send test events via SDK or curl, verify serve endpoints, and unit test functions with @inngest/test including step mocking. - Docker & Self-Hosting: Run the Dev Server in Docker Compose or operate inngest start as a self-hosted production server with Redis, PostgreSQL, or SQLite persistence. - Use Case: You are building a TypeScript app with Inngest functions and need to trigger them locally, debug why functionsFound is 0, and later deploy with the correct signing keys and sync workflow. ## Quick Start Ask the assistant to start the Inngest Dev Server pointed at your app's serve endpoint and verify that your functions are discovered correctly.

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 a specific app serve endpoint, or `-p` to change the port.

How do I test Inngest functions locally without the cloud?▼

Use the Dev Server to send events via the SDK or curl to `http://localhost:8288/e/test`. For unit tests, install `@inngest/test` and use InngestTestEngine to execute functions, test individual steps, and mock step responses.

Why does the Inngest Dev Server not find my functions?▼

The app is usually not running or the Dev Server points at the wrong URL. Start your app first, pass the correct URL with `-u`, and verify with `curl -s http://localhost:3000/api/inngest` that `functionsFound` is greater than zero.

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. 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 optional external Redis and PostgreSQL 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, or set it to the Dev Server URL such as `http://localhost:8288`, to force Dev Mode.