Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

🤯 Hermes agent just got a Kanban task board, and it changes everything. Watch multiple AI agents collaborate in real time, each with a defined role, completing tasks with way more depth than your typical sub-agents. This is the future of multi-agent workflows 👇

boxmining's profile picture

Boxmining

176,559 subscribers

12,794 Aufrufe • vor 3 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

🚨BREAKING: Hermes Agent v0.11 Just Changed AI Agents Forever! Hermes Agent just dropped V0.11. Biggest update ever. 🔥 → Brand new terminal interface. →Unlimited sub-agents spawning sub-agents. →GPT-5.5 now works inside it. →Access to every major AI model from one tool. →Redirect your agent MID-task with one command. This is a full rebuild. 🤯 FREE and open source ↓
10:47

🚨BREAKING: Hermes Agent v0.11 Just Changed AI Agents Forever! Hermes Agent just dropped V0.11. Biggest update ever. 🔥 → Brand new terminal interface. →Unlimited sub-agents spawning sub-agents. →GPT-5.5 now works inside it. →Access to every major AI model from one tool. →Redirect your agent MID-task with one command. This is a full rebuild. 🤯 FREE and open source ↓

Julian Goldie SEO

24,027 Aufrufe • vor 3 Monaten

Anthropic's multi-agent researcher just explained how to actually build a graph of Claude agents: "Multi-agent is where fundamentally you have multiple agents or multiple Claudes working at the same time - one parent agent delegates tasks to five sub-agents that can each then work in parallel." the real architecture: parent agent → delegates to sub-agents (as tools) → sub-agents run in parallel → results roll back up the failure mode nobody talks about: "Overbuilt multi-agent systems spend too much time just talking back and forth with each other and not actually making progress on the main task." sound familiar? that's every bloated human org chart too in this 19-minute conversation, an Anthropic researcher lays out the real framework: parent → sub-agents → tools → context protection = the actual shape of a working agent graph
18:57

Anthropic's multi-agent researcher just explained how to actually build a graph of Claude agents: "Multi-agent is where fundamentally you have multiple agents or multiple Claudes working at the same time - one parent agent delegates tasks to five sub-agents that can each then work in parallel." the real architecture: parent agent → delegates to sub-agents (as tools) → sub-agents run in parallel → results roll back up the failure mode nobody talks about: "Overbuilt multi-agent systems spend too much time just talking back and forth with each other and not actually making progress on the main task." sound familiar? that's every bloated human org chart too in this 19-minute conversation, an Anthropic researcher lays out the real framework: parent → sub-agents → tools → context protection = the actual shape of a working agent graph

rewind

27,106 Aufrufe • vor 24 Tagen

Hermes Agent now has multi-agent via the Kanban, new in v0.12.0. Agents claim tasks from a board, work in parallel, and hand off when blocked. You watch progress and unblock from one easy view instead of juggling terminals. We asked it to plan and make this video about itself:
1:32

Hermes Agent now has multi-agent via the Kanban, new in v0.12.0. Agents claim tasks from a board, work in parallel, and hand off when blocked. You watch progress and unblock from one easy view instead of juggling terminals. We asked it to plan and make this video about itself:

Nous Research

1,461,105 Aufrufe • vor 3 Monaten

New agentic short course! Multi AI Agent Systems with crewAI, built with CrewAI's founder and CEO João Moura. In this course, you'll learn how to break down complex tasks into subtasks for multiple AI agents, each playing a specialized role, to execute. For example, to generate a research report, you might have researcher, writer, and quality assurance agents collaborate. You'll define the roles, expectations, and interactions between the agents—like a manager organizing a team. You'll work with key agentic AI techniques like role-playing, tool use, memory, guardrails, and cross-agent collaboration. And you'll build your own multi-agent systems that can tackle complex tasks. I think you'll find it both productive and fun to design agents and watch them collaborate to get things done. Let me know what you think! I believe multi-agent architectures will drive significant progress in AI systems. Please sign up here!
2:39

New agentic short course! Multi AI Agent Systems with crewAI, built with CrewAI's founder and CEO João Moura. In this course, you'll learn how to break down complex tasks into subtasks for multiple AI agents, each playing a specialized role, to execute. For example, to generate a research report, you might have researcher, writer, and quality assurance agents collaborate. You'll define the roles, expectations, and interactions between the agents—like a manager organizing a team. You'll work with key agentic AI techniques like role-playing, tool use, memory, guardrails, and cross-agent collaboration. And you'll build your own multi-agent systems that can tackle complex tasks. I think you'll find it both productive and fun to design agents and watch them collaborate to get things done. Let me know what you think! I believe multi-agent architectures will drive significant progress in AI systems. Please sign up here!

Andrew Ng

350,175 Aufrufe • vor 2 Jahren

It is now way easier to build multi-agent workflows in n8n with the new AI Agent Tool node. Instead of juggling sub workflows a parent AI Agent can now use other Agents as tools even several layers deep. Max shows how a cheap GPT 4.1 nano Agent handles heavy data and sends summaries to a parent Agent saving token costs and making debugging simpler. Watch the full walkthrough:
0:38

It is now way easier to build multi-agent workflows in n8n with the new AI Agent Tool node. Instead of juggling sub workflows a parent AI Agent can now use other Agents as tools even several layers deep. Max shows how a cheap GPT 4.1 nano Agent handles heavy data and sends summaries to a parent Agent saving token costs and making debugging simpler. Watch the full walkthrough:

n8n.io

27,766 Aufrufe • vor 1 Jahr

Hermes Desktop just removed the biggest barrier to AI agents. No more terminal. Here’s what changed everything: → You can now run Hermes in a clean Mac app → Edit memory + skills without SSH → Search every past conversation instantly → Run multi-agent workflows visually → Assign tasks like a real team board This turns AI from “tool” → “operator.” Save this video, you’ll finally understand how agents actually work. Want the SOP? DM me. 💬
9:16

Hermes Desktop just removed the biggest barrier to AI agents. No more terminal. Here’s what changed everything: → You can now run Hermes in a clean Mac app → Edit memory + skills without SSH → Search every past conversation instantly → Run multi-agent workflows visually → Assign tasks like a real team board This turns AI from “tool” → “operator.” Save this video, you’ll finally understand how agents actually work. Want the SOP? DM me. 💬

Julian Goldie SEO

43,325 Aufrufe • vor 3 Monaten

🚀 LAUNCHING: Genspark Multi-Agent Orchestration! One lead agent coordinates multiple sub-agents to tackle complex tasks. Watch the demo: Create 10 agents simultaneously - 10 professional slide decks in the time it takes to make one. Experience it: Blog:
0:45

🚀 LAUNCHING: Genspark Multi-Agent Orchestration! One lead agent coordinates multiple sub-agents to tackle complex tasks. Watch the demo: Create 10 agents simultaneously - 10 professional slide decks in the time it takes to make one. Experience it: Blog:

Genspark

23,144 Aufrufe • vor 1 Jahr

OPENCLAW JUST GOT A FREE MISSION CONTROL DASHBOARD CALLED NERVE. One clean interface to run multiple agents with kanban, voice mode, sub agent control, and live memory editing.
8:44

OPENCLAW JUST GOT A FREE MISSION CONTROL DASHBOARD CALLED NERVE. One clean interface to run multiple agents with kanban, voice mode, sub agent control, and live memory editing.

0xMarioNawfal

95,635 Aufrufe • vor 4 Monaten

Most AI agents work alone. Today, @convergence_ai_ just leveled up again with `Parallel Agents`: A swarm-style system that splits your task into sub-tasks, spins up multiple agents (each in its own browser!), and completes complex work in seconds. Here’s how it works. ↓
0:35

Most AI agents work alone. Today, @convergence_ai_ just leveled up again with `Parallel Agents`: A swarm-style system that splits your task into sub-tasks, spins up multiple agents (each in its own browser!), and completes complex work in seconds. Here’s how it works. ↓

Charly Wargnier

55,751 Aufrufe • vor 1 Jahr

Preview of our DeepResearchSwarm™ It's incomprehensibly fast as it leverages a multi-agent architecture instead of just one agent. It utilizes a joint hierarchical-parallel architecture that creates a plan and then concurrently executes the plan with multiple search agents. Workflow: Task → Research Director → multiple search agents → final summary by summarization agent. Stay tuned for the release ↓
1:09

Preview of our DeepResearchSwarm™ It's incomprehensibly fast as it leverages a multi-agent architecture instead of just one agent. It utilizes a joint hierarchical-parallel architecture that creates a plan and then concurrently executes the plan with multiple search agents. Workflow: Task → Research Director → multiple search agents → final summary by summarization agent. Stay tuned for the release ↓

swarms

17,729 Aufrufe • vor 1 Jahr

this is wild 🤯🤯🤯 just paired openai operator with replit agent to build an app watch as two ai agents team up, exchange credentials, and start testing ai agent 🤝 ai agent the future is here and it’s insane!
0:46

this is wild 🤯🤯🤯 just paired openai operator with replit agent to build an app watch as two ai agents team up, exchange credentials, and start testing ai agent 🤝 ai agent the future is here and it’s insane!

Lamar

1,821,606 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 1 Jahr

Kanban board is now a part of the Hermes Desktop app! I did a quick video showing how to enable this plugin, plus I ran a real task through the kanban process using multiple agent profiles. Super easy to do and the look of the kanban in the app is very clean! Take a look!
6:09

Kanban board is now a part of the Hermes Desktop app! I did a quick video showing how to enable this plugin, plus I ran a real task through the kanban process using multiple agent profiles. Super easy to do and the look of the kanban in the app is very clean! Take a look!

tonbi

45,052 Aufrufe • vor 12 Tagen

It’s getting insanely easy to build complex multi-agent systems in n8n. You can now build supervisor agents that delegates tasks to specialized sub agents. Just add the sub agents via AI Agent Tool node. All in one place and a lot easier to debug! Zero code!
1:46

It’s getting insanely easy to build complex multi-agent systems in n8n. You can now build supervisor agents that delegates tasks to specialized sub agents. Just add the sub agents via AI Agent Tool node. All in one place and a lot easier to debug! Zero code!

elvis

45,690 Aufrufe • vor 1 Jahr

THE FUTURE OF WORK: AI AGENT ORG CHARTS ARE HERE Companies are creating "AI heads of departments" — each managing 5–7 sub-agents to handle tasks just like a real team. Execs delegate to a chief agent, who routes tasks to department heads, who then deploy specialized sub-agents. Employees access their department's agent through a chatbot or voicebot — making AI as easy to use as Slack. Source: benjamlns on IG
1:14

THE FUTURE OF WORK: AI AGENT ORG CHARTS ARE HERE Companies are creating "AI heads of departments" — each managing 5–7 sub-agents to handle tasks just like a real team. Execs delegate to a chief agent, who routes tasks to department heads, who then deploy specialized sub-agents. Employees access their department's agent through a chatbot or voicebot — making AI as easy to use as Slack. Source: benjamlns on IG

Mario Nawfal

1,579,207 Aufrufe • vor 1 Jahr

🤝 AI Agents That Work Together — Collaboration Made Simple! In this demo, John explores one of Agent Forge’s most powerful features: agent-to-agent collaboration. With Agent Forge, you can create agents with different roles, connect them, and watch them collaborate to solve complex tasks. Modular, scalable, and fully automated. 🔗 Try here:
1:15

🤝 AI Agents That Work Together — Collaboration Made Simple! In this demo, John explores one of Agent Forge’s most powerful features: agent-to-agent collaboration. With Agent Forge, you can create agents with different roles, connect them, and watch them collaborate to solve complex tasks. Modular, scalable, and fully automated. 🔗 Try here:

AITECH CLOUD NETWORK

43,212 Aufrufe • vor 1 Jahr

HERMES AGENT JUST GOT A FULL NATIVE DESKTOP APP. MULTI-AGENT MANAGEMENT, PERSISTENT MEMORY AND AUTONOMOUS WORKFLOWS ALL IN ONE PLACE. No more CLI only. Run your 24/7 self-evolving AI agent from a proper desktop UI.
0:34

HERMES AGENT JUST GOT A FULL NATIVE DESKTOP APP. MULTI-AGENT MANAGEMENT, PERSISTENT MEMORY AND AUTONOMOUS WORKFLOWS ALL IN ONE PLACE. No more CLI only. Run your 24/7 self-evolving AI agent from a proper desktop UI.

0xMarioNawfal

188,313 Aufrufe • vor 2 Monaten

Introducing Upstash AI Agents! 🎉 ◆ Build production-ready AI workflows in minutes ◆ Specialize agents with tools (research, writing, analysis) ◆ Works with Vercel AI SDK, Langchain and more The best way to write AI agent workflows, fully customizable 👇🏻
1:57

Introducing Upstash AI Agents! 🎉 ◆ Build production-ready AI workflows in minutes ◆ Specialize agents with tools (research, writing, analysis) ◆ Works with Vercel AI SDK, Langchain and more The best way to write AI agent workflows, fully customizable 👇🏻

Upstash

39,117 Aufrufe • vor 1 Jahr

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 Aufrufe • vor 29 Tagen