grouchy

ofc.

I just found out that if you use the "player" tag on a page, X will show a "player card," and you can embed a full app into that player. It embeds that page’s live player in a small 480×480 square window right inside the post.

Give it a spin. It's fun.

It's been fun using this in our standups. Thanks for building this.

I have to keep asking the same questions. Do you think it could remember what I typically ask and generate or suggest it?

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.

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.

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" });

I'm curious what would make you say that? Because we haven't experienced this. We are being used a fortune 1000 fintech in production.

Any specific experience you had? or more specifics of where batteries included went to far?

Yeah, we've been following it closely. We already support the majority of the MCP spec and plan to add support for UI over MCP.

But our use case is a little different. MCP Apps embed interfaces into other agents. Tambo is an embedded agent that can render your UI. There's overlap for sure, but many of the developers using us don't see themselves putting their UI inside ChatGPT or Claude. That's just not how users use their apps.

That said, we're thinking about how we could make it easy to build an embedded agent and then selectively expose those UI elements over MCP Apps where it makes sense.

There's overlap for sure. I'd say we've built a more drop-in solution. We actually migrated to AG-UI events under the hood, and we have plans to expand cross-compatibility across standards.

The major difference is we provide an agent. You don't need to bring your own agent or framework. A lot of our developers are using our agent, really happy with it, and we have a bunch of upcoming features to make it even better out of the box.