Skip navigation
TanStack AI now has subagents 🤖
0:00 / 1:04

TanStack AI now has subagents 🤖

TANSTACK

@tan_stack69K followers

Visit on X
268 likesDownloadOriginal post

32,574 views

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⚡

10 Comments

Comments from the original post on X (Twitter)

  • TANSTACK's profile picture

    @tan_stack

    Find the docs here:

    6 likes

  • MONARCH's profile picture

    @ugbahisioma

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

    2 likes

  • Webster | JARVIS's profile picture

    @websterweby

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

    2 likes

  • Jeremy Longworth's profile picture

    @Jeremylongworth

    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.”

    1 like

  • Alem Tuzlak 🇧🇦's profile picture

    @AlemTuzlak

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

    1 like

  • Automater's profile picture

    @automater_ai

    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.

    1 like

  • RusticStack's profile picture

    @RusticStack

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

    1 like

  • John Rood's profile picture

    @johnroodepic

    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.

    1 like

  • Ash Designs's profile picture

    @dezign_ash

    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?

    1 like

  • Fajar M Reza's profile picture

    @FReza1984

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