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.