by @chiefofautism on twitter

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

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.

Interesting, reminds me a little of another project posted here a few weeks ago: https://news.ycombinator.com/item?id=45823938

Very interested in the idea of an AI being able to interact with my filesystem.

we experimented with something like this: https://local-note-taker.vercel.app/chat

repo in case you'd rather run it locally: https://github.com/tambo-ai/local-note-taker

Curious to compare how our two ideas are built differently, feel free to reach out (email in my profile)

started something like this, but without the "zoom" https://timeline-of-everything.milst.dev/

very cool. Made something with a similar idea, but using timelines instead of maps. I wonder if the two could be combined in some way https://timeline-of-everything.milst.dev/

Nice, how does your timeline work under the hood? Does it read from wikipedia? What could be interesting in your project is to be able to compare timelines. See for instance this website specifically for comparing composer works (with timelines pre-extracted from wikipedia):

https://zulko.github.io/composer-timelines/?selectedComposer...

under the hood messages are sent to Tambo which knows how to use the timeline component (sort of like an LLM tool) and can fill the component's props with whatever data it decides. The actual data at this point is completely generated by the LLM (which seems to be ok for historical data on popular topics.) I should add a tool to allow tambo to fetch data from wikipedia before trying to generate timeline data.

Comparing timelines is an awesome idea, understanding when certain events happened in relation to others is really interesting. Maybe even overlaid in different colors or something instead of separate timelines.

Here's the repo btw: https://github.com/MichaelMilstead/timeline-of-everything

Very cool. Are the posts I see random from all stored, or are they the latest posts or something?

They're random from the entire set. There's only about 90 posts at the time of writing. I did disable a few... somebody was very keen to express their love for genitalia lol

This is awesome. I worked on a 'conversational historical timeline generator' a little bit ago: https://timeline-of-everything.milst.dev/

I wonder if something similar could be added here where I say something like "what's the most important descendant of x" and it would bring me to that tech and give me a little explanation of why

updated the 'overview' generation