Inngest Agent Example — Utah

Universally Triggered Agent Harness

A durable AI agent built with Inngest and pi-ai. No framework. Just a think/act/observe loop — Inngest provides durability, retries, and observability, while pi-ai provides a unified LLM interface across providers.

Simple TypeScript that gives you:

• 🔄 Durable agent loop — every LLM call and tool execution is an Inngest step
• 🔁 Automatic retries — LLM API timeouts are handled by Inngest, not your code
• 🔒 Singleton concurrency — one conversation at a time per chat, no race conditions
• ⚡ Cancel on new message — user sends again? Current run cancels, new one starts
• 📡 Multi-channel — Slack, Telegram, and more via a simple channel interface
• 🏠 Local development — runs on your machine via connect(), no server needed

Architecture

Channel (e.g. Telegram) → Inngest Cloud (webhook + transform) → WebSocket → Local Worker → LLM (Anthropic/OpenAI/Google) → Reply Event → Channel API

The worker connects to Inngest Cloud via WebSocket. No public endpoint. No ngrok. No VPS. Messages flow through Inngest as events, and the agent processes them locally with full filesystem access.

Prerequisites

• Node.js 23+ (uses native TypeScript strip-types)
• LLM API key (e.g. Anthropic API key (console.anthropic.com))