Start with the SDK, deploy a durable worker, and learn how to recover tool calls while accounting for duplicate side effects.
No. Your application runs the agent. GetRatchet records and manages tool calls, and your worker runs registered durable handlers.
No. wrap() runs a local function in your process. Use enqueue() and a separate worker for crash recovery.
No. Durable execution is at least once. Pass a stable idempotency key to the destination for payments, writes, and email.
Check worker heartbeat, exact handler version, key scope, service pause, circuit state, and database health.
No. An owner or admin reviews the current dry-run plan and acknowledges duplicate risk. Model output cannot schedule work.
Completed details are retained for 90 days by default. Admins can choose 30–365 days; unfinished work is kept.