@dbos-inc/vercel-ai weekly downloads statistics

@dbos-inc/vercel-ai

DBOS durable execution for the Vercel AI SDK.

This package makes AI SDK agents durable, backed by your Postgres database. All you have to do is wrap your model with durableCalls and your tools with durableTools and run your agents inside a DBOS workflow. Then, this integration automatically checkpoints every action your agents take in Postgres. If your process is interrupted, DBOS replays your agent from its checkpoints so it resumes from where it left off.

Installation

Requires DBOS v4.27+ or v5, AI SDK v7+, and a Postgres database for DBOS.

Durable Model Calls

To durably checkpoint each call you make to a model, wrap your model in durableCalls. Then, call your model or agent from a workflow:

You can parameterize durableCalls to configure model call retries and timeouts:

Durable Tools

To durably checkpoint your agents' tool calls, wrap them in durableTools:

You can pass step configuration (such as timeouts or retries) to durableTools. You can set defaults for all tools or configure tools individually. Retries are off by default.

When using durable tools, to ensure the ordering of parallel tool calls is consistent during recovery, do not await I/O in callbacks that run before a tool executes, such as onToolExecutionStart.

Durable Streams

You can durably stream agent or model output so it can be read by an external client or UI. To do this, configure durableCalls or durableTools/durableMCPTools with a durable stream name:

You can read from a durable stream using readDurableStream, for example to stream it to a UI. It emits a stream of AI SDK UIMessageChunk. You can also pass a DBOSClient into readDurableStream to read it from a different process.

You can write your own data to a stream with writeDurableStream(key, chunks). Tools can also write chunks with toolWriter(), which returns a UIMessageStreamWriter bound to the current tool call. Chunks from a tool call are written when the tool call succeeds (transient: true data parts are written live instead). To also include them in the response message your workflow builds, pass your createUIMessageStream writer to durableTools:

Your streams are closed when your workflow finishes; you can also close a stream early using closeDurableStream.

If a workflow is interrupted during a model call, when the workflow recovers, it restarts the model call and streams its output again. Readers that connect afterwards see the model's output once; live readers, including readers resumed from an offset, receive a transient data-dbos-superseded chunk indicating the model call has been restarted. Likewise, if a tool call is re-executed and writes different chunks, readers that connect afterwards see only the re-execution's chunks; live readers receive a transient data-dbos-tool-superseded chunk naming the toolCallId whose earlier chunks to discard.

Durable MCP Tools

durableMCPTools wraps an MCP client (for example, from @ai-sdk/mcp) so both the tool listing and every tool call run as durable steps:

To use the client's explicit-schema mode (tool subsetting, typed inputs, output schemas), pass toolOptions; it is forwarded to client.tools() for both the listing and each tool call:

Durable Subagents

You can delegate complex tasks to subagents, which act as tools for their "parent" agent. To create a durable subagent, wrap your agent in agentTool, then pass it into durableTools just like any other tool:

Internally, subagents are implemented as child workflows of the parent agent workflow, so each call has its own checkpoints and parallel calls are safe. Call agentTool before DBOS.launch(), since it registers that workflow. By default, the tool returns the subagent's final text; you can configure this with the output parameter.

Durable Embedding Models

durableEmbeddingCalls enables durable calls to embedding models:

Durable Image Models

durableImageCalls makes image generation durable:

Description from the npm listing.