Skip to content

Guides for long-runningagents.

Each guide starts from a failure we or other developers have hit, shows the cause, and ends with code that runs without Argentic. Where Argentic is one way to fix it, it says so once, near the end.

When something happens twice

The refund, the email or the ticket goes out more than once. The cause is usually a retry, a resume or a model asking twice.

When a run dies halfway

A deploy, a time limit or a crash stops the process. These cover getting back to where you were without redoing finished work.

Trust, approval and cost

Letting an agent run for hours raises questions about who approved what, whether the record can be trusted, and what the session costs.

By framework

If you already use one, start with its guide: Vercel AI SDK, OpenAI Agents SDK, LangGraph, Mastra or Pydantic AI.