Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Binary file added public/blog-assets/tanstack-ai-beta/header.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
154 changes: 154 additions & 0 deletions src/blog/tanstack-ai-beta.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,154 @@
---
title: 'TanStack AI Beta: The Switzerland of AI Tooling Grows Up'
published: 2026-06-09
excerpt: Six months ago we shipped the alpha with a promise - a framework-agnostic, provider-agnostic AI toolkit with no lock-in, ever. Today TanStack AI hits Beta with every modality, a hardened protocol, middleware, orchestration, host-side MCP, and 147 E2E tests running across 7 providers on every PR.
library: ai
authors:
- Tom Beckenham
---
Comment on lines +1 to +8

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Add headerImage to YAML front matter.

The header image is referenced on line 10, but the headerImage field is missing from the YAML front matter. Based on the blog metadata contract in src/utils/blog.functions.ts, headerImage is a supported field that should be declared here for proper metadata association.

📝 Proposed fix
 ---
 title: 'TanStack AI Beta: The Switzerland of AI Tooling Grows Up'
 published: 2026-06-09
 excerpt: Six months ago we shipped the alpha with a promise - a framework-agnostic, provider-agnostic AI toolkit with no lock-in, ever. Today TanStack AI hits Beta with every modality, a hardened protocol, middleware, orchestration, host-side MCP, and 147 E2E tests running across 7 providers on every PR.
 library: ai
+headerImage: /blog-assets/tanstack-ai-beta/header.png
 authors:
   - Tom Beckenham
 ---
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
title: 'TanStack AI Beta: The Switzerland of AI Tooling Grows Up'
published: 2026-06-09
excerpt: Six months ago we shipped the alpha with a promise - a framework-agnostic, provider-agnostic AI toolkit with no lock-in, ever. Today TanStack AI hits Beta with every modality, a hardened protocol, middleware, orchestration, host-side MCP, and 147 E2E tests running across 7 providers on every PR.
library: ai
authors:
- Tom Beckenham
---
---
title: 'TanStack AI Beta: The Switzerland of AI Tooling Grows Up'
published: 2026-06-09
excerpt: Six months ago we shipped the alpha with a promise - a framework-agnostic, provider-agnostic AI toolkit with no lock-in, ever. Today TanStack AI hits Beta with every modality, a hardened protocol, middleware, orchestration, host-side MCP, and 147 E2E tests running across 7 providers on every PR.
library: ai
headerImage: /blog-assets/tanstack-ai-beta/header.png
authors:
- Tom Beckenham
---
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/blog/tanstack-ai-beta.md` around lines 1 - 8, Add the missing headerImage
field to the YAML front matter of this Markdown post so the blog metadata
contract in blog.functions.ts can associate the image; update the front matter
block (the top --- section) to include headerImage: with the correct image path
or filename referenced by the content (the image used on line 10), ensuring the
key name is exactly "headerImage" to match the metadata schema.


![TanStack AI Beta](/blog-assets/tanstack-ai-beta/header.png)

**The TanStack team is thrilled to announce the Beta release of [TanStack AI](/ai), the framework-agnostic, provider-agnostic AI toolkit built for developers who want control over their stack.**

When we [shipped the alpha back in December](/blog/tanstack-ai-alpha-your-ai-your-way), we made a promise. No vendor lock-in. No platform to migrate to. No framework dictating how you build. Just honest open source tooling - the Switzerland of AI - that works with the stack you already have.

Six months and a long list of releases later, that promise still holds. But the toolkit behind it has grown up. What was a handful of adapters and an early protocol is now a complete, multi-modal, multi-framework AI platform.

This is the Beta.

## TL;DR

- **Every modality.** Text, streaming structured data, tool calls, embeddings, summarization, image generation, audio generation, video generation, and realtime voice. One typed API, any provider.
- **Built on AG-UI.** AG-UI is at the core of the protocol, not bolted on. TanStack AI speaks AG-UI events end to end, so it drops into the broader agent-UI ecosystem instead of inventing its own dialect.
- **A hardened, published protocol.** The server↔client contract is documented and stable, over any transport.
- **Adapters split by capability.** Smaller, composable adapters instead of one monolith, with per-model type safety that catches incompatible pairings at compile time.
- **First-class middleware.** Logging, filtering, caching, and rate limiting compose cleanly instead of bloating your endpoint.
- **Host-side MCP.** Connect one Model Context Protocol server or a whole pool, with the type-safety level you choose.
- **Experimental orchestration.** Generator-based workflows, typed agent calls, approvals, and streaming events for multi-step agentic systems.
- **Tested for real.** 147 deterministic E2E tests across 7 providers, running on every PR in under two minutes.

## What "Beta" Means

The alpha was a bet on an architecture. We told you there would be bugs, rough edges, and APIs that might change, and there were. We prototyped through [an `ai()` function we had to kill](/blog/tanstack-ai-the-ai-function-postmortem), [re-architected the adapters](/blog/tanstack-ai-why-we-split-the-adapters), and [rebuilt the modality story twice](/blog/tanstack-ai-alpha-2) before we were happy.

Beta means the bet paid off. The core APIs are stable. The protocol is documented and versioned. The surface area is broad enough to build a real product on, and the testing infrastructure is strong enough that we trust it. We're no longer asking you to take a chance on a prototype. We're asking you to build with us.

## Every Modality, One API

The biggest change since alpha is breadth. TanStack AI is no longer a text-generation library with extras bolted on. Every major modality is a first-class, typed activity:

- **Text and streaming structured data**: stream typed objects as they're generated, not just tokens, so your UI can render structured results progressively.
- **Tool calls**: defined once, with isolated server and client implementations and type safety that holds across the whole app.
- **Embeddings and summarization** out of the box.
- **Image generation** across providers.
- **Video generation** through the same typed activity model: swap the provider, keep your code.
- **[Audio generation](/blog/tanstack-ai-audio-generation)**: music, sound effects, text-to-speech, and transcription via a streaming `generateAudio` activity, with fal and Gemini Lyria adapters.
- **[Realtime voice chat](/blog/tanstack-ai-realtime-voice-chat)**: real voice, real time, with OpenAI Realtime over WebRTC and ElevenLabs over WebSocket, all behind one provider-agnostic architecture.

Here's what that looks like in practice. A chat endpoint on the server:

```ts
import { chat, toServerSentEventsResponse } from '@tanstack/ai'
import { openaiText } from '@tanstack/ai-openai'

export async function POST(request: Request) {
const { messages } = await request.json()

const stream = chat({
adapter: openaiText('gpt-5.2'),
messages,
})

return toServerSentEventsResponse(stream)
}
```

And the client, in React:

```tsx
import { fetchServerSentEvents, useChat } from '@tanstack/ai-react'

function Chat() {
const { messages, sendMessage, isLoading } = useChat({
connection: fetchServerSentEvents('/api/chat'),
})
// render messages however you like
}
```

Switching providers is the import and the adapter. Nothing else moves:

```diff
- import { openaiText } from '@tanstack/ai-openai'
+ import { anthropicText } from '@tanstack/ai-anthropic'

const stream = chat({
- adapter: openaiText('gpt-5.2'),
+ adapter: anthropicText('claude-fable-5'),
messages,
})
```

And every other modality follows the same shape — an adapter in, a typed result out:

```ts
import { generateAudio } from '@tanstack/ai'
import { geminiAudio } from '@tanstack/ai-gemini'

const result = await generateAudio({
adapter: geminiAudio('lyria-3-pro-preview'),
prompt: 'A cinematic orchestral piece with a rising string motif',
})
```

Switch the modality, switch the provider, and the shape of your code stays the same.

## Per-Model Type Safety That Actually Matters

Every provider has different options. Every model supports different modalities and different native tools. TanStack AI types `providerOptions` on a per-model basis, so your IDE knows exactly what each model can do.

That extends to provider tools: native capabilities like web search and code execution that some models support and others silently ignore. As of Beta, [those pairings are gated at the type level](/blog/type-safe-provider-tools-tanstack-ai). Wire an incompatible tool to a model and TypeScript tells you on the line where you pass it, instead of letting it fail quietly in production.

## Composing Real Systems

A toy chat endpoint is easy. A production one accretes logging, content filtering, caching, and rate limiting until it's an unmaintainable monster. Beta ships the pieces that keep that complexity in check:

- **[Middleware](/blog/tanstack-ai-middleware)**: a first-class system so cross-cutting concerns compose instead of pile up.
- **[Lazy tool discovery](/blog/tanstack-ai-lazy-tool-discovery)**: stop spending tokens (and model accuracy) on tool definitions the model doesn't need yet.
- **[Code Mode](/blog/tanstack-ai-code-mode)**: let the LLM write and execute TypeScript in a secure sandbox, composing your tools with loops, conditionals, and `Promise.all` in a single shot instead of one round-trip per call.
- **[Host-side MCP](/blog/your-mcp-your-way)**: connect a single Model Context Protocol server or a whole pool, with managed or manual lifecycle and the type-safety level that fits your app, from zero-config discovery to fully generated end-to-end types.
- **[Experimental orchestration](/blog/tanstack-ai-orchestration)**: generator-based workflows, typed agent calls, human-in-the-loop approvals, SSE streaming, AG-UI events, and React hooks for building multi-step agentic systems.

## TypeScript First, On An Open Protocol

TanStack AI is TypeScript-first. The toolkit, the per-model type safety, and everything you've seen in this post is built for TypeScript end to end. But the thing that makes it all portable is the protocol: we've documented exactly how the server and client communicate, and in Beta it's stable. Speak it over any transport (HTTP, WebSockets, RPC) through a connection adapter, and our clients work with your backend.

**AG-UI is at its core.** The events flowing across that connection are AG-UI events, not a bespoke format with a compatibility shim on top. Because the standard is built in from the ground up, TanStack AI interoperates with the wider agent-UI ecosystem out of the box. It's the same no-lock-in principle, applied to the wire.

On the client side, vanilla JS, React, and Solid are ready, with more frameworks on the way.

## Debugging You Can Actually See

AI pipelines are notoriously opaque: a missing chunk here, a middleware that didn't fire there, a tool call with mystery arguments. TanStack AI ships two answers:

- **[Pluggable debug logging](/blog/debug-logging-for-tanstack-ai)**: flip one flag and the whole pipeline prints itself, with per-category toggles across every activity and adapter.
- **Isomorphic devtools**: a full panel, built on [TanStack Devtools](/devtools), that shows you what the LLM is doing on both sides of the connection.

## Tested Like We Mean It

Confidence at Beta isn't a vibe. It's [147 deterministic end-to-end tests running across 7 LLM providers on every pull request](/blog/how-we-test-tanstack-ai-across-7-providers), all in under two minutes. Provider behavior drifts, models get deprecated, and APIs change underneath you. Our test suite catches it before you do.

## Still Honest, Still Open Source

None of this changes the original deal. There's no service to buy. No platform to migrate to. No vendor lock-in waiting around the corner, and there never will be. TanStack AI is open source, built by the same small, volunteer teams that have shipped framework-agnostic developer tools for years.

We're still taking a lot on, and we still want your help. Build adapters. File the bug you just hit. Tell us what's missing. Beta is the most stable TanStack AI has ever been, but it's not the finish line. It's the version we're confident enough to ask you to build on.

So go build something. It starts with one install:

```bash
pnpm add @tanstack/ai @tanstack/ai-react @tanstack/ai-openai
```

[Get started with TanStack AI](/ai), and tell us what you ship.
Loading