Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Those building AI coding agents will eventually hit the same wall: No matter how smart the model is, the moment you ask it to write production-ready code with the latest libraries, it starts hallucinating. Everyone is building coding agents these days, but most of them run into the same... show more

Jafar Najafov

61,421 subscribers

19,873 views • 2 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Most AI coding agents can write code. But what happens when you give one agent an entire project and tell it to figure everything out? I put EvoX Agent to the test. Here’s what happened ↓

Most AI coding agents can write code. But what happens when you give one agent an entire project and tell it to figure everything out? I put EvoX Agent to the test. Here’s what happened ↓

GrowAIHub

55,857 views • 1 month ago

Meet Muse Spark 1.2 and Muse Code, the agent built to run it against your coding challenges. Now in beta. Together they take a task from idea to production, and deploy teams of agents that plan, write and refine across your repos. Start building now:

Meet Muse Spark 1.2 and Muse Code, the agent built to run it against your coding challenges. Now in beta. Together they take a task from idea to production, and deploy teams of agents that plan, write and refine across your repos. Start building now:

Meta for Developers

155,499 views • 2 months ago

AI coding isn't just “building apps faster.” Sometimes it feels closer to drawing with logic. Everyone has their own timeline. Everyone has their own shape. You write a prompt, adjust the motion, bend the layout, and slowly the thing starts to breathe. I don't think this is beneath AIGC. If image generation is painting with pixels, AI coding is painting with behavior. Which one feels more like art to you?

AI coding isn't just “building apps faster.” Sometimes it feels closer to drawing with logic. Everyone has their own timeline. Everyone has their own shape. You write a prompt, adjust the motion, bend the layout, and slowly the thing starts to breathe. I don't think this is beneath AIGC. If image generation is painting with pixels, AI coding is painting with behavior. Which one feels more like art to you?

Verdent

307,761 views • 4 months ago

AI coding agents are moving past “write me code.” They can now build, review, and improve the same project. So we connected Claude Code to Step 3.7 flash and gave it a real task.

AI coding agents are moving past “write me code.” They can now build, review, and improve the same project. So we connected Claude Code to Step 3.7 flash and gave it a real task.

Future Stacked

231,171 views • 3 months ago

Issue 4 of Interfaces just released! This issue is about building an animated sign-in dialog. It covers everything that goes into building it, from the animations to the small but important details. It's one of the most in-depth issues yet, full of code snippets and demos.

Issue 4 of Interfaces just released! This issue is about building an animated sign-in dialog. It covers everything that goes into building it, from the animations to the small but important details. It's one of the most in-depth issues yet, full of code snippets and demos.

Jakub Krehel

37,748 views • 4 months ago

NO WAY. Someone is basically building a MANAGER for your AI agents. You give it one objective. It briefs Claude, Codex + the agents you choose, keeps them on the same context and coordinates the work. This is Jarvix. And I had to dig into this: 🧵 #JarvixOS

NO WAY. Someone is basically building a MANAGER for your AI agents. You give it one objective. It briefs Claude, Codex + the agents you choose, keeps them on the same context and coordinates the work. This is Jarvix. And I had to dig into this: 🧵 #JarvixOS

EyeingAI

37,574 views • 1 month ago

AI agents are quickly becoming one of crypto’s biggest narratives in 2026 🤖 Coinbase calls it the future. Jensen Huang says they will “change everything.” At Bluwhale, you can already create your own AI agent with Bluprint ⚔️ No coding required. Start building 👇 👇 Source

AI agents are quickly becoming one of crypto’s biggest narratives in 2026 🤖 Coinbase calls it the future. Jensen Huang says they will “change everything.” At Bluwhale, you can already create your own AI agent with Bluprint ⚔️ No coding required. Start building 👇 👇 Source

Bluwhale

20,269 views • 5 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 →

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 • 1 year 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.

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 • 4 months ago

Building AI agents is finally simple — and Airia is leading the way. I’ve been testing Airia AI , enterprise AI orchestration platform that unifies every model, workflow, and data source into one secure environment. Whether you’re a developer, analyst, creator, or enterprise leader, Airia makes it incredibly easy to build powerful AI agents — without wrestling with multiple tools or complex integrations. Using the no-code builder, you can drag-and-drop actions, connect data, choose your LLM, and launch an agent in minutes. Then run it live, publish it, and even share it with the Airia Community, home to 2,500+ pre-built agents you can use or remix. If you want to automate workflows, prototype faster, or explore real enterprise AI use cases, Airia is the place to start. 👉 Build your first agent today: 👉 Explore the community: #Airia #AgenticAI #AIOrchestration #AIAgents #AIWorkflow #DigitalTransformation

Building AI agents is finally simple — and Airia is leading the way. I’ve been testing Airia AI , enterprise AI orchestration platform that unifies every model, workflow, and data source into one secure environment. Whether you’re a developer, analyst, creator, or enterprise leader, Airia makes it incredibly easy to build powerful AI agents — without wrestling with multiple tools or complex integrations. Using the no-code builder, you can drag-and-drop actions, connect data, choose your LLM, and launch an agent in minutes. Then run it live, publish it, and even share it with the Airia Community, home to 2,500+ pre-built agents you can use or remix. If you want to automate workflows, prototype faster, or explore real enterprise AI use cases, Airia is the place to start. 👉 Build your first agent today: 👉 Explore the community: #Airia #AgenticAI #AIOrchestration #AIAgents #AIWorkflow #DigitalTransformation

Adarsh Chetan

269,556 views • 10 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.

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

31,074 views • 10 months ago

Seems like Visual Studio Code is starting to tell you: your agent primitives need to move. There is now a new migration banner in the Chat panel, and it is part of a much bigger change happening under the hood: the move from the old Local harness to the new Agent Host architecture built around AHP. This is not just about moving where an agent runs. The old model was very VS Code-centric: prompts, custom agents, instructions and skills could live in VS Code-specific locations and the agent runtime lived inside the extension host. The new Agent Host separates the agent runtime from the editor. Sessions can keep running when the window closes, be shared across VS Code windows, run remotely, and support different harnesses such as Copilot, CLI and Copilot Desktop App through a common session layer. And that means some of our primitives need to move too. Prompt files are being deprecated for Agent Host and migrated to Skills. User-level agents and instructions that lived in VS Code profile storage need to move to harness-supported locations. Even the old location settings are being deprecated. The new migration experience can detect these things and guide you through moving or converting them, while keeping the originals unless you explicitly remove them. The new banner is basically the first visible sign that this migration is becoming a real product workflow. Basically telling us - it's time to move on!!!! If you have accumulated a lot of prompts, custom agents, instructions and skills over the last year, now is probably a good time to understand where they actually live and which harness owns them. To summarize the shift - it isn't just: VS Code Chat → Agent Host It is: VS Code-specific primitives → harness-native primitives. And I think this is going to become increasingly important as agents stop being features inside an IDE and become runtimes that multiple clients can connect to. Go run your migrations now 🏃‍♀️

Oren Melamed

29,753 views • 7 days ago

Agents are the future of AI creative tools. And the new Grok Imagine Agent is a great one! It feels like a smart partner that you can brainstorm and iterate with - it does the heavy lifting of writing prompts + building out the canvas. Watch me build a froyo brand 👇

Justine Moore

31,430 views • 5 months ago

It's true, most AI coding tools make you do the grunt testing and debugging work. That's why we invested in researching and building a state-of-the-art app testing tool. Replit Agent 3 will spin up a browser and test your app end-to-end.

It's true, most AI coding tools make you do the grunt testing and debugging work. That's why we invested in researching and building a state-of-the-art app testing tool. Replit Agent 3 will spin up a browser and test your app end-to-end.

Amjad Masad

110,113 views • 10 months ago

whoever leaked this is f*cking crazy someone mapped 300+ AI agents into one GitHub repo - and basically leaked the shortlist of what’s actually worth trying. coding agents. browser agents. memory. voice. research. multi-agent teams. local models. sandboxes. evals. all sitting on one page. and once you start opening the categories, you realize how much stuff people are still building from scratch for absolutely no reason. want an AI that works inside your codebase? -> Aider / Continue want agents working together like a tiny company? -> CrewAI / AutoGen / MetaGPT want your agent to actually remember you tomorrow? -> Mem0 want it running code somewhere that isn’t your laptop? -> E2B want models running locally for $0/token? -> Ollama want to see what your agent actually did after it inevitably does something weird? -> AgentOps and that’s barely scratching it. there are 300+ projects across ~25 categories. the real cheat code isn’t downloading all of them. it’s opening the repo before you build anything and asking: “has someone already solved this?” because there’s a pretty good chance the answer is yes - and the open-source version already has thousands of people testing it for you. I went through the map and pulled out the agents I’d actually start with + my pick for every major part of the stack. full 300+ AI agent list below

whoever leaked this is f*cking crazy someone mapped 300+ AI agents into one GitHub repo - and basically leaked the shortlist of what’s actually worth trying. coding agents. browser agents. memory. voice. research. multi-agent teams. local models. sandboxes. evals. all sitting on one page. and once you start opening the categories, you realize how much stuff people are still building from scratch for absolutely no reason. want an AI that works inside your codebase? -> Aider / Continue want agents working together like a tiny company? -> CrewAI / AutoGen / MetaGPT want your agent to actually remember you tomorrow? -> Mem0 want it running code somewhere that isn’t your laptop? -> E2B want models running locally for $0/token? -> Ollama want to see what your agent actually did after it inevitably does something weird? -> AgentOps and that’s barely scratching it. there are 300+ projects across ~25 categories. the real cheat code isn’t downloading all of them. it’s opening the repo before you build anything and asking: “has someone already solved this?” because there’s a pretty good chance the answer is yes - and the open-source version already has thousands of people testing it for you. I went through the map and pulled out the agents I’d actually start with + my pick for every major part of the stack. full 300+ AI agent list below

kiosa

100,730 views • 3 days ago

‼️found a site that ends AI design slop. superrr is an MCP server that gives your coding agent taste. they measured 132 real landing pages, verified 123 of them and pulled out 17 design directions with exact tokens. the agents still writes the code. superrr picks the direction, hands it the structure then grades what it built by scanning the live page after. no more generic purple gradient landing pages. their landing page was one-shotted with it. three lines to connect to Claude. link:

‼️found a site that ends AI design slop. superrr is an MCP server that gives your coding agent taste. they measured 132 real landing pages, verified 123 of them and pulled out 17 design directions with exact tokens. the agents still writes the code. superrr picks the direction, hands it the structure then grades what it built by scanning the live page after. no more generic purple gradient landing pages. their landing page was one-shotted with it. three lines to connect to Claude. link:

sui

25,411 views • 1 month ago

Today, AI can generate tons of code—but how do we know if it's good? That's why we built Sculptor: the first coding agent environment. Sculptor helps you catch issues, write tests, and improve your code—all while you work in your favorite editor.

Today, AI can generate tons of code—but how do we know if it's good? That's why we built Sculptor: the first coding agent environment. Sculptor helps you catch issues, write tests, and improve your code—all while you work in your favorite editor.

Kanjun 🐙

137,491 views • 1 year ago

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

New open-source agent harness just landed! I got early access to TrueForge by TrueFoundry and have been running it locally for the past few days. The harness layer deserves as much attention as the model, and open source matters here because you can inspect the loop, run it on your own infrastructure, and swap to the latest or cheaper models. TrueForge handles the runtime work that makes an agent reliable. It drives the tool-calling loop, manages context, coordinates subagents, and executes code in a sandbox, with any model you choose. Every tool call re-sends the growing context to the model, so in practice the harness controls most of what an agent costs to run. A few things stood out from my testing and their published benchmarks. Vendor-Neutral by design. It runs OpenAI, Anthropic, and Google models alongside open-weight models like Kimi, GLM, and DeepSeek. Model routing is a setting, and you can send each task to the model that fits it. On a 14-task enterprise agent benchmark, it matched the accuracy of Claude Managed Agents running the same Opus 4.8 model at roughly 30% lower cost per run (3.8M tokens vs 10M for the same answers). Routing the same tasks to GLM-5.2 held accuracy and brought cost down by about 75%, around $3 per run instead of $12. Fully self-hosted and Open Source (MIT License). I had it running locally with one command, with sandboxed code execution working out of the box. It's time to own your agent harness. Thanks to TrueFoundry for partnering on this post.

elvis

11,303 views • 1 month ago