正在加载视频...

视频加载失败

Introducing CoAgents v0.2🪁🦜🚀 Build full-stack Agent-Native Apps with LangGraph 🤝 CopilotKit (Like Cursor for __) Including: ✨Agentic UI/UX + Frontend 🪢 Shared state (agent app) 👨‍🦰Human-in-the-Loop 🦜Full LangGraph Platform support (Python, JS, Cloud) Get Started: Check out the demo:

32,118 次观看 • 1 年前 •via X (Twitter)

10 条评论

Csaba Kissi 的头像
Csaba Kissi1 年前

Awesome news! Good luck guys!

Arindam Majumder 𝕏 的头像
Arindam Majumder 𝕏1 年前

Amazing Work Team!

Akshay 🚀 的头像
Akshay 🚀1 年前

This is amazing! Thanks for sharing!

Avi Chawla 的头像
Avi Chawla1 年前

This is great! Can't wait to try this out.

Caleb John 的头像
Caleb John1 年前

Let’s gooo

Josue 的头像
Josue1 年前

do you like it @vykthur ?

Michael 🥶 Cold Outreach 的头像
Michael 🥶 Cold Outreach1 年前

I have to try this out!

Chirag Aggarwal 的头像
Chirag Aggarwal1 年前

amazingg!

Pheonix Coder 的头像
Pheonix Coder1 年前

Less go 🔥🔥

Akash Jana 的头像
Akash Jana1 年前

On my way to try it out! Let's go ✨

相关视频

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.

Avi Chawla

455,742 次观看 • 1 个月前

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 次观看 • 18 天前