An eve workflow tool that waits for a search result

An eve workflow tool that asks for approval, orders a synthetic local search in one "use step" function, parks on a createWebhook URL holding no compute, and survives a kill -9 of eve dev followed by eve dev --resume. One order, one callback, and the step's recorded result is replayed rather than re-run.

Back to the exercise

Before you start

Before you start:Node.js, pnpm and TypeScript Durable agents with eve Get an OpenRouter key Local models with Ollama

This exercise calls a model. Run it either way

Any model through OpenRouterOne key for Claude, GPT, Gemini, Llama and more. Pay per token, with a credit limit.A local open-source modelFree and private with Ollama. Weaker on hard tasks.

Which should I pick? →

order_local_search is a defineWorkflowTool whose body does three things: mint a webhook, order the search through a step, and await the webhook. Everything that touches the outside world or reads a clock is a "use step" function, so when the run replays after a wait or a crash, eve hands back the recorded results instead of running them again. The decision that matters most is that the order step is idempotent twice over: eve records its result, and the step sends a stable Idempotency-Key derived from the matter and title, so even a step that is retried after a crash can't order a second search.

Answers Lesson 2: Durable, long-running agents

Step-by-step answer

Stretch 90 min7 steps