正在加载视频...

视频加载失败

TanStack AI now has subagents 🤖 Define agents once, pass them to chat(), and each one streams its own card in your UI. Jev routes every message to the right agents, in parallel or in order⚡

30,764 次观看 • 2 天前 •via X (Twitter)

10 条评论

TANSTACK 的头像
TANSTACK2 天前

Find the docs here:

MONARCH 的头像
MONARCH2 天前

Feels like Tanstack AI is the only Tanstack library receiving updates 😞

Webster | JARVIS 的头像
Webster | JARVIS2 天前

love the parallel streaming cards way nicer than one long assistant blob how does Jev decide order vs parallel routing?

Jeremy Longworth 的头像
Jeremy Longworth2 天前

This is a clean example of orchestration moving into the framework layer. Define specialized agents once, route work by intent, run them in parallel or sequence, and keep their outputs visible in the UI. That’s a much more useful abstraction than “one agent does everything.”

Alem Tuzlak 🇧🇦 的头像
Alem Tuzlak 🇧🇦2 天前

Man @typesafeai was really the missing piece we needed all along

Automater 的头像
Automater2 天前

The UI card is useful only if it carries execution context: input slice, tools called, and exit condition. Otherwise parallel cards just turn one opaque blob into several smaller opaque blobs.

RusticStack 的头像
RusticStack2 天前

Jev picks parallel when no child needs another child's text, and sequence only when a later agent must read the earlier one.

John Rood 的头像
John Rood2 天前

fan-out is where determinism dies quietly: each subagent should read a frozen input slice taken at spawn, not the shared live conversation. otherwise results depend on who read when, and the same message lands in different cards on a rerun. freeze the inputs, merge the outputs.

Ash Designs 的头像
Ash Designs2 天前

One card per agent streaming in parallel is a nice default. The hard part for users is knowing which card to trust when two disagree. Any plans for a merged summary view?

Fajar M Reza 的头像
Fajar M Reza2 天前

Streaming each specialist’s card could make parallel agent workflows easier to debug.

相关视频