Loading video...

Video Failed to Load

Go Home

we released our react package build an ai chat w/ interactive components in a few lines of code. add it to your app with: npx tambo full-send we support: - streaming for both messages and components - message history and message threads - state manage for generated components -...

65,473 views • 1 year ago •via X (Twitter)

10 Comments

Michael Magán's profile picture
Michael Magán1 year ago

check out this demo at

PDF GPT's profile picture
PDF GPT2 years ago

This is my favorite AI tool for reviewing reports. Just upload a report, ask for a summary, and get one in seconds. It's like ChatGPT, but built for documents. Try it for free.

Anicet's profile picture
Anicet1 year ago

I need an option to use OpenRouter instead of OpenAI for this, I see myself using this in production if it does

Michael Magán's profile picture
Michael Magán1 year ago

on the roadmap. what are you building?

Atai Barkai's profile picture
Atai Barkai1 year ago

Congratulations on the launch!! Very nicely done

Michael Magán's profile picture
Michael Magán1 year ago

thanks! 🙏

Bee 🐝's profile picture
Bee 🐝1 year ago

I like the name tambo

Michael Magán's profile picture
Michael Magán1 year ago

thanks

Dylan Meade's profile picture
Dylan Meade1 year ago

Congrats on the launch!

osco ᯅ 🇸🇻's profile picture
osco ᯅ 🇸🇻1 year ago

new micheal app dropped 👀

Related Videos

React tip: "use client" misconceptions (2/5) 🚫 "You cannot nest Server Components inside Client Components because "use client" turns everything into Client Components." ✅ We can pass the rendered result of Server Components to Client Components as props. Simple example: (Server Component) (Client Component) (Server Component) is designed for the client. It needs to instantly open and close when clicked. is designed for the server. It uses packages that don't work in the browser and needs to fetch data close to where it's stored without exposing credentials. So, how can we nest a component that uses server APIs inside a component that uses client APIs... without using `import`? React props to the rescue! --- (0:00) 1-4: Reminder: Importing code forms a module dependency graph. Adding dependencies to a server or client bundle. (0:23) 5-6: Reminder: Using components eventually forms a rendered component tree. (0:37) 9: Oh no! We get an error when trying to `import` a client API (useState) into a server module. (0:44) 10: We know the trick by now: Add "use client" to mark `2.js` as a client entry point. This moves the module to the client bundle and allows us to use client APIs like `useState.` (0:51) 11: But we get a new error! "use client" moved all imported dependencies into the client bundle, including our ORM package, which doesn't work in the browser. (0:59) 13: Let's refactor without changing our rendered component hierarchy. First, we move the `Cart` import to the parent file that imports `Modal`. This moves `Cart` outside the "use client" boundary and consequently the client bundle. (1:11) 15: Then, we pass down the rendered result of `Cart` as a prop to `Modal`. This allows `Cart` to be entirely rendered on the server as a Server Component before being passed down. `Modal` has no knowledge of what the `cart` prop is. Its only responsibility is placing whatever it receives into the `{cart}` slot. (1:15) 16: Finally, it's common to use the special `children` prop for a component's primary content. The key insight is that we were able to use props to retain our desired component hierarchy even though we changed our module dependency graph.

Delba

43,989 views • 2 years ago