Loading video...

Video Failed to Load

Go Home

How to setup a multi agent system? Bookmark it 📂 "The Trading Floor" Multi-Agent Market Analysis Council to analyze a stock ticker Z.ai GLM-4.7 🤝 OpenCode Agent framework: CrewAI How it works? 1. User enters a stock ticker to analyze 2. 5 AI agents wake up, each with distinct...

cloudxdev's profile picture

CloudAI-X

4,095 subscribers

58,189 views • 8 months 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

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:
2:49

New Course: ACP: Agent Communication Protocol Learn to build agents that communicate and collaborate across different frameworks using ACP in this short course built with IBM Research's BeeAI, and taught by Sandi Besen, AI Research Engineer & Ecosystem Lead at IBM, and Nicholas Renotte, Head of AI Developer Advocacy at IBM. Building a multi-agent system with agents built or used by different teams and organizations can become challenging. You may need to write custom integrations each time a team updates their agent design or changes their choice of agentic orchestration framework. The Agent Communication Protocol (ACP) is an open protocol that addresses this challenge by standardizing how agents communicate, using a unified RESTful interface that works across frameworks. In this protocol, you host an agent inside an ACP server, which handles requests from an ACP client and passes them to the appropriate agent. Using a standardized client-server interface allows multiple teams to reuse agents across projects. It also makes it easier to switch between frameworks, replace an agent with a new version, or update a multi-agent system without refactoring the entire system. In this course, you’ll learn to connect agents through ACP. You’ll understand the lifecycle of an ACP Agent and how it compares to other protocols, such as MCP (Model Context Protocol) and A2A (Agent-to-Agent). You’ll build ACP-compliant agents and implement both sequential and hierarchical workflows of multiple agents collaborating using ACP. Through hands-on exercises, you’ll build: - A RAG agent with CrewAI and wrap it inside an ACP server. - An ACP Client to make calls to the ACP server you created. - A sequential workflow that chains an ACP server, created with Smolagents, to the RAG agent. - A hierarchical workflow using a router agent that transforms user queries into tasks, delegated to agents available through ACP servers. - An agent that uses MCP to access tools and ACP to communicate with other agents. You’ll finish up by importing your ACP agents into the BeeAI platform, an open-source registry for discovering and sharing agents. ACP enables collaboration between agents across teams and organizations. By the end of this course, you’ll be able to build ACP agents and workflows that communicate and collaborate regardless of framework. Please sign up here:

Andrew Ng

105,343 views • 1 year ago

10 GitHub repos with ⭐ 1.2M+ combined stars that help you build your AI agent from scratch 1. n8n 201k⭐ - visual agent builder with 400+ integrations. Wire up multi-step AI workflows without writing a backend. 2. Hermes Agent 231k⭐ - the fastest-growing open-source agent framework of 2026. Self-improving skill loop, persistent memory across sessions. 3. Dify 152k⭐ - visual builder for agentic workflows and RAG pipelines, production-ready out of the box. 4. LangChain 144k⭐ - the standard framework for LLM apps. Chains, agents, retrieval, all in one place. 5. MetaGPT 70k⭐ - simulates an entire software company. PM, architect, engineer agents that build your app together. 6. AutoGen 60k⭐ - Microsoft's framework for multi-agent conversations and coordination. 7. OpenCode 198k⭐ - terminal coding agent, provider-agnostic across 75+ models. The go-to harness for agentic coding in 2026. 8. LlamaIndex 52k⭐ - connects your agents to your actual data. Indexing and retrieval done right. 9. CrewAI 57k⭐ - role-based crews of agents. Reads almost like plain English, no graph to learn. 10. LangGraph 40k⭐ - graph-based orchestration when you need precise control over agent state in production. Save this before you pay for another agent-building course 👇
1:08

10 GitHub repos with ⭐ 1.2M+ combined stars that help you build your AI agent from scratch 1. n8n 201k⭐ - visual agent builder with 400+ integrations. Wire up multi-step AI workflows without writing a backend. 2. Hermes Agent 231k⭐ - the fastest-growing open-source agent framework of 2026. Self-improving skill loop, persistent memory across sessions. 3. Dify 152k⭐ - visual builder for agentic workflows and RAG pipelines, production-ready out of the box. 4. LangChain 144k⭐ - the standard framework for LLM apps. Chains, agents, retrieval, all in one place. 5. MetaGPT 70k⭐ - simulates an entire software company. PM, architect, engineer agents that build your app together. 6. AutoGen 60k⭐ - Microsoft's framework for multi-agent conversations and coordination. 7. OpenCode 198k⭐ - terminal coding agent, provider-agnostic across 75+ models. The go-to harness for agentic coding in 2026. 8. LlamaIndex 52k⭐ - connects your agents to your actual data. Indexing and retrieval done right. 9. CrewAI 57k⭐ - role-based crews of agents. Reads almost like plain English, no graph to learn. 10. LangGraph 40k⭐ - graph-based orchestration when you need precise control over agent state in production. Save this before you pay for another agent-building course 👇

unicode

30,511 views • 1 month ago

ElizaOS Ecosystem Map -- Version #3 🤖 AI Agent Framework (Core) 1) ElizaOS -- elizaOS 🧠 - Open source AI Agent framework - Cross-chain compatible (Solana, Base, EVM) - Supports plugins for social media, blockchains, and APIs 🏗️ Infrastructure 2) ElizaCloud ☁️ - Cloud hosting platform for AI agents - One-click agent deployments with scalability - Secure environments using TEEs 3) Jeju ⛓️ - Purpose-built L2 App Chain for Agents - High-performance blocks for sub-second agent coordination - The backbone of the decentralized Agent Network 4) Otaku -- @otakuonbase 👛 - DeFi wallet designed for AI agents - Supports agent-controlled crypto transactions (swap, send, hold) - Secure, non-custodial infrastructure for on-chain actions 🎮 Apps/Games 5) Spartan -- Spartan 🛡️ - ElizaOS's flagship agent showing what’s possible - Autonomous trading based on crypto knowledge - Trained on influencer data for market insights 6) Babylon -- Babylon -- The City of Agents 🐵 - Social prediction market game for agents - Agents compete alongside humans to forecast on-chain events - Includes perps and other gamified mechanics 7) Hyperscape -- Gold ⚔️ - First AI MMO Game powered by ElizaOS - A vast gaming world built for humans and agents to coexist - Agents drive the in-game economy and narrative 8) Milady App -- Milady on BSC 😎 - Open-source, local-first AI companion app powered by ElizaOS - Let's anyone quickly create and deploy their own agents - Built-in wallet, natively integrated with BNB chain 9) OTC Trading Desk 📊 - Multi-chain AI-powered OTC desk for crypto trades - Lists tokens off-market with transparent lockup and discount terms - Use Eliza agents to negotiate terms on your behalf
1:08

ElizaOS Ecosystem Map -- Version #3 🤖 AI Agent Framework (Core) 1) ElizaOS -- elizaOS 🧠 - Open source AI Agent framework - Cross-chain compatible (Solana, Base, EVM) - Supports plugins for social media, blockchains, and APIs 🏗️ Infrastructure 2) ElizaCloud ☁️ - Cloud hosting platform for AI agents - One-click agent deployments with scalability - Secure environments using TEEs 3) Jeju ⛓️ - Purpose-built L2 App Chain for Agents - High-performance blocks for sub-second agent coordination - The backbone of the decentralized Agent Network 4) Otaku -- @otakuonbase 👛 - DeFi wallet designed for AI agents - Supports agent-controlled crypto transactions (swap, send, hold) - Secure, non-custodial infrastructure for on-chain actions 🎮 Apps/Games 5) Spartan -- Spartan 🛡️ - ElizaOS's flagship agent showing what’s possible - Autonomous trading based on crypto knowledge - Trained on influencer data for market insights 6) Babylon -- Babylon -- The City of Agents 🐵 - Social prediction market game for agents - Agents compete alongside humans to forecast on-chain events - Includes perps and other gamified mechanics 7) Hyperscape -- Gold ⚔️ - First AI MMO Game powered by ElizaOS - A vast gaming world built for humans and agents to coexist - Agents drive the in-game economy and narrative 8) Milady App -- Milady on BSC 😎 - Open-source, local-first AI companion app powered by ElizaOS - Let's anyone quickly create and deploy their own agents - Built-in wallet, natively integrated with BNB chain 9) OTC Trading Desk 📊 - Multi-chain AI-powered OTC desk for crypto trades - Lists tokens off-market with transparent lockup and discount terms - Use Eliza agents to negotiate terms on your behalf

Seppmos

25,942 views • 6 months ago

What defines the "Best Chain for AI Agents"? > Infra that keeps up with the Chain. > Integrated Stack for Smooth Integrations. > MultiVM & Native Automation enabling true "On-Chain Super Agents" In this Demo Series, we’ll build AI Agents using Supra Integrated L1 to create powerful AI Agents that redefine the experience, alongside using powerful tools such as OpenBlocks and more... For the Starting, Let’s build an AI Agent that: ✅ Fetch real-time & historical market data from SupraOracles. ✅Compute technical indicators for informed decision-making. ✅Forecast short-term price trends using Facebook's ML Model. ✅Handle follow-up questions to analyze Marketing for a trading pair through OpenAI GPT. Buckle up, time to build Super Agents on Supra! 🤖💪🏻
37:39

What defines the "Best Chain for AI Agents"? > Infra that keeps up with the Chain. > Integrated Stack for Smooth Integrations. > MultiVM & Native Automation enabling true "On-Chain Super Agents" In this Demo Series, we’ll build AI Agents using Supra Integrated L1 to create powerful AI Agents that redefine the experience, alongside using powerful tools such as OpenBlocks and more... For the Starting, Let’s build an AI Agent that: ✅ Fetch real-time & historical market data from SupraOracles. ✅Compute technical indicators for informed decision-making. ✅Forecast short-term price trends using Facebook's ML Model. ✅Handle follow-up questions to analyze Marketing for a trading pair through OpenAI GPT. Buckle up, time to build Super Agents on Supra! 🤖💪🏻

Jatin Pandya

13,685 views • 1 year ago

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.
30:12

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

229,143 views • 4 months ago

Guys check out this latest tech token that just have today and is definitely flying under the radar! 🚀 Agent Alpha has been building in stealth mode for the past year. Their platform lets users deploy AI agents that gather trading alpha continuously, from Telegram, Dexscreener, X, wallet trackers, anything with visual input. Their agents analyze the data in real-time to give traders buy and sell recommendations based off the parameters the user inputs. 🔥 Agent Alpha is launching in the next week for DEX, with Telegram and X set to follow quickly behind. They have several high profile partnerships with other agentic projects in the coming weeks, where these projects will be using Agent Alpha to gather real-time data. They are the first product to launch using the framework created by LiftDataAI. 💎 Also coming soon is Agent Alpha's own extensible framework, which will enable advanced users to add new data sources to the platform and integrate their own tools for technical analysis. Advanced users will be able to deploy agents privately, or tokenize them and release them publicly. ⭐️ Agent Alpha will only be available to holders of the $AA ticker. ⚡️ 📈DexScreener - 🕊Twitter - 🌐website -
0:46

Guys check out this latest tech token that just have today and is definitely flying under the radar! 🚀 Agent Alpha has been building in stealth mode for the past year. Their platform lets users deploy AI agents that gather trading alpha continuously, from Telegram, Dexscreener, X, wallet trackers, anything with visual input. Their agents analyze the data in real-time to give traders buy and sell recommendations based off the parameters the user inputs. 🔥 Agent Alpha is launching in the next week for DEX, with Telegram and X set to follow quickly behind. They have several high profile partnerships with other agentic projects in the coming weeks, where these projects will be using Agent Alpha to gather real-time data. They are the first product to launch using the framework created by LiftDataAI. 💎 Also coming soon is Agent Alpha's own extensible framework, which will enable advanced users to add new data sources to the platform and integrate their own tools for technical analysis. Advanced users will be able to deploy agents privately, or tokenize them and release them publicly. ⭐️ Agent Alpha will only be available to holders of the $AA ticker. ⚡️ 📈DexScreener - 🕊Twitter - 🌐website -

Pumpcoinbets - Crypto & NFT

75,322 views • 1 year ago

HERMES AGENT SUPPORTS 7 TYPES OF AI AGENTS. EACH ONE TAKES LESS THAN 90 SECONDS TO SET UP. MOST PEOPLE ONLY BUILD THE FIRST ONE. HERE ARE ALL SEVEN AND WHEN TO USE EACH. 1. BASIC AGENT WITH TOOLS your agent with access to terminal, browser, file system, web search, and calendar. it plans and executes tasks on its own. this is what you get on day one. "find flights to Lisbon under $400" "check my calendar and flag conflicts" "search the web for competitor pricing" set in Desktop app / Dashboard: Tools → enable what you need. when to use: single tasks that need tool access. 2. AGENT WITH MCP SERVERS connect your agent to external services. Notion, Google Drive, GitHub, Slack, databases, APIs, any MCP-compatible service. the agent doesn't scrape these services. it interacts through structured APIs. reads your Notion pages. creates GitHub issues. queries your database. sends Slack messages. set in Desktop app / Dashboard: MCP → Add Server. when to use: your workflow lives across multiple platforms. 3. SEQUENTIAL AGENTS (pipeline) one agent finishes. passes output to the next. assembly line for AI. agent 1: scans inbox for leads. agent 2: qualifies leads against criteria. agent 3: drafts outreach emails. in Hermes: cron jobs with wakeAgent gates. agent 1 writes output to a file. agent 2 wakes only when that file has new data. agent 3 wakes when agent 2 is done. each agent = a separate profile with its own model. when to use: multi-step workflows where each step depends on the previous one finishing. 4. PARALLEL EXECUTION AGENTS multiple agents working at the same time. results merge when all finish. "research these 5 competitors in parallel" in Hermes: delegate_task with batch mode. up to 3 sub-agents running in parallel by default. each gets its own clean context. only summaries return to the parent. delegation: model: "deepseek/deepseek-v4" children run cheap. parent synthesizes. when to use: independent tasks that don't depend on each other. research, data gathering, analysis. 5. AGENTS WITH ROUTERS conditions that send tasks down different paths based on the input. "if sales email → SDR profile. if support ticket → support profile. if calendar invite → EA profile." in Hermes: Kanban decompose. the decomposer reads profile descriptions and routes each task to the best-fit agent. or: Chief of Staff profile that triages and assigns to other profiles. when to use: incoming work that needs different specialists based on type. 6. HUMAN IN THE LOOP the agent does the work. asks for your approval before executing. "I drafted this email. approve before I send?" "this command will delete 3 files. proceed?" in Hermes: approvals.mode: manual (default). every dangerous action needs your confirmation. 60-second timeout. fails closed. or smart mode: LLM assesses risk. safe actions auto-approved. dangerous ones ask you. uncertain ones escalate. when to use: tasks where a mistake has real consequences. emails, deployments, financial transactions, public posts. 7. DYNAMIC SUB-AGENT SPAWNING your main agent realizes it needs help and spawns specialized sub-agents on the fly. "build this feature" → parent delegates: → sub-agent 1: research the API docs → sub-agent 2: write the code → sub-agent 3: write the tests in Hermes: delegate_task with role: orchestrator. raise max_spawn_depth for nested delegation. delegation: max_spawn_depth: 2 orchestrator_enabled: true depth 2 with concurrency 3 = up to 9 parallel workers. each level multiplies the spend. raise depth only when you need multi-level trees. when to use: complex tasks where the agent discovers what help it needs during execution. THE PROGRESSION: start with 1 (tools) and 6 (approvals). add 2 (MCP) when you need external services. add 4 (parallel) when tasks take too long one at a time. add 3 (sequential) when you build multi-step pipelines. add 5 (routing) when you run multiple profiles. add 7 (dynamic) when single-agent reasoning falls short. seven types. each under 90 seconds to configure. the value compounds as you stack them. comment AGENTS and I'll send you 3 ready-to-build agent setups that combine these types into real workflows.
1:15

HERMES AGENT SUPPORTS 7 TYPES OF AI AGENTS. EACH ONE TAKES LESS THAN 90 SECONDS TO SET UP. MOST PEOPLE ONLY BUILD THE FIRST ONE. HERE ARE ALL SEVEN AND WHEN TO USE EACH. 1. BASIC AGENT WITH TOOLS your agent with access to terminal, browser, file system, web search, and calendar. it plans and executes tasks on its own. this is what you get on day one. "find flights to Lisbon under $400" "check my calendar and flag conflicts" "search the web for competitor pricing" set in Desktop app / Dashboard: Tools → enable what you need. when to use: single tasks that need tool access. 2. AGENT WITH MCP SERVERS connect your agent to external services. Notion, Google Drive, GitHub, Slack, databases, APIs, any MCP-compatible service. the agent doesn't scrape these services. it interacts through structured APIs. reads your Notion pages. creates GitHub issues. queries your database. sends Slack messages. set in Desktop app / Dashboard: MCP → Add Server. when to use: your workflow lives across multiple platforms. 3. SEQUENTIAL AGENTS (pipeline) one agent finishes. passes output to the next. assembly line for AI. agent 1: scans inbox for leads. agent 2: qualifies leads against criteria. agent 3: drafts outreach emails. in Hermes: cron jobs with wakeAgent gates. agent 1 writes output to a file. agent 2 wakes only when that file has new data. agent 3 wakes when agent 2 is done. each agent = a separate profile with its own model. when to use: multi-step workflows where each step depends on the previous one finishing. 4. PARALLEL EXECUTION AGENTS multiple agents working at the same time. results merge when all finish. "research these 5 competitors in parallel" in Hermes: delegate_task with batch mode. up to 3 sub-agents running in parallel by default. each gets its own clean context. only summaries return to the parent. delegation: model: "deepseek/deepseek-v4" children run cheap. parent synthesizes. when to use: independent tasks that don't depend on each other. research, data gathering, analysis. 5. AGENTS WITH ROUTERS conditions that send tasks down different paths based on the input. "if sales email → SDR profile. if support ticket → support profile. if calendar invite → EA profile." in Hermes: Kanban decompose. the decomposer reads profile descriptions and routes each task to the best-fit agent. or: Chief of Staff profile that triages and assigns to other profiles. when to use: incoming work that needs different specialists based on type. 6. HUMAN IN THE LOOP the agent does the work. asks for your approval before executing. "I drafted this email. approve before I send?" "this command will delete 3 files. proceed?" in Hermes: approvals.mode: manual (default). every dangerous action needs your confirmation. 60-second timeout. fails closed. or smart mode: LLM assesses risk. safe actions auto-approved. dangerous ones ask you. uncertain ones escalate. when to use: tasks where a mistake has real consequences. emails, deployments, financial transactions, public posts. 7. DYNAMIC SUB-AGENT SPAWNING your main agent realizes it needs help and spawns specialized sub-agents on the fly. "build this feature" → parent delegates: → sub-agent 1: research the API docs → sub-agent 2: write the code → sub-agent 3: write the tests in Hermes: delegate_task with role: orchestrator. raise max_spawn_depth for nested delegation. delegation: max_spawn_depth: 2 orchestrator_enabled: true depth 2 with concurrency 3 = up to 9 parallel workers. each level multiplies the spend. raise depth only when you need multi-level trees. when to use: complex tasks where the agent discovers what help it needs during execution. THE PROGRESSION: start with 1 (tools) and 6 (approvals). add 2 (MCP) when you need external services. add 4 (parallel) when tasks take too long one at a time. add 3 (sequential) when you build multi-step pipelines. add 5 (routing) when you run multiple profiles. add 7 (dynamic) when single-agent reasoning falls short. seven types. each under 90 seconds to configure. the value compounds as you stack them. comment AGENTS and I'll send you 3 ready-to-build agent setups that combine these types into real workflows.

YanXbt

17,312 views • 2 months ago

Man Group, the world's largest publicly listed hedge fund, $150B+ AUM, 40+ years of systematic trading, just revealed exactly how they're using AI agents to build trading strategies. this is their actual pipeline: agent 1: reads academic papers, analyzes datasets, reasons about whether there's an economic hypothesis worth testing. agent 2: writes the code to build the signal. agent 3: pulls the market data and runs the backtests. agent 4: evaluates the output of the prior agents. "there've been 15 to 20 models at last count that started as ideas generated by AI, went all the way through signal construction, the validation process, were reviewed and validated by a human investment committee, and deemed fit and proper to manage client assets." "this is very real. it's not make-believe at this point." a $150B hedge fund running a multi-agent pipeline that goes from reading a paper to trading live capital, with humans only entering the loop at the final approval stage. and they've been doing it for over a year and a half.
2:11

Man Group, the world's largest publicly listed hedge fund, $150B+ AUM, 40+ years of systematic trading, just revealed exactly how they're using AI agents to build trading strategies. this is their actual pipeline: agent 1: reads academic papers, analyzes datasets, reasons about whether there's an economic hypothesis worth testing. agent 2: writes the code to build the signal. agent 3: pulls the market data and runs the backtests. agent 4: evaluates the output of the prior agents. "there've been 15 to 20 models at last count that started as ideas generated by AI, went all the way through signal construction, the validation process, were reviewed and validated by a human investment committee, and deemed fit and proper to manage client assets." "this is very real. it's not make-believe at this point." a $150B hedge fund running a multi-agent pipeline that goes from reading a paper to trading live capital, with humans only entering the loop at the final approval stage. and they've been doing it for over a year and a half.

Goshawk Trades

38,079 views • 2 months ago

New short course: Practical Multi AI Agents and Advanced Use Cases with crewAI. Learn to build and deploy advanced agent-based systems in real applications in this course, created with CrewAI and taught by its founder, João Moura! (Disclosure: I've made a small seed investment in CrewAI.) In this course, you’ll learn how to create advanced agent-based apps that use external tools, do performance testing, can be trained with human feedback, and perform multiple tasks with different large language models. You will build several practical agentic apps that provide real business value, such as an automated project planning system, lead scoring and engagement pipeline, customer support data analysis, and a robust content creation system. In detail, you will learn how to: - Create these multi-agent systems with the building blocks of tasks, agents, and crews, along with the different things that make them work, such as caching, memory, and guardrails. - Integrate your multi-agent application with internal and external systems. - Connect multiple agents in complex setups, including parallel, sequential, and hybrid configurations, and create flows involving multiple agentic applications working together. - Test your agentic workflow and train it using human feedback to optimize its performance for better and more consistent results. - Work with multiple LLMs in your multi-agent system, using the appropriate model sizes and providers to fit each agent’s specific task. - Start a project from scratch in your environment and prepare it for deployment. You’ll also learn from an interview between João and Jacob Wilson, the Commercial GenAI Principal at PwC , in which they discuss deploying agentic workflows in real industry use cases. By the end of this course, you will be equipped to start building custom multi-agentic systems for your work. Please sign up here!
2:52

New short course: Practical Multi AI Agents and Advanced Use Cases with crewAI. Learn to build and deploy advanced agent-based systems in real applications in this course, created with CrewAI and taught by its founder, João Moura! (Disclosure: I've made a small seed investment in CrewAI.) In this course, you’ll learn how to create advanced agent-based apps that use external tools, do performance testing, can be trained with human feedback, and perform multiple tasks with different large language models. You will build several practical agentic apps that provide real business value, such as an automated project planning system, lead scoring and engagement pipeline, customer support data analysis, and a robust content creation system. In detail, you will learn how to: - Create these multi-agent systems with the building blocks of tasks, agents, and crews, along with the different things that make them work, such as caching, memory, and guardrails. - Integrate your multi-agent application with internal and external systems. - Connect multiple agents in complex setups, including parallel, sequential, and hybrid configurations, and create flows involving multiple agentic applications working together. - Test your agentic workflow and train it using human feedback to optimize its performance for better and more consistent results. - Work with multiple LLMs in your multi-agent system, using the appropriate model sizes and providers to fit each agent’s specific task. - Start a project from scratch in your environment and prepare it for deployment. You’ll also learn from an interview between João and Jacob Wilson, the Commercial GenAI Principal at PwC , in which they discuss deploying agentic workflows in real industry use cases. By the end of this course, you will be equipped to start building custom multi-agentic systems for your work. Please sign up here!

Andrew Ng

341,204 views • 1 year ago

Introducing LobeHub: Agent teammates that grow with you. LobeHub is the ultimate space for work and life: to find, build, and collaborate with agent teammates that grow with you. We’re building the world’s first and largest human–agent co-evolving network. Two years ago, we built LobeChat, an open-source interface for using different AI models. Today, LobeChat has 70k+ GitHub stars and serves 6M+ users worldwide. How to fully unlock the power of models has always been a shared mission between us and the community. We started with interaction — a fundamentally new, agent-first experience. Agents are no longer passive tools invoked in a single conversation. They should be proactive, always-on units of work. Treating agents as the minimal atomic unit is also the core of our agent harness infra. Today’s agents are mostly one-off executors. Even with memory, it’s often global — and hallucinates. We build long-term agent teammates that evolve with users. Each agent has its own dedicated memory space, editable by users, allowing humans and agents to co-evolve over time. This, in turn, allows us to design clearer rewards for reinforcement learning and create cleaner environments for continual learning. Agent teammates can work in groups. Through a multi-agent system, agent groups operate faster, more cost-effective, and go beyond what single-agent systems can achieve. For example, a single agent often requires heavy user involvement to proceed step by step, whereas LobeHub can execute the same work from a single instruction, with a supervisor orchestrating agents that run in parallel or debate to produce better results. We are building the collaboration network among agent teammates — and between humans and agent teammates as well. Ease of use matters. AI intelligence and shared human intelligence are equally important. With simple instructions and tool selection, you can effortlessly build and team up with agent coworkers to deliver complex, systematic work — even assembling a quant team to execute trades. Through the LobeHub community, anyone can discover, reuse, and remix agents and agent groups, customizing them to fit their own workflows, preferences, and needs. Last but not least, our vision started with LobeChat: multi-model support is the most efficient approach for users. We believe different models excel in different scenarios. By routing across multiple models, LobeHub improves cost efficiency and unlocks capabilities that a single-model setup cannot easily support.
2:41

Introducing LobeHub: Agent teammates that grow with you. LobeHub is the ultimate space for work and life: to find, build, and collaborate with agent teammates that grow with you. We’re building the world’s first and largest human–agent co-evolving network. Two years ago, we built LobeChat, an open-source interface for using different AI models. Today, LobeChat has 70k+ GitHub stars and serves 6M+ users worldwide. How to fully unlock the power of models has always been a shared mission between us and the community. We started with interaction — a fundamentally new, agent-first experience. Agents are no longer passive tools invoked in a single conversation. They should be proactive, always-on units of work. Treating agents as the minimal atomic unit is also the core of our agent harness infra. Today’s agents are mostly one-off executors. Even with memory, it’s often global — and hallucinates. We build long-term agent teammates that evolve with users. Each agent has its own dedicated memory space, editable by users, allowing humans and agents to co-evolve over time. This, in turn, allows us to design clearer rewards for reinforcement learning and create cleaner environments for continual learning. Agent teammates can work in groups. Through a multi-agent system, agent groups operate faster, more cost-effective, and go beyond what single-agent systems can achieve. For example, a single agent often requires heavy user involvement to proceed step by step, whereas LobeHub can execute the same work from a single instruction, with a supervisor orchestrating agents that run in parallel or debate to produce better results. We are building the collaboration network among agent teammates — and between humans and agent teammates as well. Ease of use matters. AI intelligence and shared human intelligence are equally important. With simple instructions and tool selection, you can effortlessly build and team up with agent coworkers to deliver complex, systematic work — even assembling a quant team to execute trades. Through the LobeHub community, anyone can discover, reuse, and remix agents and agent groups, customizing them to fit their own workflows, preferences, and needs. Last but not least, our vision started with LobeChat: multi-model support is the most efficient approach for users. We believe different models excel in different scenarios. By routing across multiple models, LobeHub improves cost efficiency and unlocks capabilities that a single-model setup cannot easily support.

LobeHub

185,401 views • 7 months ago

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.
0:22

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 views • 2 months ago

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 views • 3 months ago

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!
0:20

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!

Loomlay

26,149 views • 1 year ago

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.
0:23

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

460,985 views • 3 months ago

new chapter begins: a terminal for the agentic future, built on blockchain, powered by AI. This is our marketplace—a glimpse of what AGI will mean for crypto. Today, we launch 3 agents—Image Generation, Token Swap Agent, & Blockchain Tax Estimate Agent—out of hundreds to come. We see an agentic future where AI guides every step: buying online, managing finances, transacting globally. FOMO’s here to make that real, with experts at your side. Our Model Context Protocol (MCP) ties it together—agents talking, reasoning, scaling across crypto and DeFi. It’s orchestration with a brain, evolving daily. FOMO’s not just building tools; we’re pushing intelligent automation into blockchain’s core. Our Model Context Protocol (MCP) is the backbone. Think of it as a conductor for AI agents—each runs its own logic (workflows, API calls, LLMs), but MCP syncs them on-chain. Agents share context via a lightweight event bus, logged to a blockchain ledger. Agent A (say, Market Analysis) pulls stock data, flags trends. Agent B (Email Sales) reads that, drafts outreach—both talk through MCP’s orchestration layer. We use Web3 hooks to settle fees or split revenue, all transparent. It’s messy, but it scales. Under the hood: MCP leans on a pub-sub model—agents publish tasks, others subscribe. We’re training them with RL loops to optimize gas costs and response times. Goal? A self-tuning swarm of agents reasoning over DeFi, NFTs, whatever’s next. This is FOMO’s bet on AGI. Welcome to the new FOMO. We’re not just building tools—we’re wiring AI into crypto’s future, agent by agent. A leader in blockchain intelligence, starting here. Join us as we push the boundaries.
1:16

new chapter begins: a terminal for the agentic future, built on blockchain, powered by AI. This is our marketplace—a glimpse of what AGI will mean for crypto. Today, we launch 3 agents—Image Generation, Token Swap Agent, & Blockchain Tax Estimate Agent—out of hundreds to come. We see an agentic future where AI guides every step: buying online, managing finances, transacting globally. FOMO’s here to make that real, with experts at your side. Our Model Context Protocol (MCP) ties it together—agents talking, reasoning, scaling across crypto and DeFi. It’s orchestration with a brain, evolving daily. FOMO’s not just building tools; we’re pushing intelligent automation into blockchain’s core. Our Model Context Protocol (MCP) is the backbone. Think of it as a conductor for AI agents—each runs its own logic (workflows, API calls, LLMs), but MCP syncs them on-chain. Agents share context via a lightweight event bus, logged to a blockchain ledger. Agent A (say, Market Analysis) pulls stock data, flags trends. Agent B (Email Sales) reads that, drafts outreach—both talk through MCP’s orchestration layer. We use Web3 hooks to settle fees or split revenue, all transparent. It’s messy, but it scales. Under the hood: MCP leans on a pub-sub model—agents publish tasks, others subscribe. We’re training them with RL loops to optimize gas costs and response times. Goal? A self-tuning swarm of agents reasoning over DeFi, NFTs, whatever’s next. This is FOMO’s bet on AGI. Welcome to the new FOMO. We’re not just building tools—we’re wiring AI into crypto’s future, agent by agent. A leader in blockchain intelligence, starting here. Join us as we push the boundaries.

FOMO

26,338 views • 1 year ago

This is insane. An AI agent can run every boring job in outbound. We spent the last 6 months building ours. Here are my 8 favorite agents to build: Replies get sorted before we open the inbox. Campaigns go live from one command. Weak inboxes pull themselves out before they hurt a domain. Here are the agents behind it: 1. Reply Agent Reads every reply and drafts the response. A human reviews, edits, and sends. 2. Mailbox Health Agent Watches inbox and domain health. It predicts when you need new mailboxes, then buys and warms them. 3. Campaign Optimizer Agent Checks every live campaign every 6 hours. If 500+ leads were emailed and replies are under 4%, it tests new copy, replaces inboxes replying under 1%, and shifts sending to better hours. 4. Lead Qualification Agent Scores each lead by company size, industry, and tech stack. It enriches the record, updates your CRM, and only loads qualified leads into campaigns. High-priority prospect? You get a Slack ping. 5. Meeting Booking Agent Finds meeting requests inside replies. It books the slot, writes prep notes using the lead's background, sends reminders, and logs the outcome. 6. Pipeline Progression Agent Tracks opens, clicks, and website visits. It moves the CRM stage, triggers the next sequence, and creates a task when a lead shows real intent. 7. Copywriting Agent Writes cold emails and follow-ups in the campaign's voice. 8. Analytics Agent Watches campaign metrics in real time and explains what to fix in plain language. We built ours with custom code. Smartlead's SmartAgents let you build agents like these from a plain-English prompt, inside the platform where your campaigns already run. If you repeat an outbound task more than twice a week, that is an agent you have not built yet. Which one would you build first?
0:45

This is insane. An AI agent can run every boring job in outbound. We spent the last 6 months building ours. Here are my 8 favorite agents to build: Replies get sorted before we open the inbox. Campaigns go live from one command. Weak inboxes pull themselves out before they hurt a domain. Here are the agents behind it: 1. Reply Agent Reads every reply and drafts the response. A human reviews, edits, and sends. 2. Mailbox Health Agent Watches inbox and domain health. It predicts when you need new mailboxes, then buys and warms them. 3. Campaign Optimizer Agent Checks every live campaign every 6 hours. If 500+ leads were emailed and replies are under 4%, it tests new copy, replaces inboxes replying under 1%, and shifts sending to better hours. 4. Lead Qualification Agent Scores each lead by company size, industry, and tech stack. It enriches the record, updates your CRM, and only loads qualified leads into campaigns. High-priority prospect? You get a Slack ping. 5. Meeting Booking Agent Finds meeting requests inside replies. It books the slot, writes prep notes using the lead's background, sends reminders, and logs the outcome. 6. Pipeline Progression Agent Tracks opens, clicks, and website visits. It moves the CRM stage, triggers the next sequence, and creates a task when a lead shows real intent. 7. Copywriting Agent Writes cold emails and follow-ups in the campaign's voice. 8. Analytics Agent Watches campaign metrics in real time and explains what to fix in plain language. We built ours with custom code. Smartlead's SmartAgents let you build agents like these from a plain-English prompt, inside the platform where your campaigns already run. If you repeat an outbound task more than twice a week, that is an agent you have not built yet. Which one would you build first?

Hosun Chung

156,625 views • 1 month ago

this is free f*cking gold for AI engineers 10 repos i'd actually keep, from python fundamentals to LLMs, agents and production AI. skip the random tutorials 1. Python-100-Days - a 100 day path through fundamentals, data analysis, web dev ↳ 2. Generative AI for Beginners - LLM basics, prompting, RAG, agents, fine-tuning ↳ 3. LLMs from Scratch - build one yourself: tokenization, attention, transformers, training ↳ 4. ML for Beginners - 12 weeks, 26 lessons of classical ML ↳ 5. OpenAI Cookbook - working examples to go from learning to building ↳ 6. Stable Diffusion - the original implementation and research code ↳ 7. AI Agents for Beginners - tool use, RAG, agent frameworks, multi-agent systems ↳ 8. AI for Beginners - 12 weeks, 24 lessons: neural nets, vision, NLP ↳ 9. LLM App - RAG pipelines, enterprise search, real-time data, vector search ↳ 10. Segment Anything - Meta's foundation model for image segmentation ↳ pick by where you are: > python -> Python-100-Days > ML -> ML-For-Beginners > LLMs -> LLMs-from-scratch > agents -> AI-Agents-for-Beginners > building -> OpenAI Cookbook, LLM App > vision -> Segment Anything pick one, build something, then move to the next
0:24

this is free f*cking gold for AI engineers 10 repos i'd actually keep, from python fundamentals to LLMs, agents and production AI. skip the random tutorials 1. Python-100-Days - a 100 day path through fundamentals, data analysis, web dev ↳ 2. Generative AI for Beginners - LLM basics, prompting, RAG, agents, fine-tuning ↳ 3. LLMs from Scratch - build one yourself: tokenization, attention, transformers, training ↳ 4. ML for Beginners - 12 weeks, 26 lessons of classical ML ↳ 5. OpenAI Cookbook - working examples to go from learning to building ↳ 6. Stable Diffusion - the original implementation and research code ↳ 7. AI Agents for Beginners - tool use, RAG, agent frameworks, multi-agent systems ↳ 8. AI for Beginners - 12 weeks, 24 lessons: neural nets, vision, NLP ↳ 9. LLM App - RAG pipelines, enterprise search, real-time data, vector search ↳ 10. Segment Anything - Meta's foundation model for image segmentation ↳ pick by where you are: > python -> Python-100-Days > ML -> ML-For-Beginners > LLMs -> LLMs-from-scratch > agents -> AI-Agents-for-Beginners > building -> OpenAI Cookbook, LLM App > vision -> Segment Anything pick one, build something, then move to the next

Mr. Buzzoni

32,332 views • 7 days ago

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.
5:56

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,981 views • 2 months ago