Niches · Agent frameworks & SDKs

Run a long or scheduled agent job that survives restarts

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
18companies, fit with a limit
25companies carry the tag
11share of the category's work
9first-hand accounts

What counts as done

State is written to a named durable store after each step, a run killed mid-way resumes from the last completed step with a documented rule for the tool call that was in flight, cancelling keeps what was already streamed, and the docs show resume across a code change or new agent ids.

Measured, for our own tests: kill the process during step 3 of 5 and count repeated tool calls on resume. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: run this report for every customer each night, resume the agent where it stopped after a crash, keep the conversation after the server restarts, cancel a run and carry on the thread

Does the job, with a limit 18

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
AgentOS A
Framers Lab, Inc.
SqlCheckpointStore (SQLite or Postgres) ships, and resume marks write and external nodes complete with their recorded output while failed nodes re-run. The docs don't cover resume across code changes or what a cancel keeps. source
Agno BB
Agno Inc.
Runs persist to SQLite or Postgres and continue by run_id in a new process. I found no rule for a tool call in flight at a crash, and resume across code changes isn't documented. source
BoxLang AI B
Ortus Solutions, Corp.
A checkpointer memory (cache or jdbc) stores suspended state and cancelRun stops at the next beforeLLMCall or beforeToolCall. No documented rule for a tool in flight at a crash or resume across code changes. source
Claude Agent SDK BB
Anthropic, PBC
Sessions persist and resume by id, and a SessionStore mirrors transcripts to your own store so a new container can hydrate. I found no rule for a tool call in flight when the process died; state on the container disk is lost on restart without a store. source
CrewAI C
CrewAI, Inc.
Checkpointing ships JsonProvider and SqliteProvider; a restore skips completed tasks and rehydrates memory. No Postgres or Redis store, no rule for an in-flight tool call, and lambdas and bound-method callbacks are not restored. source
Cursor Agent SDK B
Anysphere, Inc.
Sessions keep an append-only record of messages and tool calls that survives a restart, stop records turn.failed as cancelled, and tool effects mark writes run-once. The store is not named and resume across code changes isn't covered. source
Docker Agent BB
Docker, Inc.
Every message, tool call and sub-agent run is stored in a SQLite session.db and a run resumes by session id. No rule for a tool call in flight at a crash, and resuming mid-run differs from continuing a conversation. source
Agent Development Kit (ADK) BB
Google LLC
ResumabilityConfig logs completed steps and reinstates tool results, re-running the interrupted tool so tools run at least once; resume after modifying the workflow is not supported, and resume isn't available from ADK Web or the CLI. source
guilds.run C
Cigale AI
Runs live in PostgreSQL; on restart, unfinished committed tool calls get an interrupted result, pending group dispatch resumes, and routines wake agents on schedules. Resume across a code change isn't documented, and a run that hit its tool-call cap can't be resumed. source
LangGraph BB
LangChain, Inc.
Postgres, SQLite and MongoDB checkpointers ship; checkpoints land at super-step boundaries and resume re-runs the node at least once, with idempotency-key guidance. Accounts: cancelling a run loses state since the last checkpoint (langgraph #5672, open) and Redis resume failed (#5074). source
LlamaIndex Framework BB
LlamaIndex, Inc.
Context.to_dict() snapshots a run for any store, resume re-dispatches pending events and re-runs a step that was mid-execution (at-least-once), and a DBOS integration exists. You write the store; an account hit serialisation errors for Gemini function calls in Postgres (llama_index #19992). source
Mastra A
Kepler Software, Inc.
Durable agents run the loop inside a workflow; with Inngest each tool call is a memoized step retried independently. Storage is libSQL, PostgreSQL or MongoDB. Agent run snapshots are deleted when the run finishes, and resume across code change isn't covered. source
Microsoft Agent Framework A
Microsoft Corporation
Workflow checkpoints at superstep ends go to in-memory, file or Cosmos DB storage, and the Durable Task extension keeps agent sessions across crashes for days. Upgraded workers need replay-compatibility checks, and agent-id changes broke resume for one account (#4793). source
OpenAI Agents SDK AA
OpenAI OpCo, LLC
Sessions ship for SQLite, SQLAlchemy, Redis and Dapr, and a RunState serialises with to_string() to resume an interrupted or cancelled run. No rule for a tool call in flight at a crash was found. source
Pydantic AI AA
Pydantic Services Inc.
Nine durable engines (Temporal, DBOS, Prefect, Restate, AWS Lambda and more) journal model and tool calls so a run survives a crash mid-step, and StepPersistence saves, resumes and forks runs. The overview doesn't cover resume across code changes or what a cancel keeps. source
Strands Agents A
Amazon Web Services, Inc.
Session managers persist to local disk or S3 (SnapshotSessionManager recommended), with snapshot_latest used to resume after a restart. No Postgres or Redis store and no rule for a tool call in flight; the in-memory history gap of strands #33 is closed. source
TradingAgents B
Tauric Research
Opt-in --checkpoint saves LangGraph state after each node to a per-ticker SQLite database so a crashed run resumes from the last step. No rule for an in-flight tool call; its tools only read data, so repeats have no side effect. source
AI SDK AA
Vercel Inc.
WorkflowAgent from @ai-sdk/workflow runs each tool call as a durable workflow step with retries and survives restarts; ToolLoopAgent itself is in memory. Durability depends on Vercel Workflow, and WorkflowAgent applies no default step limit. source

Doesn't do this job 2

Listings in the category that do something else, with the reason.

ListingWhy
NitroStack C
Nitrostack Inc.
MCP Tasks cover long-running tool calls with progress, cancellation and a TTL, but there is no agent run state or checkpoint store; an account saw tasks still working past their TTL deleted (nitrostack #329, open). source
smolagents B
Hugging Face, Inc.
No checkpoint store or resume page in the docs index; an open account proposes state serialisation because none exists (smolagents #364). source

What stops agents finishing

  • only an in-memory or file checkpoint store ships
  • history with provider-specific function-call objects fails to serialise to the store
  • resume fails when agent ids or code change between runs
  • a cancelled run loses everything after the last checkpoint

Around it

Before: agent-harnesses.scheduled-job. After: human-in-the-loop.durable-wait, agent-observability.debug-failed-run.

Where this comes from

Weight 11 of 100 in Agent frameworks & SDKs: 7 of 61 accounts have this as their main job (share 11.5, rounded by largest remainder to sum 100)

The same as data: /api/v1/use-cases/frameworks.durable-long-run.json, or the MCP tool get_use_case with id frameworks.durable-long-run. Other jobs in this category: /api/v1/niches?category=frameworks.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.