Loading video...

Video Failed to Load

Go Home

Replit, Vercel, and OpenAI have built very cool agent-native applications, but nobody else has passed the demo stage. Building agents that work is complex. Teams aren't shipping agents because we don't have good tooling yet (and most of us don't know how to do this well.) A couple of...

svpino's profile picture

Santiago

452,587 subscribers

63,073 views • 1 year ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

A massive repository with end-to-end examples of AI applications with React! Together with MCP and A2A, the Agent-User Interaction Protocol (AG-UI) is the third piece that will help you build user-facing AI agents. This GitHub repository will give you access to a bunch of examples showing you how to build the following: • Real-time updates between AI and users • Shared mutable state between agents and users • Tool orchestration • Security boundaries • UI synchronization In every one of these examples, you'll get the following: • Client sends a POST request to the agent endpoint • Then listens to a unified event stream over HTTP • Each event includes a type and a minimal payload • Agents emit events in real-time • The frontend can react immediately to these events • The frontend emits events and context back to the agent Check the link in the next post:
0:19

A massive repository with end-to-end examples of AI applications with React! Together with MCP and A2A, the Agent-User Interaction Protocol (AG-UI) is the third piece that will help you build user-facing AI agents. This GitHub repository will give you access to a bunch of examples showing you how to build the following: • Real-time updates between AI and users • Shared mutable state between agents and users • Tool orchestration • Security boundaries • UI synchronization In every one of these examples, you'll get the following: • Client sends a POST request to the agent endpoint • Then listens to a unified event stream over HTTP • Each event includes a type and a minimal payload • Agents emit events in real-time • The frontend can react immediately to these events • The frontend emits events and context back to the agent Check the link in the next post:

Santiago

78,271 views • 11 months ago

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.
0:19

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

30,762 views • 9 months ago

Google ADK 🤝 AG-UI Excited to welcome ADK into the AG-UI ecosystem. Bring your ADK agents into Fullstack applications and allow them to collaborate with users in real time. Includes: - Agent UI (headless UI or pre-built components) - State synchronization (between agent app) - Frontend tool calls - Human-in-the-Loop Demo & more👇
0:15

Google ADK 🤝 AG-UI Excited to welcome ADK into the AG-UI ecosystem. Bring your ADK agents into Fullstack applications and allow them to collaborate with users in real time. Includes: - Agent UI (headless UI or pre-built components) - State synchronization (between agent app) - Frontend tool calls - Human-in-the-Loop Demo & more👇

CopilotKit🪁

33,444 views • 10 months ago

How do you build AI agents that remember and learn from past conversations? Watch this episode of The Agent Factory for a deep dive into building agents with memory, including the fundamentals of agent memory, Vertex AI Memory Bank, and more →
0:18

How do you build AI agents that remember and learn from past conversations? Watch this episode of The Agent Factory for a deep dive into building agents with memory, including the fundamentals of agent memory, Vertex AI Memory Bank, and more →

Google Cloud Tech

12,952 views • 11 months ago

This is how you unlock the next billion software developers. The new Replit ⠕ Agent 3 (they just launched) is the most advanced vibe-coding agent in the world. 1. Smarter than any other vibe-coding model (10x more autonomous than the previous version). 2. It thinks harder and lasts longer than any other model (up to 200 minutes running fully autonomously). 3. The agent can now use an actual browser to test and fix its own code. 4. 3x faster and 10x more cost-effective than any other "Computer Use" for testing. 5. It can build other agents and automations to take care of repetitive tasks. Seeing the agent test the application autonomously is science fiction!
0:16

This is how you unlock the next billion software developers. The new Replit ⠕ Agent 3 (they just launched) is the most advanced vibe-coding agent in the world. 1. Smarter than any other vibe-coding model (10x more autonomous than the previous version). 2. It thinks harder and lasts longer than any other model (up to 200 minutes running fully autonomously). 3. The agent can now use an actual browser to test and fix its own code. 4. 3x faster and 10x more cost-effective than any other "Computer Use" for testing. 5. It can build other agents and automations to take care of repetitive tasks. Seeing the agent test the application autonomously is science fiction!

Santiago

167,056 views • 11 months ago

🤖 How to Build a Team of AI Agents with Agent Forge! What if you could build your own team of AI agents—each with a role, a purpose, and the ability to execute tasks 24/7? With Agent Forge, you can: 🔹 Set Goals 🔹 Assign Roles 🔹 Deploy in Minutes 🔹 Use Real-Time Data 🔹 Chain Agents Together 👉 Get started:
0:13

🤖 How to Build a Team of AI Agents with Agent Forge! What if you could build your own team of AI agents—each with a role, a purpose, and the ability to execute tasks 24/7? With Agent Forge, you can: 🔹 Set Goals 🔹 Assign Roles 🔹 Deploy in Minutes 🔹 Use Real-Time Data 🔹 Chain Agents Together 👉 Get started:

AITECH

65,649 views • 1 year ago

$1.5M is up for grabs in the Great Tournament of Agents! Build and deploy a trading agent using Cod3x Create today for your chance to win. Don't know how to build an agent? Join our FREE BootCamp @
0:14

$1.5M is up for grabs in the Great Tournament of Agents! Build and deploy a trading agent using Cod3x Create today for your chance to win. Don't know how to build an agent? Join our FREE BootCamp @

Cod3x | Win More Trades

656,466 views • 1 year ago

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:
0:16

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 views • 3 months ago

Very pleasantly surprised to discover Cursor cloud agents can playtest the godot game I built. See the (sped up) video below of the agent playtesting the game. As I was watching it play the game, I can see the agent slowly learn how the game works and familiarise with the game's UI. I also realised that the agent is a very 'safe' player, choosing to play very safely and retreating from battle if it foresees it can't defeat. Very interesting to see. I wonder if I could simulate different game playtester behaviours that mimic different types of real-world player archetypes. With agentic playtesting, this means that the agents are able to provide actual gameplay feedback and suggestions to improve the game, having played the game itself. This unlocks a whole lot of possibilities for AI-assisted game dev, since it closes the playtest loop. This feels like the future of recursive game development, where agents can now recursively build > playtest > improve the games they are working on. Thanks edwin for letting me know that these agents can actually playtest games, not just software! Very excited to dig deeper to see what I can do with these agents with computer access!
0:17

Very pleasantly surprised to discover Cursor cloud agents can playtest the godot game I built. See the (sped up) video below of the agent playtesting the game. As I was watching it play the game, I can see the agent slowly learn how the game works and familiarise with the game's UI. I also realised that the agent is a very 'safe' player, choosing to play very safely and retreating from battle if it foresees it can't defeat. Very interesting to see. I wonder if I could simulate different game playtester behaviours that mimic different types of real-world player archetypes. With agentic playtesting, this means that the agents are able to provide actual gameplay feedback and suggestions to improve the game, having played the game itself. This unlocks a whole lot of possibilities for AI-assisted game dev, since it closes the playtest loop. This feels like the future of recursive game development, where agents can now recursively build > playtest > improve the games they are working on. Thanks edwin for letting me know that these agents can actually playtest games, not just software! Very excited to dig deeper to see what I can do with these agents with computer access!

Danny Limanseta

52,121 views • 5 months ago

Excited to launch a new way to upskill with AI agents. This is how we are making it possible for anyone to learn to build with coding agents. To start, we are launching 4 new hands-on labs on the following topics: - Agent Skills - Agentic Image Generation - 30 Days of Hermes Agents - Prompt Engineering with Agents I am confident that with our new DAIR.AI platform, anyone can learn to become a top AI builder by building and acquiring highly-demanded AI skills. And there is a lot more landing in the coming weeks.
0:14

Excited to launch a new way to upskill with AI agents. This is how we are making it possible for anyone to learn to build with coding agents. To start, we are launching 4 new hands-on labs on the following topics: - Agent Skills - Agentic Image Generation - 30 Days of Hermes Agents - Prompt Engineering with Agents I am confident that with our new DAIR.AI platform, anyone can learn to become a top AI builder by building and acquiring highly-demanded AI skills. And there is a lot more landing in the coming weeks.

elvis

19,058 views • 2 months ago

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.
0:14

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

Akshay 🚀

52,426 views • 5 months ago

I agree that agents integrated into team environments is the next paradigm in LLM UIUX but I'd take it a step further and argue that you shouldn't have to even tag your agent. Agents should be smart enough to know when to do work, just like a human.
0:12

I agree that agents integrated into team environments is the next paradigm in LLM UIUX but I'd take it a step further and argue that you shouldn't have to even tag your agent. Agents should be smart enough to know when to do work, just like a human.

nader dabit

56,717 views • 1 month ago

Alright, now that we know *what* an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.
0:15

Alright, now that we know *what* an agent is, how does it actually work? When you ask for help on a task, the agent plans a series of steps and executes them directly in the application on your behalf, using the tools it has access to. Say you are booking a local service or trying to organize your inbox (which typically takes multiple steps): the AI model first plans how to achieve the task using its existing knowledge and then interacts with your inbox to execute the task. The agent will continue until it is confident the task has been successfully completed.

Google AI

22,487 views • 8 months ago

EIP-8004 is coming to the Nova architecture, a trustless infrastructure for AI agents that introduces key on-chain registries, enabling agents to interact safely across the Shido Network. These core components allow autonomous AI agents to verify identity, build reputation, and collaborate without relying on a centralized platform. The result is a decentralized trust layer for agent-to-agent economies, where agents can autonomously discover, evaluate, and work with one another across the Shido ecosystem.
0:20

EIP-8004 is coming to the Nova architecture, a trustless infrastructure for AI agents that introduces key on-chain registries, enabling agents to interact safely across the Shido Network. These core components allow autonomous AI agents to verify identity, build reputation, and collaborate without relying on a centralized platform. The result is a decentralized trust layer for agent-to-agent economies, where agents can autonomously discover, evaluate, and work with one another across the Shido ecosystem.

Shido

390,734 views • 5 months ago

The hard part of multi-agent systems is getting agents to stay quiet. Put five agents on one task, and they duplicate work and burn tokens talking to each other. Offloop trained a dispatcher model called D1 that decides which agent moves next and when the right move is to do nothing. They achieve state-of-the-art performance on GDPval at a fraction of the usual cost. You can bring your own AI subscription.
0:12

The hard part of multi-agent systems is getting agents to stay quiet. Put five agents on one task, and they duplicate work and burn tokens talking to each other. Offloop trained a dispatcher model called D1 that decides which agent moves next and when the right move is to do nothing. They achieve state-of-the-art performance on GDPval at a fraction of the usual cost. You can bring your own AI subscription.

elvis

22,116 views • 21 days ago

2 Cursor Composer agents working together on the same project. one builds the project, the other reviews once the first agent is done and writes a report. cursor rules file is in comment to achieve this. first agent is instructed to build the project second agent is instructed to write a monitoring script to determine when the project is done then to review the project for errors and write a report This prompt can be improved. This is meant as a baseline If you are interested in learning how to use Cursor more in depth, I have a 28 chapter 1000x Cursor Course building full apps from scratch with 19 hours of content. link is in my bio if you are interested
0:19

2 Cursor Composer agents working together on the same project. one builds the project, the other reviews once the first agent is done and writes a report. cursor rules file is in comment to achieve this. first agent is instructed to build the project second agent is instructed to write a monitoring script to determine when the project is done then to review the project for errors and write a report This prompt can be improved. This is meant as a baseline If you are interested in learning how to use Cursor more in depth, I have a 28 chapter 1000x Cursor Course building full apps from scratch with 19 hours of content. link is in my bio if you are interested

echo.hive

149,034 views • 1 year ago

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.
0:15

Increasingly, HTML Artifacts are becoming a core part of how I work with AI agents. Long-horizon agent sessions need a better way to surface insights about what work it has done. This may not be obvious right now, but as you start to let your agent work on dynamic workflows, large codebases, long-running loops (e.g., using /goal), and deep research tasks, you need a good way to present results. Chat window is not it. You also don't want to just trust everything the agents do. Artifacts help provide an important verification layer, which in turn enables important decision-making. I like HTML artifacts because I can just ask the agent to produce as many of them (and in whatever form) as I need to verify the work and make sense out of everything. I even built a nice tab system for my artifacts. They are great for continual learning and research. I use HTML artifacts for logging, tracking experiments, brainstorming, managing my inbox, code reviews, agent session management, deep research, writing, reading, and so much more. I believe Andrej Karpathy wrote about this somewhere: As we move on to more advanced applications of AI agents and outputs get more complex, we will start to find the need for even more advanced forms of interactions with AI, including interactive neural videos/simulations.

elvis

36,881 views • 2 months ago

LayerAI AI Agent Manifesto is Live: The Path Forward 🧬 We've made it easy for ecosystem veterans & newcomers to get excited about the market & product opportunity we're tackling next: AI Agent Infrastructure. We're building an AI-powered agent platform where people can deploy, market, and succeed with this new token subcategory. At the heart of this transformation lies a challenge: primitive & so far limited tech & AI capabilities of incumbent platforms. We believe that LayerAI is equipped to rise as the new leading infrastructure provider for this market. LayerAI has already demonstrated market validation for AI Agents and looks to build on what we believe is the very start of this category in web3. 👉 Explore now:
0:19

LayerAI AI Agent Manifesto is Live: The Path Forward 🧬 We've made it easy for ecosystem veterans & newcomers to get excited about the market & product opportunity we're tackling next: AI Agent Infrastructure. We're building an AI-powered agent platform where people can deploy, market, and succeed with this new token subcategory. At the heart of this transformation lies a challenge: primitive & so far limited tech & AI capabilities of incumbent platforms. We believe that LayerAI is equipped to rise as the new leading infrastructure provider for this market. LayerAI has already demonstrated market validation for AI Agents and looks to build on what we believe is the very start of this category in web3. 👉 Explore now:

LayerAI | AI2Earn

158,919 views • 1 year ago

Stop spending hours on manual work. You can now use a multi-agent AI workforce to get more work done in less time. Here's how 👇 --- Try Eigent AI - Lets you build and run a custom AI workforce on your desktop. - Automate complex workflows using multi-agent task execution. - Built on CAMEL-AI’s top open-source projects ( CAMEL-AI.org & OWL). - Boost productivity with deep customization and strong privacy --- Features: - Customize Your AI Workforce: Build task-specific agents with domain skills and tools. - Faster Execution: Eigent runs agents in parallel to automate complex workflows. - Human-in-the-loop: Automatically asks for help when tasks hit uncertainty. --- What sets Eigent apart? - 3–5× faster task execution using a parallel multi-agent workforce. - Modular design lets you add new capabilities without changing the core system. - Self-optimizing agents that replan and adapt during execution for higher success. - Deploy anywhere: cloud, local, or enterprise, with full open-source flexibility. --- Try building your multi-agent AI workforce here: Join their community to build your multi-agent workforce: Check their GitHub: ---
0:13

Stop spending hours on manual work. You can now use a multi-agent AI workforce to get more work done in less time. Here's how 👇 --- Try Eigent AI - Lets you build and run a custom AI workforce on your desktop. - Automate complex workflows using multi-agent task execution. - Built on CAMEL-AI’s top open-source projects ( CAMEL-AI.org & OWL). - Boost productivity with deep customization and strong privacy --- Features: - Customize Your AI Workforce: Build task-specific agents with domain skills and tools. - Faster Execution: Eigent runs agents in parallel to automate complex workflows. - Human-in-the-loop: Automatically asks for help when tasks hit uncertainty. --- What sets Eigent apart? - 3–5× faster task execution using a parallel multi-agent workforce. - Modular design lets you add new capabilities without changing the core system. - Self-optimizing agents that replan and adapt during execution for higher success. - Deploy anywhere: cloud, local, or enterprise, with full open-source flexibility. --- Try building your multi-agent AI workforce here: Join their community to build your multi-agent workforce: Check their GitHub: ---

Shushant Lakhyani

20,423 views • 1 year ago