Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Tambo 1.0: Open-source toolkit for agents that render React components

github.com

Post reply on HN
Print view View original

21–27 of 27 posts

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#21

Post by fitzgera1d »

milst wrote: post #10
fitzgera1d wrote: post #7

There’s an MCP Apps version of this that is interesting: https://creature.run Maybe I’m misunderstanding, but isn’t generating UI just-in-time kind of risky because AI can get it wrong? Whereas you can generate/build an MCP App once that is deterministic, always returns a working result, and just as AI native.

With this you build your own React components and register them with the AI. The AI chooses which to use and what props to pass into them, so it's not generating UI from scratch, if that's what you mean - other Michael from the Tambo team

I see. how often does AI get the components wrong? This is my big question wrt just in time generative ui. UI built beforehand (also likely generated by ai but vetted by eng team) feels like it has the win here. Why take on risks of non determinism if you don’t have to. This feels like the big pro for mcp apps.

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#22

Post by oulipo2 »

grouchy wrote: post #11
dzogchen wrote: post #8

I don’t understand what this does. Who would use this and why? I need an ELIF. Edit: Announcement was more clear https://tambo.co/blog/posts/introducing-tambo-generative-ui Can it also generate new components?

You install the React SDK, register your React components with Zod schemas, and then the agent responds to users with your UI components. Developers are using it to build agents that actually solve user needs with their own UI elements, instead of text instructions or taking actions with minimal visibility for the user. We're building out a generative UI library, but as of right now it doesn't generate any code (that…

Okay but I fail to see how this is "new tech"?

Basically it's just... agreeing upon a description format for UI components ("put the component C with params p1, p2, ... at location x, y") using JSON / zod schema etc... and... that's it?

Then the agent just uses a tool "putCompoent(C, params, location)" which just renders the component?

I'm failing to understand how it would be more than this?

On one hand I agree that if we "all" find a standard way to describe those components, then we can integrate them easily in multiple tools so we don't have to do it again each time. At the same time, it seems like this is just a "nice render-based wrapper" over MCP / tool calls, no? am I missing something?

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#23

Post by grouchy »

eagleinparadise wrote: post #19

Does this support standard schema?

It does!

import { z } from "zod";

inputSchema: z.object({ query: z.string() });

or

import * as v from "valibot";

inputSchema: v.object({ query: v.string() });

or

import { type } from "arktype";

inputSchema: type({ query: "string" });

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#24

Post by grouchy »

fitzgera1d wrote: post #21
milst wrote: post #10

Earlier quoted context omitted.

With this you build your own React components and register them with the AI. The AI chooses which to use and what props to pass into them, so it's not generating UI from scratch, if that's what you mean - other Michael from the Tambo team

I see. how often does AI get the components wrong? This is my big question wrt just in time generative ui. UI built beforehand (also likely generated by ai but vetted by eng team) feels like it has the win here. Why take on risks of non determinism if you don’t have to. This feels like the big pro for mcp apps.

It get's it wrong sometimes but I think the alternative is the user getting it wrong trying to navigate your site.

I like to think how much time I spend clicking different nav links, clicking different drop downs trying to find the functionality I need.

It's just a new way for the app to surface what the user needs when they need it.

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#25

Post by grouchy »

_the_inflator wrote: post #20

I got you an my watch list for quite some time and will definitely give you a try. It sounds promising, because it is on the outside reproducible deterministic component generation in a modern fashion as far as I understood it. I build a large platform using a methodically comparable approach I suppose, albeit in the pre-AI time, and that's why I wanna have a closer look at the inner workings and results of your proj…

Glad you like the approach. When you give it a spin or look into the implementation please let us know what you think.

We are constantly improving tambo. It's crazy to see how much it's improved since we first started.

Re: Tambo 1.0: Open-source toolkit for agents that render React components

#26

Post by milst »

oulipo2 wrote: post #22
grouchy wrote: post #11

Earlier quoted context omitted.

You install the React SDK, register your React components with Zod schemas, and then the agent responds to users with your UI components. Developers are using it to build agents that actually solve user needs with their own UI elements, instead of text instructions or taking actions with minimal visibility for the user. We're building out a generative UI library, but as of right now it doesn't generate any code (that…

Okay but I fail to see how this is "new tech"? Basically it's just... agreeing upon a description format for UI components ("put the component C with params p1, p2, ... at location x, y") using JSON / zod schema etc... and... that's it? Then the agent just uses a tool "putCompoent(C, params, location)" which just renders the component? I'm failing to understand how it would be more than this? On one hand I agree that…

It's that plus the hosted service which interacts with the LLM, stores threads, handles auth, gives observability of interactions in your app, etc.
Post reply on HN