Inngest Changelog

We've improved Insights and added new datasources, functionality and syntax support.

New datasources include:

• Runs — Query your function runs and their associated data, such as input, output, and execution time.
• Steps/StepAttempts — Query the individual steps within your function runs, including their status, output, and execution time.
• Extended Trace Spans — Query the spans associated with your function runs, providing more information about the execution of your functions.

New features added:

• Insights AI — An assistant to help write your queries from plain English descriptions.
• Schema Explorer — A sidebar utility that shows available tables and event schemas.

Also added support for new functions and improved syntax support to make it easier to query your data.

Realtime is now a first-class part of the TypeScript SDK. Channels, topics, publishing, and subscribing all have an improved DX, along with an updated useRealtime React hook. The legacy @inngest/realtime package is deprecated in favor of the built-in realtime APIs in inngest, inngest/realtime, and inngest/react.

The TypeScript SDK v4 is now generally available!

This is a major version with breaking changes, but for most apps the migration is trivial.

Install with npm install inngest@latest.

For full details on changes and how to migrate from v3:

• Announcement blog post
• Migration guide

Added timeline header with time brush for zooming into specific time ranges in traces for long-running functions. Improved step details panel with timing info, step-specific fields, and a new Headers tab showing response headers returned by SDK endpoints.

The TypeScript SDK v4 is now available in beta! Major improvements include:

• Rewritten middleware — Hooks are more intuitive, less overloaded, and enable new use cases.
• Better schemas — Runtime event data validation with Standard Schema support (not just Zod!).
• Faster by default — Parallel step optimization and checkpointing are both enabled by default, leading to fewer requests and lower latency.
• Improved logging — Structured logging (Pino-style) and cleaner separation of internal vs. app logs.
• Cleaner API — Triggers in the options object, lazy init for edge runtimes, and more compile-time safety

This is a major version with breaking changes, but for most apps the migration is trivial.

Install the beta with npm install inngest@beta.

More info:

• Announcement blog post
• Migration guide

Official Helm chart now published as OCI artifact for easy installation and upgrades for self-hosting Inngest. Includes improved labels support with Kubernetes best practices and improved probes.

Released Inngest Agent Skills — pre-built skills for AI coding agents (Claude Code, Cursor, Windsurf) covering project configuration, event design, durable functions, workflow composition, flow control, and middleware. Six skills available with full Inngest development workflow coverage.

Durable Endpoints bring Inngest's durability into API handlers. Wrap endpoint code with inngest.endpoint() and use step.run() for automatic retries, recovery, and observability. Features zero configuration, automatic recovery from last successful step, built-in observability, and low latency powered by Checkpointing. Available in public beta for Next.js and Bun.

Docs now have quick actions to copy or open pages in Markdown format and open conversations with markdown URLs in Claude, ChatGPT, or other LLM providers. The llms.txt file includes markdown URLs for each page to reduce required context.

Released developer preview of Checkpointing, enabling near-zero inter-step latency in durable workflows. Dogfooding results show 50% reduction in workflow duration and near-zero inter-step latency. Available as opt-in configuration at client or function level.

Released MCP Integration for the Inngest dev server, enabling AI-assisted development workflows. Connect Claude Code, Cursor, and other AI assistants directly to local Inngest functions. Provides 8 tools: event management, real-time monitoring, direct function invocation, documentation access, and integration testing.

Webhooks are now more flexible with the addition of x-www-form-urlencoded and multipart/form-data content types. When sending a request with either of these content types, your webhook transform will have access to both a JSON object representation of the body and the raw body as a string.

Example: When sending form-encoded data like name=Alice&messages=hello&messages=world, the webhook transform receives both the parsed JSON object and the raw body string.