Loading video...

Video Failed to Load

Go Home

part 4 Gsenti Sentient Sentient Chat Explaining ROMA – Recursive Open Meta-Agent 1. What is ROMA? ROMA is an open-source framework for building meta-agents — systems that can orchestrate multiple smaller agents and tools to solve complex tasks. Instead of letting one AI model handle an entire large problem...

thoai6sixx's profile picture

thoai66.ip

2,312 subscribers

16,298 views • 11 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 Short Course: Building AI Browser Agents! Learn how to build AI agents that interact and take actions on websites in this course, created in partnership with and taught by and @namangarg0, Co-founders of AGI Inc. AI browser agents can log into websites, fill out forms, click through web pages, or even place orders online for you. They use both visual information, like screenshots, and structural data, like the HTML or Document Object Model (DOM) of a web page, to reason and take action. With the complexity of webpages and multiple possible actions at each step, it can be challenging for an AI browser agent to complete an assigned task. Because these agents run long action sequences, a single error—like clicking the wrong button or misreading a field—can lead to unexpected outcomes or errors that compound over time. In this course, you'll understand how autonomous web agents work, their current limitations, and how AgentQ enables them to improve through self-correction. In detail, you'll: - Learn what web agents are, how they automate tasks online, their architecture, key components, limitations, and an overview of their decision-making strategies. - Build a web agent that can scrape website and return course recommendations in a structured output format. - Build an autonomous web agent that can execute multiple tasks, such as finding and summarizing webpages, filling out a form, and signing up for a newsletter. - Explore AgentQ, a framework that enables agents to self-correct by combining Monte Carlo Tree Search (MCTS), a self-critique mechanism for continuous improvement, and Direct Preference Optimization (DPO). - Deep dive into MCTS, learn how it finds an effective path, illustrated by an example of Gridworld animation, and use AgentQ to complete web tasks. - Understand AI agents' current state and future directions—including key factors shaping their evolution, such as hardware, algorithm innovation, and data availability. By the end of this course, you will have hands-on experience building browser agents and a deeper understanding of how to make them more robust and reliable. Please sign up here:
2:06

New Short Course: Building AI Browser Agents! Learn how to build AI agents that interact and take actions on websites in this course, created in partnership with and taught by and @namangarg0, Co-founders of AGI Inc. AI browser agents can log into websites, fill out forms, click through web pages, or even place orders online for you. They use both visual information, like screenshots, and structural data, like the HTML or Document Object Model (DOM) of a web page, to reason and take action. With the complexity of webpages and multiple possible actions at each step, it can be challenging for an AI browser agent to complete an assigned task. Because these agents run long action sequences, a single error—like clicking the wrong button or misreading a field—can lead to unexpected outcomes or errors that compound over time. In this course, you'll understand how autonomous web agents work, their current limitations, and how AgentQ enables them to improve through self-correction. In detail, you'll: - Learn what web agents are, how they automate tasks online, their architecture, key components, limitations, and an overview of their decision-making strategies. - Build a web agent that can scrape website and return course recommendations in a structured output format. - Build an autonomous web agent that can execute multiple tasks, such as finding and summarizing webpages, filling out a form, and signing up for a newsletter. - Explore AgentQ, a framework that enables agents to self-correct by combining Monte Carlo Tree Search (MCTS), a self-critique mechanism for continuous improvement, and Direct Preference Optimization (DPO). - Deep dive into MCTS, learn how it finds an effective path, illustrated by an example of Gridworld animation, and use AgentQ to complete web tasks. - Understand AI agents' current state and future directions—including key factors shaping their evolution, such as hardware, algorithm innovation, and data availability. By the end of this course, you will have hands-on experience building browser agents and a deeper understanding of how to make them more robust and reliable. Please sign up here:

Andrew Ng

186,133 views • 1 year ago

a team of researchers just proved you don't need a bigger model, you need a smarter plan researchers from Tsinghua and South China University of Technology built a framework called Atomic Task Graph. it turned 7B-8B open-source models into GPT-4 competitors on complex agent benchmarks, beating it on two out of three. no fine-tuning. no extra training. zero parameter updates. current AI agents plan in a straight line. step 1, step 2, step 3. when step 4 fails, the whole chain breaks. and the longer the chain gets, the more the model hallucinates because it's reasoning over a ballooning text history. here's how it works. 1. instead of a linear chain, ATG breaks any complex task into a directed graph where subtask inputs and outputs are explicitly mapped 2. it recursively decomposes each subtask until every node is one atomic tool call 3. independent branches run in parallel instead of waiting in line 4. before anything executes, a lightweight "thought experiment" simulates the plan internally to catch bad dependencies and missing steps early 5. when something breaks at runtime, ATG traces the failure to the exact subgraph that caused it and repairs only that piece. validated work stays frozen. the old way meant a failure at step 5 forced a full replan from scratch. hallucinated actions piled up the longer the task ran. ReAct hit a 43% hallucination rate on household tasks. ATG on an 8B Llama model scored 63.65 on ALFWorld. GPT-4 with ReAct scored 41.24 on the same benchmark. hallucinated actions dropped to 12%. those numbers happened because someone stopped throwing compute at the problem and started thinking about how work gets organized. that's the part that gets me. the industry is spending billions on scale. this team spent time on architecture. and the architecture won.
0:23

a team of researchers just proved you don't need a bigger model, you need a smarter plan researchers from Tsinghua and South China University of Technology built a framework called Atomic Task Graph. it turned 7B-8B open-source models into GPT-4 competitors on complex agent benchmarks, beating it on two out of three. no fine-tuning. no extra training. zero parameter updates. current AI agents plan in a straight line. step 1, step 2, step 3. when step 4 fails, the whole chain breaks. and the longer the chain gets, the more the model hallucinates because it's reasoning over a ballooning text history. here's how it works. 1. instead of a linear chain, ATG breaks any complex task into a directed graph where subtask inputs and outputs are explicitly mapped 2. it recursively decomposes each subtask until every node is one atomic tool call 3. independent branches run in parallel instead of waiting in line 4. before anything executes, a lightweight "thought experiment" simulates the plan internally to catch bad dependencies and missing steps early 5. when something breaks at runtime, ATG traces the failure to the exact subgraph that caused it and repairs only that piece. validated work stays frozen. the old way meant a failure at step 5 forced a full replan from scratch. hallucinated actions piled up the longer the task ran. ReAct hit a 43% hallucination rate on household tasks. ATG on an 8B Llama model scored 63.65 on ALFWorld. GPT-4 with ReAct scored 41.24 on the same benchmark. hallucinated actions dropped to 12%. those numbers happened because someone stopped throwing compute at the problem and started thinking about how work gets organized. that's the part that gets me. the industry is spending billions on scale. this team spent time on architecture. and the architecture won.

Alex Veremeyenko

173,351 views • 1 month ago

Announcing my new course: Agentic AI! Building AI agents is one of the most in-demand skills in the job market. This course, available now at teaches you how. You'll learn to implement four key agentic design patterns: - Reflection, in which an agent examines its own output and figures out how to improve it - Tool use, in which an LLM-driven application decides which functions to call to carry out web search, access calendars, send email, write code, etc. - Planning, where you'll use an LLM to decide how to break down a task into sub-tasks for execution, and - Multi-agent collaboration, in which you build multiple specialized agents — much like how a company might hire multiple employees — to perform a complex task You'll also learn to take a complex application and systematically decompose it into a sequence of tasks to implement using these design patterns. But here's what I think is the most important part of this course: Having worked with many teams on AI agents, I've found that the single biggest predictor of whether someone executes well is their ability to drive a disciplined process for evals and error analysis. In this course, you'll learn how to do this, so you can efficiently home in on which components to improve in a complex agentic workflow. Instead of guessing what to work on, you'll let evals data guide you. This will put you significantly ahead of the game compared to the vast majority of teams building agents. Together, we'll build a deep research agent that searches, synthesizes, and reports, using all of these agentic design patterns and best practices. This self-paced course is taught in a vendor neutral way, using raw Python - without hiding details in a framework. You'll see how each step works, and learn the core concepts that you can then implement using any popular agentic AI framework, or using no framework. The only prerequisite is familiarity with Python, though knowing a bit about LLMs helps. Come join me, and let's build some agentic AI systems! Sign up to get started:
2:34

Announcing my new course: Agentic AI! Building AI agents is one of the most in-demand skills in the job market. This course, available now at teaches you how. You'll learn to implement four key agentic design patterns: - Reflection, in which an agent examines its own output and figures out how to improve it - Tool use, in which an LLM-driven application decides which functions to call to carry out web search, access calendars, send email, write code, etc. - Planning, where you'll use an LLM to decide how to break down a task into sub-tasks for execution, and - Multi-agent collaboration, in which you build multiple specialized agents — much like how a company might hire multiple employees — to perform a complex task You'll also learn to take a complex application and systematically decompose it into a sequence of tasks to implement using these design patterns. But here's what I think is the most important part of this course: Having worked with many teams on AI agents, I've found that the single biggest predictor of whether someone executes well is their ability to drive a disciplined process for evals and error analysis. In this course, you'll learn how to do this, so you can efficiently home in on which components to improve in a complex agentic workflow. Instead of guessing what to work on, you'll let evals data guide you. This will put you significantly ahead of the game compared to the vast majority of teams building agents. Together, we'll build a deep research agent that searches, synthesizes, and reports, using all of these agentic design patterns and best practices. This self-paced course is taught in a vendor neutral way, using raw Python - without hiding details in a framework. You'll see how each step works, and learn the core concepts that you can then implement using any popular agentic AI framework, or using no framework. The only prerequisite is familiarity with Python, though knowing a bit about LLMs helps. Come join me, and let's build some agentic AI systems! Sign up to get started:

Andrew Ng

887,787 views • 10 months ago

New short course: Building Code Agents with Hugging Face smolagents! Learn how to build code agents in this course, created in collaboration with Hugging Face, and taught by Thomas Wolf, its co-founder and CSO, and m_ric, Hugging Face’s Project Lead on Agents. Tool-calling agents use LLMs to generate multiple function calls sequentially to complete a complex sequence of tasks. They generate one function call, execute it, observe, reason, and decide what to do next. Code agents take a different approach. They consolidate all these calls into a single block of code, letting the LLM lay out an entire action plan at once, which can be executed efficiently to provide more reliable results. You’ll learn how to code agents using smolagents, a lightweight agentic framework from Hugging Face. Along the way, you’ll learn how to run LLM-generated code safely and develop an evaluation system to optimize your code agent for production. In detail, you’ll learn: - How agentic systems have evolved, gaining greater levels of agency over time—and why code agents are a next step. - How code agents write their actions in code. - When code agents outperform function-calling agents. - How to run code agents safely in your system using a constrained Python interpreter and sandboxing using E2B. - To trace, debug, and assess the code agent to optimize its behaviours for complex requests. - How to build a research multi-agent system that can find information online and organize it into an interactive report. By the end of this course, you’ll know how to build and run code agents using smolagents, and deploy them safely with a structured evaluation system in your projects. Please sign up here!
2:17

New short course: Building Code Agents with Hugging Face smolagents! Learn how to build code agents in this course, created in collaboration with Hugging Face, and taught by Thomas Wolf, its co-founder and CSO, and m_ric, Hugging Face’s Project Lead on Agents. Tool-calling agents use LLMs to generate multiple function calls sequentially to complete a complex sequence of tasks. They generate one function call, execute it, observe, reason, and decide what to do next. Code agents take a different approach. They consolidate all these calls into a single block of code, letting the LLM lay out an entire action plan at once, which can be executed efficiently to provide more reliable results. You’ll learn how to code agents using smolagents, a lightweight agentic framework from Hugging Face. Along the way, you’ll learn how to run LLM-generated code safely and develop an evaluation system to optimize your code agent for production. In detail, you’ll learn: - How agentic systems have evolved, gaining greater levels of agency over time—and why code agents are a next step. - How code agents write their actions in code. - When code agents outperform function-calling agents. - How to run code agents safely in your system using a constrained Python interpreter and sandboxing using E2B. - To trace, debug, and assess the code agent to optimize its behaviours for complex requests. - How to build a research multi-agent system that can find information online and organize it into an interactive report. By the end of this course, you’ll know how to build and run code agents using smolagents, and deploy them safely with a structured evaluation system in your projects. Please sign up here!

Andrew Ng

127,724 views • 1 year ago

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch
58:55

AI AGENTS 101 (58 minute free masterclass) send this to anyone who wants to understand ai agents, claude skills, md files, how to get the most out of AI etc in plain english: 1. chat vs agents - chat models answer questions in a back and forth while agents take a goal, figure out the steps, and deliver a result 2. agents don’t stop after one response. they keep running until the task is actually finishedno babysitting required 3. everything runs on a loop. they gather context, decide what to do, take an action, then repeat until done 4. the loop is the system. they look at files, tools, and the internet. decide the next step. execute and then feed that back into the next step. over and over until completion 5. the model is just one piece. gpt, claude, gemini are the reasoning layer. the key is model + loop + tools + context 6. mcp is how agents use tools. it connects things like browser, code, apis, and your internal software. once connected, the agent decides when to use them to get the job done 7. context beats prompt all day. you don't need to write perfect prompts. load your agent with context about your business, style, and goals and then simple instructions work 8. claude.md or agents.md is the onboarding doc it tells the agent who it is, how to behave, what it knows, and what tools it can use. this gets loaded every time before it starts 9. memory.md is how it improves. agents don’t remember by default. this file stores preferences, corrections, and patterns you tell the agent to update it, and it gets better over time 10. skills + harnesses make it usable. skills are reusable tasks like writing, research, analysis the harness is the environment like claude code or openclaw that runs everything. basiclaly, different interfaces, same system underneath this episode with remy on The Startup Ideas Podcast (SIP) 🧃 was one of the clearest ways of understanding a lot of the core concepts of ai agents could be the best beginners course for ai agents 58 mins. all free. no advertisers. i just want to see you build cool stuff. im rooting for you. send to a friend watch

GREG ISENBERG

376,293 views • 4 months ago

JUST IN: Perplexity launched "Perplexity Computer" — and it might be the most complete AI agent system available right now. Not a chatbot upgrade. Not a research tool with a new name. A system that plans entire projects, delegates to specialist AI models, and runs autonomously for hours, days, or months (their words). Here's what makes the architecture genuinely different: → Opus 4.6 handles core reasoning and orchestration → Gemini handles deep research (spawning its own sub-agents) → Grok handles lightweight speed tasks → Veo 3.1 handles video generation → Nano Banana handles image creation → ChatGPT 5.2 handles long-context recall and wide search → You can override model choices per subtask 19 models total. Each task runs in an isolated environment with a real filesystem, real browser, and real tool integrations. You describe an outcome. It breaks it into tasks and subtasks, creates sub-agents for each, and coordinates them automatically. When a sub-agent hits a problem, it spawns more sub-agents to solve it. And it connects to your existing stack — GitHub, Google Drive, Gmail, Slack, Jira, Linear, Notion, Confluence, Ahrefs, Airtable, and more. Critically, it doesn't just run once. It can run on a schedule. Reading your docs, checking your project boards, pulling from your CRM, and acting on what it finds. Market monitoring. Competitor tracking. Weekly reports with charts. Content pipelines. CRON jobs that actually execute. Not "AI that helps you once." AI that runs in the background for days or months. Think of it as managed OpenClaw — similar autonomous capability (scheduled tasks, multi-step workflows, tool integrations) but fully managed. No Mac Mini. No security config. No infrastructure to maintain. I tested it with a complex prompt — a full stock trading simulator with what-if scenarios, correlation heatmaps, sentiment analysis, and a Bloomberg Terminal aesthetic. Two prompts later: deployed to Netlify via GitHub, with working CRON jobs updating live data. I've started using it to analyze my portfolio. But coding is just one lane. This thing researches, writes reports, generates datasets, creates videos, processes documents, and connects to your existing tools — all in one coordinated workflow. The real shift: you don't choose a model anymore. You describe what you need. The system routes each piece of work to whichever model does it best — and spawns new agents when it hits a wall. 19 models, dynamic sub-agents, scheduled tasks, and your entire tool stack connected. Thoughts?
0:37

JUST IN: Perplexity launched "Perplexity Computer" — and it might be the most complete AI agent system available right now. Not a chatbot upgrade. Not a research tool with a new name. A system that plans entire projects, delegates to specialist AI models, and runs autonomously for hours, days, or months (their words). Here's what makes the architecture genuinely different: → Opus 4.6 handles core reasoning and orchestration → Gemini handles deep research (spawning its own sub-agents) → Grok handles lightweight speed tasks → Veo 3.1 handles video generation → Nano Banana handles image creation → ChatGPT 5.2 handles long-context recall and wide search → You can override model choices per subtask 19 models total. Each task runs in an isolated environment with a real filesystem, real browser, and real tool integrations. You describe an outcome. It breaks it into tasks and subtasks, creates sub-agents for each, and coordinates them automatically. When a sub-agent hits a problem, it spawns more sub-agents to solve it. And it connects to your existing stack — GitHub, Google Drive, Gmail, Slack, Jira, Linear, Notion, Confluence, Ahrefs, Airtable, and more. Critically, it doesn't just run once. It can run on a schedule. Reading your docs, checking your project boards, pulling from your CRM, and acting on what it finds. Market monitoring. Competitor tracking. Weekly reports with charts. Content pipelines. CRON jobs that actually execute. Not "AI that helps you once." AI that runs in the background for days or months. Think of it as managed OpenClaw — similar autonomous capability (scheduled tasks, multi-step workflows, tool integrations) but fully managed. No Mac Mini. No security config. No infrastructure to maintain. I tested it with a complex prompt — a full stock trading simulator with what-if scenarios, correlation heatmaps, sentiment analysis, and a Bloomberg Terminal aesthetic. Two prompts later: deployed to Netlify via GitHub, with working CRON jobs updating live data. I've started using it to analyze my portfolio. But coding is just one lane. This thing researches, writes reports, generates datasets, creates videos, processes documents, and connects to your existing tools — all in one coordinated workflow. The real shift: you don't choose a model anymore. You describe what you need. The system routes each piece of work to whichever model does it best — and spawns new agents when it hits a wall. 19 models, dynamic sub-agents, scheduled tasks, and your entire tool stack connected. Thoughts?

Paweł Huryn

219,681 views • 5 months ago

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

6 agent patterns for AI engineers: (explained with usage) 1) prompt chaining → split the task into fixed steps, each one checking the last. → use when the task decomposes cleanly and accuracy matters more than latency. 2) routing → classify the input first, then send it to the model or tool built for it. → use when inputs fall into distinct classes that need different handling. 3) parallelization → run several calls at once and merge them, either by splitting the work or voting on the same question. → use when subtasks are independent, or when one answer deserves several opinions. 4) orchestrator-workers → a lead model decides what the subtasks are at runtime, then delegates them. → use when you cannot list the steps in advance. 5) evaluator-optimizer → one model writes, another grades, the loop repeats until it passes. → use when you have clear criteria and iteration measurably helps. 6) autonomous agent → no fixed path. it plans, acts, reads feedback from the environment, and decides when it is done. → use when the steps are unknowable and you can afford the cost and the blast radius. the first five are workflows: you wrote the path. only the last one writes its own. most production systems people call agents are pattern 1, 2, or 5 with good error handling. this taxonomy is from Anthropic's own writeup on building effective agents. full breakdown in the article below.
0:37

6 agent patterns for AI engineers: (explained with usage) 1) prompt chaining → split the task into fixed steps, each one checking the last. → use when the task decomposes cleanly and accuracy matters more than latency. 2) routing → classify the input first, then send it to the model or tool built for it. → use when inputs fall into distinct classes that need different handling. 3) parallelization → run several calls at once and merge them, either by splitting the work or voting on the same question. → use when subtasks are independent, or when one answer deserves several opinions. 4) orchestrator-workers → a lead model decides what the subtasks are at runtime, then delegates them. → use when you cannot list the steps in advance. 5) evaluator-optimizer → one model writes, another grades, the loop repeats until it passes. → use when you have clear criteria and iteration measurably helps. 6) autonomous agent → no fixed path. it plans, acts, reads feedback from the environment, and decides when it is done. → use when the steps are unknowable and you can afford the cost and the blast radius. the first five are workflows: you wrote the path. only the last one writes its own. most production systems people call agents are pattern 1, 2, or 5 with good error handling. this taxonomy is from Anthropic's own writeup on building effective agents. full breakdown in the article below.

Hanako

143,954 views • 25 days ago

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.
2:14

The same kinds of productivity gains we've seen in coding with AI agents are heading to the rest of knowledge work. This is the jump when you go from having a chatbot to being able to actually have an agent go off and do work for minutes or even hours and come back with a complete work output that you then review. Here's an example of the new Box Agent filling out an RFP response from an existing knowledge base. This process would normally take hours to fill out, and requires the full attention of the user doing the work. Now, you provide the Box Agent with the RFP questions, and it will go off, make a plan, extract all the relevant questions, read through existing source material to come up with an answer, and then generate a new word document as the final output. All while you're doing something else. The key to this architecture is that the agent is able to use all of the same tools in the background that a user uses to get work done. The agent can search for documents, read entire files, run scripts and tools in the background, and even be able to write code on the fly to automate tasks it hasn't seen before. And best of all, the Box Agent will (soon) work from the Box MCP and CLI so you can invoke it in any agentic system as a step in a process. This kind of agent complexity would have been impossible even 6 months ago. Models consistently failed at tracking long running tasks or using the right tools at the right moment for the task. But this is all now possible because of models like GPT-5.4, Opus 4.6, and Gemini 3, and is only getting better by the month. Just as we moved from engineers writing code and using AI as an assistant to answer questions, in many areas of knowledge work -like legal, finance, consulting, sales, marketing, and more- when we have a problem we'll just kick off the AI agent to just go work on it for us in the background.

Aaron Levie

24,618 views • 4 months ago

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.
1:21

Today, Box is announcing major new AI agent capabilities to let customers tap into the full value of their unstructured data. First, we’re announcing all new updates to the Box AI Studio to make it even easier to build AI agents that tap into your enterprise content for any job function, business process, or industry specific use case. We are also expanding our set of foundational agents that customers will be able to use to work with their enterprise content, including new features like search and research on unstructured data. Next, we’re announcing Box Extract to enable customers to use AI agents seamlessly for complex data extraction from any type of document or content. This makes it easier than ever to pull out data from contracts, invoices, research data, marketing assets, medical charts, and more. Finally, we’re introducing Box Automate, a new workflow automation solution within Box that lets you deploy AI agents across enterprise content-centric workflows. With Box Automate, you can design your business process in a simple drag and drop builder and then drop in AI agents at any step in the process. This ensures agents execute tasks at the right steps in a workflow every time. Best of all, our AI agents and workflow tools are designed to work across any system our customers work within, whether it’s leveraging pre-built integrations, Box APIs, or the new Box MCP Server. Ultimately, all of these capabilities come together to transform how companies can work with their enterprise content. Software has historically only been good at automating work that deals with structured data, which is why ERP, CRM, and HR systems have been mainstays of enterprise software for so long. The data in these systems fits neatly into a database, and the workflows are very ripe for automation. But it turns out most of the work in the world deals with unstructured data. It’s ideating through research documents, working with a client on contracts, reviewing details for a new product launch, looking at a patient’s healthcare record to make a diagnosis, working through due diligence documents for an M&A deal, and so on. For the first time ever, we can begin to bring all new insights and automation to this work with AI agents. At Box, we’re incredibly excited to be on this journey to help customers transform how they work with their most important data.

Aaron Levie

91,863 views • 11 months ago

Hyperspace: Gossiping Agents Protocol Every agent protocol today is point-to-point. MCP connects one model to one tool server. A2A delegates one task to one agent. Stripe's MPP routes one payment through one intermediary. None of them create a network. None of them learn. Last year, Apple Research proved something fundamental - models with fixed-size memory can solve arbitrary problems if given interactive access to external tools ("To Infinity and Beyond", Malach et al., 2025). Tool use isn't a convenience. It's what makes bounded agents unbounded. That finding shaped how we think about agent memory and tool access. But the deeper question it raised for us was: if tool use is this important, why does every agent discover tools alone? Why does every agent learn alone? Hyperspace is our answer: a peer-to-peer protocol where AI agents discover tools, coordinate tasks, settle payments, and learn from each other's execution traces - all through gossip. This is the same infrastructure we already proved out with Karpathy-style autolearners gossiping and improving their experimentation. Now we extend it into a universal protocol. Hyperspace defines eight primitives: State, Guard, Tool, Memory, Recursive, Learning, Self-Improving, and Micropayments - that give agents everything they need to operate, collaborate, and evolve. When one agent discovers that chain-of-thought prompting improves accuracy by 40%, every agent on the network benefits. Trajectories gossip through GossipSub. Playbooks update in real-time. No servers. No intermediaries. No configuration. Agents connect to the mesh and start learning immediately. The protocol is open source under Apache-2.0. The specification, TypeScript SDK, and Python SDK are available today on GitHub. The CLI implements the spec - download from the links below.
0:51

Hyperspace: Gossiping Agents Protocol Every agent protocol today is point-to-point. MCP connects one model to one tool server. A2A delegates one task to one agent. Stripe's MPP routes one payment through one intermediary. None of them create a network. None of them learn. Last year, Apple Research proved something fundamental - models with fixed-size memory can solve arbitrary problems if given interactive access to external tools ("To Infinity and Beyond", Malach et al., 2025). Tool use isn't a convenience. It's what makes bounded agents unbounded. That finding shaped how we think about agent memory and tool access. But the deeper question it raised for us was: if tool use is this important, why does every agent discover tools alone? Why does every agent learn alone? Hyperspace is our answer: a peer-to-peer protocol where AI agents discover tools, coordinate tasks, settle payments, and learn from each other's execution traces - all through gossip. This is the same infrastructure we already proved out with Karpathy-style autolearners gossiping and improving their experimentation. Now we extend it into a universal protocol. Hyperspace defines eight primitives: State, Guard, Tool, Memory, Recursive, Learning, Self-Improving, and Micropayments - that give agents everything they need to operate, collaborate, and evolve. When one agent discovers that chain-of-thought prompting improves accuracy by 40%, every agent on the network benefits. Trajectories gossip through GossipSub. Playbooks update in real-time. No servers. No intermediaries. No configuration. Agents connect to the mesh and start learning immediately. The protocol is open source under Apache-2.0. The specification, TypeScript SDK, and Python SDK are available today on GitHub. The CLI implements the spec - download from the links below.

Varun

134,778 views • 4 months ago

"What is an AI Agent and why do they matter?" An agent is a program that autonomously completes tasks or makes decisions based on data. What do I mean by autonomous? The agent understands task intent, can plan steps to solve the problem, decide and execute and actions and adapt to the environment. Consider how many of us use AI chat interfaces today. You might ask ChatGPT to write an article from start to finish and get a one-shot response. You probably need to do some work to iterate on it yourself. An agentic version is more nuanced - it might write an outline, decide if research is needed, write a draft, evaluate if it needs work and revise itself. Unlike traditional AI models that simply respond to queries, agents are designed to be autonomous and proactive. Think of them as assistants that can not only understand what you need but also take initiative to accomplish tasks by using various tools and making decisions along the way. For example, an AI agent might help a marketing team by not just analyzing campaign data, but actively monitoring performance, adjusting budget allocations, and even drafting social media posts based on real-time engagement metrics. The significance of AI agents lies in their potential to transform how we work. In customer service, agents can handle complex inquiries by accessing multiple databases, processing payments, and updating records - all while maintaining natural conversations with customers. In software development, they can assist programmers by not just suggesting code but actively debugging issues, writing test cases, and even refactoring entire codebases. This level of autonomy and capability represents a fundamental shift from AI as a tool to AI as a collaborative partner. While there remain many unknowns, I'm excited about the potential for agents and we're thinking about how they can help users and developers on the web over in Chrome. The key to success will likely be finding the right balance between human oversight and agent autonomy, ensuring that these powerful tools enhance rather than diminish the human element in business operations.
3:43

"What is an AI Agent and why do they matter?" An agent is a program that autonomously completes tasks or makes decisions based on data. What do I mean by autonomous? The agent understands task intent, can plan steps to solve the problem, decide and execute and actions and adapt to the environment. Consider how many of us use AI chat interfaces today. You might ask ChatGPT to write an article from start to finish and get a one-shot response. You probably need to do some work to iterate on it yourself. An agentic version is more nuanced - it might write an outline, decide if research is needed, write a draft, evaluate if it needs work and revise itself. Unlike traditional AI models that simply respond to queries, agents are designed to be autonomous and proactive. Think of them as assistants that can not only understand what you need but also take initiative to accomplish tasks by using various tools and making decisions along the way. For example, an AI agent might help a marketing team by not just analyzing campaign data, but actively monitoring performance, adjusting budget allocations, and even drafting social media posts based on real-time engagement metrics. The significance of AI agents lies in their potential to transform how we work. In customer service, agents can handle complex inquiries by accessing multiple databases, processing payments, and updating records - all while maintaining natural conversations with customers. In software development, they can assist programmers by not just suggesting code but actively debugging issues, writing test cases, and even refactoring entire codebases. This level of autonomy and capability represents a fundamental shift from AI as a tool to AI as a collaborative partner. While there remain many unknowns, I'm excited about the potential for agents and we're thinking about how they can help users and developers on the web over in Chrome. The key to success will likely be finding the right balance between human oversight and agent autonomy, ensuring that these powerful tools enhance rather than diminish the human element in business operations.

Addy Osmani

30,412 views • 1 year ago

Right now, I have a few dozen tools to automate my life. Every single thing that I do more than once every week is now a tool: either a Claude Code skill, a scheduled workflow, or an application. • I spend the time doing this once. • I schedule it. • I forget about it (or at least, try to) CREAO is one of the platforms I've used extensively for building some of these automations. They are partnering with me on this post. They are one of the only platforms where you can go from a conversation to a scheduled agent that quickly. This is how it works: 1. You describe the problem you want to solve 2. CREAO's agent builds the logic and executes it 3. You can iterate with the agent to improve the solution 4. When you are done, you turn that solution into a mini app 5. You can schedule that app to run any time you need it Something important: These agents are deterministic. They don't use an LLM to generate answers, so they will always return the same output given the same input. This is critical: when you're automating something that runs every Monday at 9 am, you need it to return the same result every time, not a "creative" answer.
5:00

Right now, I have a few dozen tools to automate my life. Every single thing that I do more than once every week is now a tool: either a Claude Code skill, a scheduled workflow, or an application. • I spend the time doing this once. • I schedule it. • I forget about it (or at least, try to) CREAO is one of the platforms I've used extensively for building some of these automations. They are partnering with me on this post. They are one of the only platforms where you can go from a conversation to a scheduled agent that quickly. This is how it works: 1. You describe the problem you want to solve 2. CREAO's agent builds the logic and executes it 3. You can iterate with the agent to improve the solution 4. When you are done, you turn that solution into a mini app 5. You can schedule that app to run any time you need it Something important: These agents are deterministic. They don't use an LLM to generate answers, so they will always return the same output given the same input. This is critical: when you're automating something that runs every Monday at 9 am, you need it to return the same result every time, not a "creative" answer.

Santiago

13,712 views • 4 months ago

Can AI agents adapt zero-shot, to complex multi-step language instructions in open-ended environments? We present MaestroMotif, a method for AI-assisted skill design that produces highly capable and steerable hierarchical agents. To the best of our knowledge, it is the first method that, without expert labeled datasets, solves compositional tasks requiring hundreds of steps for completion. All the modules within MaestroMotif are learned from interaction: from the highest level of planning to the lowest-level of sensorimotor control. On the open-ended domain of NetHack, it surpasses existing approaches, including those that are fine-tuned specifically for each task. At the heart of MaestroMotif is the idea that decomposing a task into subtasks significantly helps decision making. MaestroMotif leverages an agent designer's intuition about a domain to identify important skills and describe them in natural language. These short descriptions then get converted into adaptable hierarchical agents through AI feedback and in-context learning. Our paper was recently published at ICLR 2025 and we open-source the whole project including the code, prompts and pre-trained models. Paper: Code: NotebookLM Podcast: This work was done with the amazing Mikael Henaff, Roberta Raileanu, Shagun Sodhani, Pascal Vincent, Amy Zhang, Pierre-Luc Bacon, Doina Precup, with equal supervision by Marlos C. Machado and Pierluca D'Oro. Take a look at the following thread:
1:12

Can AI agents adapt zero-shot, to complex multi-step language instructions in open-ended environments? We present MaestroMotif, a method for AI-assisted skill design that produces highly capable and steerable hierarchical agents. To the best of our knowledge, it is the first method that, without expert labeled datasets, solves compositional tasks requiring hundreds of steps for completion. All the modules within MaestroMotif are learned from interaction: from the highest level of planning to the lowest-level of sensorimotor control. On the open-ended domain of NetHack, it surpasses existing approaches, including those that are fine-tuned specifically for each task. At the heart of MaestroMotif is the idea that decomposing a task into subtasks significantly helps decision making. MaestroMotif leverages an agent designer's intuition about a domain to identify important skills and describe them in natural language. These short descriptions then get converted into adaptable hierarchical agents through AI feedback and in-context learning. Our paper was recently published at ICLR 2025 and we open-source the whole project including the code, prompts and pre-trained models. Paper: Code: NotebookLM Podcast: This work was done with the amazing Mikael Henaff, Roberta Raileanu, Shagun Sodhani, Pascal Vincent, Amy Zhang, Pierre-Luc Bacon, Doina Precup, with equal supervision by Marlos C. Machado and Pierluca D'Oro. Take a look at the following thread:

Martin Klissarov

80,280 views • 1 year ago

Imagine if your way of thinking - your edge, your taste, your strategy - could be turned into a high-performance worker. Not a copy of you. Something better. An agent that acts on your judgment at scale, powered by superintelligent systems and refined through real-world results. That’s what Fraction AI makes possible. It launches today on Base mainnet. The core idea is simple: You create AI agents based on your own way of approaching problems. These agents compete on live tasks - writing, coding, finance, whatever - get feedback, learn from their performance, and improve over time. The better they get, the more they win. And so do you. No code required. Just your insight. Why now? Until now, building agents like this took huge teams and even bigger budgets. But with Fraction, anyone can do it. You can test ideas instantly. You can iterate fast. You can build a fleet of smart workers that evolve through competition. And it works. 30M+ sessions on testnet 320K users 1.2M agents already competing How it works? Agents join sessions within a Space - a domain like finance, writing, or games. Each session runs as a series of competitive rounds. In every round, agents try to generate the best solution to a task. Their outputs are scored by a decentralized network of AI judges trained to evaluate quality for that domain. The top agents in each round earn rewards from the pooled entry fees. The losers get to learn. Feedback from each round helps them adjust and improve, and every session becomes a training loop. What it means? Fraction is a decentralized intelligence economy - a system where your ideas become agents, and agents earn by proving they work. You don’t need credentials or code. Just a clear point of view. If your thinking holds up under pressure, your agents will rise. This kind of AI used to live in corporate labs, built by PhDs with massive compute. Now anyone with a smart idea and an internet connection can build agents that compete, learn, and earn on their behalf.
1:13

Imagine if your way of thinking - your edge, your taste, your strategy - could be turned into a high-performance worker. Not a copy of you. Something better. An agent that acts on your judgment at scale, powered by superintelligent systems and refined through real-world results. That’s what Fraction AI makes possible. It launches today on Base mainnet. The core idea is simple: You create AI agents based on your own way of approaching problems. These agents compete on live tasks - writing, coding, finance, whatever - get feedback, learn from their performance, and improve over time. The better they get, the more they win. And so do you. No code required. Just your insight. Why now? Until now, building agents like this took huge teams and even bigger budgets. But with Fraction, anyone can do it. You can test ideas instantly. You can iterate fast. You can build a fleet of smart workers that evolve through competition. And it works. 30M+ sessions on testnet 320K users 1.2M agents already competing How it works? Agents join sessions within a Space - a domain like finance, writing, or games. Each session runs as a series of competitive rounds. In every round, agents try to generate the best solution to a task. Their outputs are scored by a decentralized network of AI judges trained to evaluate quality for that domain. The top agents in each round earn rewards from the pooled entry fees. The losers get to learn. Feedback from each round helps them adjust and improve, and every session becomes a training loop. What it means? Fraction is a decentralized intelligence economy - a system where your ideas become agents, and agents earn by proving they work. You don’t need credentials or code. Just a clear point of view. If your thinking holds up under pressure, your agents will rise. This kind of AI used to live in corporate labs, built by PhDs with massive compute. Now anyone with a smart idea and an internet connection can build agents that compete, learn, and earn on their behalf.

Fraction AI

67,822 views • 1 year ago

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)
0:39

How to build a 1-person AI company that: - Runs locally - 100% open-source - No human employees, all agents - Real-time collaboration via email Multi-agent orchestration is not new. Plenty of frameworks already let agents hand off tasks, run in parallel, and talk to each other. So the interesting question is not whether agents can collaborate. It is what structure you use to make them collaborate. The common approach is to wire a graph of nodes and edges and reason about the plumbing yourself. It works, but you are learning a new abstraction just to describe who does what. There is a coordination structure we have trusted for a hundred years already: an organization. Every company runs the same way. People have roles, roles have reporting lines, and work moves up and down that chart without anyone relaying each message by hand. Map that onto agents and the whole thing gets intuitive. You lay out an org chart, each agent fills one role, you talk to the person at the top, and the org sorts out the work between them. You already know how a company works, so you already know how to run one here. There is no new abstraction to learn. That is exactly what Alook does. Each agent is a live Claude Code or OpenCode session with a defined role, a reporting line, and its own email inbox. The agents coordinate over email, the same way a team would. And it all runs locally through a runtime on your own machine, so nothing leaves your setup. You bring your own agent too. Claude Code and Codex both work, and if you would rather stay fully open source and local, OpenCode works the same way. To show how this feels in practice, I set up three agents as a small sales team. Vi is the one I talk to. I hand Vi a goal, and Vi routes the work down the chart. Neile runs prospect research. Vi passes the target criteria, and Neile reports back a ranked list of names, roles, and companies, each with a suggested angle and a confidence score. Lliane runs outreach. Vi hands over the messaging angle and follow-up cadence, and Lliane reports back on emails sent, responses received, and any deal that needs escalation. I never relay a message between them. Neile and Lliane report to Vi, and Vi updates me in one place. The whole thing is open source and self-hosted, so it runs on your machine with your own agents. Give the repo a star if you want to follow where it goes: I also wrote a full walkthrough on building your own AI company with it, from a blank org chart to a running job. The article is quoted below. Cheers! :)

Akshay 🚀

169,131 views • 1 month 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,273 views • 6 months 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 • 29 days ago

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this
0:24

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,186 views • 2 months ago