Vercel Connect now lets agents authenticate TanStack AI MCP clients at runtime. Tokens are issued per request and consent lives at the route boundary, so nothing sensitive ever sits in your environment. A clean way to wire up agent auth. vercel.com/changelog/vercel-…

migrated a fully functioning app from nextjs to tanstack start to move away from vercel to cloudflare in under 3 hours can't imagine building without ai anymore

Went for a run and ended up talking about AI, open source, and the long road to TanStack Charts. Put together a recap, transcript, and recording if you’d like to read or listen: tannerlinsley.com/posts/ai-o…

Who knew I’d come around to directives 😜 Working on a new project using TanStack Start/Router, DB, AI, Query, Table, Markdown, Highlight, Virtual, Charts, and Hotkeys 🔥 A couple of these were just a default from the agent. The others only took one “use TanStack” 🪄 So cool

Meta Muse builds apps with @Tan_Stack

OpenMuse is powered by TanStack AI 🌴

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⚡

Haha crazy how things have changed. Now we use Tanstack

Saving 50-60 MBs on Fluid function invocation on @vercel after moving Tanstack Start (nitro) application from @bunjavascript 1.3.14 to Bun 1.4.1 runtime. 📉

BRB need to do this right now

I shipped a rather large update to TanStack Hotkeys yesterday, which adds much better physical key support options, instead of mostly relying on event.key with only event.code fallbacks like before. This was an overdue correction that was needed! The string templates still use event.key matching by default, but now, if you want to force a physical key check, you can just use `[]` around a physical key code, like the screenshot down below. Hotkey recording now defaults to physical key recording in order to fix multiple bugs across different layouts. This is configurable. From my testing, if you define hotkeys with our initial event.key string templates, you should actually have a pretty safe setup already. It's really the custom hotkey recording features that add a lot of complexity and bugs, and now I think we're closer to addressing those issues with this latest update. Would love people to try this out and help report remaining issues with TanStack Hotkeys before we move to beta.

Ciao NextJS, bonjour Tanstack: histoire d’une migration pimpée à l’IA news.humancoders.com/t/dev-f…

🎉 To no one's surprise, Jev support just landed in TanStack AI via `decide()`, our new API for typed choices, scores, and booleans. We're excited to use this new API with more models soon, but for now the "jevolution" is in full swing! Jev on, ya'll.

new post: the senior engineer death spiral sunilpai.dev/posts/the-senio… a friend just started a big job and asked for some advice. so I braindumped a monologue about a super common failure mode I see with engineers and posted it here, hope it helps whoever it can.

It has been over 6 weeks since we released TanStack Table V9, and it has been... surprisingly quiet. V9 is already getting a couple million downloads per week, but there's barely been any issues opened, and we fixed the few that were reported in week 1. I think that our V8->V9 migration guide is really good and comprehensive, but could that alone be why it's going so smoothly for everyone? Or if there actually are problems in V9, does everyone's AI agents just know how to workaround those issues and they just go unreported now?