Agents now visit your product the way customers do, and most products make them fumble. An agent that reaches a website usually reads the page structure and clicks around a layout built for a person with a mouse. Speaking to developers in San Francisco on Nov. 18, I argued that this is a design problem we can fix.
Read the full walkthrough on open.bot
WebMCP is the better route. You expose parts of your site's functionality to the agent directly, which takes far fewer tokens than working through the page. If your app already uses CopilotKit, its frontend tools can be exposed through WebMCP too.
The design work runs the other way as well. When your customers use their own agent, your product shows up inside that agent's chat, and that view needs the same care. CopilotKit's AG-UI protocol supports chat panels in apps, terminal agents and personal agents.
I showed the third case live with OpenBot™, CopilotKit's desktop workspace for AI coworkers. The walkthrough on open.bot covers the demo and lets you jump to any part of the video.
Full walkthrough: OpenBot™ Lets You Lead AI Coworkers Built on Any Agent, Any Model, Any Server



Subscribe to our blog and get updates on CopilotKit in your inbox.