Skip to content

Clarify TanStack AI durability setup #1175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tannerlinsley wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Open

Clarify TanStack AI durability setup #1175

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa601d3
Clarify TanStack AI durability setup
tannerlinsley Aug 22, 2026
0745211
Use accurate AI middleware terminology
tannerlinsley Aug 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/blog/tanstack-ai-rc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Our initial goal was to create an architecture that could be easily extended not

One of the biggest payoffs since we started has been making the right architectural decisions early and building everything on top of those foundations. One of the strongest parts of that architecture is our [middleware system](https://tanstack.com/ai/latest/docs/advanced/middleware).

You can build just about anything with middleware. Chat persistence, agent harnesses running inside sandboxes, memory, telemetry, durability, and many other features are simply middleware functions that you pass into your `chat()` method.
You can build just about anything with middleware. Chat persistence, agent harnesses running inside sandboxes, memory, telemetry, and many other features are middleware you pass into your `chat()` method. Durability is separate and plugs into the streaming response through an adapter.

Another powerful feature we offer is [lazy tool calling](https://tanstack.com/ai/latest/docs/tools/lazy-tool-discovery), which can help reduce token costs with a simple Boolean flag. We also support advanced [interrupt scenarios](https://tanstack.com/ai/latest/docs/interrupts/overview) driven by your schemas. You can modify tool-call arguments, trigger multiple interrupts, and mix and match these capabilities while keeping everything completely type-safe from end to end.

Expand Down
Loading