Skip to content

Commit 9c8861a

Browse files
committed
nanobot support remote-dom
1 parent ac56986 commit 9c8861a

File tree

1 file changed

+0
-5
lines changed
  • exercises/02.consistent/01.problem.remote-dom

1 file changed

+0
-5
lines changed

exercises/02.consistent/01.problem.remote-dom/README.mdx

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,5 @@
11
# Remote DOM
22

3-
<callout-warning>
4-
As of the time of this writing, no popular AI Agent apps support MCP-UI with
5-
Remote DOM, so you'll need to use your imagination 🌈
6-
</callout-warning>
7-
83
👨‍💼 When users interact with our journaling app, they expect a consistent, professional experience that feels native to the application they're using. Right now, our tag viewer uses raw HTML which means our UI is rendered in an iframe and cannot resemble the variety of agents using our MCP server because it can't integrate with the host application's design system. Users notice this inconsistency and it makes our app feel less polished and trustworthy.
94

105
The problem is that raw HTML gives us complete control but also complete responsibility for every aspect of the user interface. This leads to a fragmented user experience where each UI component feels like it belongs to a different application.

0 commit comments

Comments
 (0)