Post

🚀 Introducing aibind — AI SDK bindings for every JS framework ⚡ Reactive streaming 🌿 Branching chat history 🤖 Agents & tool calling 🔄 Model switching & racing 📝 Streaming markdown 💾 Durable streams SvelteKit · Next.js · Nuxt · SolidStart · TanStack · React Router

6/3/26, 4:48 pm3 reposts11 likes

Axel Rock

@axelrock.com

7 Mar

I’ll take a deep look, it sounds very interesting. I tried to build all of this myself, not that easy

{PuruVijay}.svelte

@puruvj.dev

9 Mar

Sure do! And let me know what problems you had to endure

Michael

@svelte-apps.me

16 Mar

This looks interesting, but you should have added the GitHub link or live docs page

{PuruVijay}.svelte

@puruvj.dev

6 Mar

Why does this exist? Every time I built an AI feature, I was writing the same plumbing: - wire up the stream - parse chunks into state - handle errors mid-response - manage conversation history - figure out markdown rendering None of that is the actual product. aibind handles all of it.

{PuruVijay}.svelte

@puruvj.dev

6 Mar

Streaming in your framework should feel native. In Svelte: stream.text is a reactive $state In Vue: stream.text is a ref In React: it's just a hook Same API everywhere. No adapters, no wrappers, no fighting the runtime.

{PuruVijay}.svelte

@puruvj.dev

6 Mar

Chat history is deceptively hard. Edit a past message? That's a branch. Regenerate? Another branch. aibind ships a full message tree — edit anywhere, branch anywhere, navigate back and forward. Like git, but for conversations.

{PuruVijay}.svelte

@puruvj.dev

6 Mar

You don't want your most expensive model answering "what's 2+2". aibind lets you define named models and route automatically: routeModel: (prompt) => { if (prompt.length < 200) return "fast" if (/explain|analyze/.test(prompt)) return "reason" return "smart" }