Loading video...

Video Failed to Load

Go Home

Shopify CEO Tobi Lütke called Pi "the most interesting agent harness" - a tiny, open-source framework built by a single developer that powers OpenClaw and is changing how builders think about AI agents. In this clip, Dave Killeen (Field CPO at Pendo) breaks down why Pi matters, how it...

aakashgupta's profile picture

Aakash Gupta

331,868 subscribers

10,691 views • 5 days ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

4 Comments

Aakash Gupta's profile picture
Aakash Gupta5 days ago

Full podcast:

Kamal Bisht 🔴 AI Marketer's profile picture
Kamal Bisht 🔴 AI Marketer5 days ago

A single dev building something that gets Tobi Lütke's attention says everything about where agent tooling is heading — the real story is that the barrier to entry just collapsed.

Labangram Photography's profile picture
Labangram Photography4 days ago

Open harness + model orchestration is the real differentiator vs closed stacks. Same models, very different failure modes once routing is yours.

SmoothOpeRAIDER's profile picture
SmoothOpeRAIDER5 days ago

Tell him to stop fucking recommending I watch the Oprah podcast.. Ty.

Related Videos

i tested a fully local ai coding setup: gemma4 from Google DeepMind running through LM Studio, paired with pi which is a minimal open source coding harness this is part 1 of a two part series. here we cover the why and the complete hands-on setup 0:00 - Running a coding agent fully local 0:47 - Why Pi as the coding agent harness 1:39 - Why Gemma 4 and which variant to pick 2:44 - Architecture: Pi, LM Studio and Gemma 4 3:45 - LM Studio setup and model download 5:01 - Starting the local server 5:19 - API sanity check with curl 6:08 - Installing the Pi coding agent 6:20 - Configuring models.json for local models 8:20 - First run: selecting the model in Pi 8:58 - Fixing the context length error 10:16 - Testing the working setup 10:50 - What is coming in Part 2
11:32

i tested a fully local ai coding setup: gemma4 from Google DeepMind running through LM Studio, paired with pi which is a minimal open source coding harness this is part 1 of a two part series. here we cover the why and the complete hands-on setup 0:00 - Running a coding agent fully local 0:47 - Why Pi as the coding agent harness 1:39 - Why Gemma 4 and which variant to pick 2:44 - Architecture: Pi, LM Studio and Gemma 4 3:45 - LM Studio setup and model download 5:01 - Starting the local server 5:19 - API sanity check with curl 6:08 - Installing the Pi coding agent 6:20 - Configuring models.json for local models 8:20 - First run: selecting the model in Pi 8:58 - Fixing the context length error 10:16 - Testing the working setup 10:50 - What is coming in Part 2

Nidhi Singh

16,289 views • 3 months ago

I rebuilt Posia using the Pi Agent SDK. The core agent is ~15 lines of code, and the harness is so flexible and hackable. Recorded a 17-min walkthrough on: - Pi’s extension system + how to build your own - extensions that cut tool tokens by 80–96% - the core Pi SDK, step by step - building hosted agents with it Adding my Pi extensions setup in AI Builder Club repo here:
17:22

I rebuilt Posia using the Pi Agent SDK. The core agent is ~15 lines of code, and the harness is so flexible and hackable. Recorded a 17-min walkthrough on: - Pi’s extension system + how to build your own - extensions that cut tool tokens by 80–96% - the core Pi SDK, step by step - building hosted agents with it Adding my Pi extensions setup in AI Builder Club repo here:

Jason Zhou

66,010 views • 2 months ago

Thrilled to see Amazon Web Services making a major contribution to the open source AI community with the launch of the Strands Agents, an open source AI agents SDK! The core of Strands is the simple agentic loop that connects the model and tools together, like the two strands of DNA. This model-driven approach to agent building eliminates the need for complex agent orchestration by embracing the capabilities of state-of-the-art models to plan, chain thoughts, call tools, and reflect. Providing open source tools and interoperability with open source protocols is an important part of our strategy to enable an agentic future. Can't wait to see what you build with Strands!
1:33

Thrilled to see Amazon Web Services making a major contribution to the open source AI community with the launch of the Strands Agents, an open source AI agents SDK! The core of Strands is the simple agentic loop that connects the model and tools together, like the two strands of DNA. This model-driven approach to agent building eliminates the need for complex agent orchestration by embracing the capabilities of state-of-the-art models to plan, chain thoughts, call tools, and reflect. Providing open source tools and interoperability with open source protocols is an important part of our strategy to enable an agentic future. Can't wait to see what you build with Strands!

Swami Sivasubramanian

32,185 views • 1 year ago

Perplexity CEO Aravind Srinivas on the brutal truth about who actually makes money in AI (and why it's not who you think): Aravind argues that the real value in AI comes from orchestration. He points to products like Codex, Claude Code, and Perplexity Computer: "What is that? It's an orchestration system. It takes a model, pairs it with an agent harness." And what is an agent harness? "The simplest way of describing it is like rules for how the agent loop should run. What are all the skills and sub-agents and connectors and tools it accesses? Without the harness, you don't necessarily capture and convert the intrinsic intelligence in the model into valuable output tokens." This leads to a blunt conclusion about who has a real business in AI, and who doesn't: "If you're literally just a reseller of model tokens, you have no business, because the model will get commoditized. So even if you're a model builder, you don't have a business. As an infra layer, you have some business on serving those output tokens. But as an application layer or model builder, you don't really have a business if you're just a reseller of tokens that come directly out of the model." So where does the value accrue? "You have a business if you know how to take the model, ground it in valuable context, orchestrate it with a really good agent harness, connected to the right set of tools and connectors (whether it's personal connectors or business connectors) and provide the experience to people in one single unified system." Aravind Srinivas then explains Perplexity's specific edge: Beyond orchestrating across tools, files, and connectors, they also orchestrate across models. "That is the differentiation that Anthropic and OpenAI cannot claim, because you wouldn't find GPT-5 inside the Claude Code harness. You wouldn't find Claude Opus inside the Codex harness. These are competing with each other. Whereas you would find both these models inside Perplexity Computer." Why does this matter? Because it all comes down to power. In Aravind's framing, the fundamental cost driver in AI is watts (the one input nobody can subsidize except the government). "Whoever provides the most valuable output tokens with the least amount of power expended to produce them generates the greatest value to the end user, has the most pricing power, has the most value. That is the orchestration problem to solve." His conclusion: "The one single most important metric in AI is token value per watt per user."
2:50

Perplexity CEO Aravind Srinivas on the brutal truth about who actually makes money in AI (and why it's not who you think): Aravind argues that the real value in AI comes from orchestration. He points to products like Codex, Claude Code, and Perplexity Computer: "What is that? It's an orchestration system. It takes a model, pairs it with an agent harness." And what is an agent harness? "The simplest way of describing it is like rules for how the agent loop should run. What are all the skills and sub-agents and connectors and tools it accesses? Without the harness, you don't necessarily capture and convert the intrinsic intelligence in the model into valuable output tokens." This leads to a blunt conclusion about who has a real business in AI, and who doesn't: "If you're literally just a reseller of model tokens, you have no business, because the model will get commoditized. So even if you're a model builder, you don't have a business. As an infra layer, you have some business on serving those output tokens. But as an application layer or model builder, you don't really have a business if you're just a reseller of tokens that come directly out of the model." So where does the value accrue? "You have a business if you know how to take the model, ground it in valuable context, orchestrate it with a really good agent harness, connected to the right set of tools and connectors (whether it's personal connectors or business connectors) and provide the experience to people in one single unified system." Aravind Srinivas then explains Perplexity's specific edge: Beyond orchestrating across tools, files, and connectors, they also orchestrate across models. "That is the differentiation that Anthropic and OpenAI cannot claim, because you wouldn't find GPT-5 inside the Claude Code harness. You wouldn't find Claude Opus inside the Codex harness. These are competing with each other. Whereas you would find both these models inside Perplexity Computer." Why does this matter? Because it all comes down to power. In Aravind's framing, the fundamental cost driver in AI is watts (the one input nobody can subsidize except the government). "Whoever provides the most valuable output tokens with the least amount of power expended to produce them generates the greatest value to the end user, has the most pricing power, has the most value. That is the orchestration problem to solve." His conclusion: "The one single most important metric in AI is token value per watt per user."

Big Brain AI

42,319 views • 1 month ago

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11
43:20

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper

66,840 views • 4 months ago

Ex-Google engineer just compressed the shift from AI agents to "graphs" and "loops" into one 2h47m lecture: • 00:00 - understanding the different layers of AI memory • 30:00 - moving from simple LLM calls to AI agents • 50:00 - why agent systems are becoming a graph engineering problem • 1:12:00 - connecting context, tools and agent state • 1:24:00 - building a minimal agent harness from scratch • 1:46:00 - breaking down the architecture behind Hermes Agent • 2:08:00 - turning agent concepts into working systems 167-minute deep dive, and one of the clearest ways to understand how AI engineering is moving beyond prompts The progression: Prompt → Context → Memory → Agent → Loop → Graph → Agent Harness Watch it today, then read the full roadmap below
2:47:42

Ex-Google engineer just compressed the shift from AI agents to "graphs" and "loops" into one 2h47m lecture: • 00:00 - understanding the different layers of AI memory • 30:00 - moving from simple LLM calls to AI agents • 50:00 - why agent systems are becoming a graph engineering problem • 1:12:00 - connecting context, tools and agent state • 1:24:00 - building a minimal agent harness from scratch • 1:46:00 - breaking down the architecture behind Hermes Agent • 2:08:00 - turning agent concepts into working systems 167-minute deep dive, and one of the clearest ways to understand how AI engineering is moving beyond prompts The progression: Prompt → Context → Memory → Agent → Loop → Graph → Agent Harness Watch it today, then read the full roadmap below

Morlex

51,558 views • 1 month ago

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

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

Himanshu Kumar

228,994 views • 4 months ago

We're entering a new era of software where a single person, working with AI agents, can build products that previously required entire teams. In this episode of the Lightcone Podcast, they break down the rise of AI coding agents, "tokenmaxxing", and the emerging workflows behind tools like Claude Code and OpenClaw. They discuss why AI systems today feel less like productivity tools and more like collaborators, why the future of AI should be personal and user-controlled, and how founders are starting to build software in completely new ways. 00:00 — Will you control your AI? 00:47 — Coding again after 13 years 01:56 — Rebuilding a startup with Claude Code 05:50 — Software that thinks like a journalist 07:09 — The rise of “tokenmaxxing” 10:07 — The accidental creation of GStack 14:21 — The workflow behind 400x output 20:59 — Thin Harness, Fat Skills 24:35 — AI agents are like Ferraris 27:12 — The future of personal AI 38:37 — Buying back time with tokens
41:29

We're entering a new era of software where a single person, working with AI agents, can build products that previously required entire teams. In this episode of the Lightcone Podcast, they break down the rise of AI coding agents, "tokenmaxxing", and the emerging workflows behind tools like Claude Code and OpenClaw. They discuss why AI systems today feel less like productivity tools and more like collaborators, why the future of AI should be personal and user-controlled, and how founders are starting to build software in completely new ways. 00:00 — Will you control your AI? 00:47 — Coding again after 13 years 01:56 — Rebuilding a startup with Claude Code 05:50 — Software that thinks like a journalist 07:09 — The rise of “tokenmaxxing” 10:07 — The accidental creation of GStack 14:21 — The workflow behind 400x output 20:59 — Thin Harness, Fat Skills 24:35 — AI agents are like Ferraris 27:12 — The future of personal AI 38:37 — Buying back time with tokens

Y Combinator

67,145 views • 4 months ago

🔥 🤖 🕵️‍♂️ INTRODUCING: Meta Agent 💥 this is by far the most exciting thing I've created using AI!!! >>> made using Manus and @windsurf 🔑 Meta Agent is an AI agent that uses the OpenAI Agents SDK to GENERATE NEW AGENTS you simply tell Meta Agent in natural language the agent you want... 🤯 and Meta Agent generates it for you fully open --> link to GitHub and example walkthrough below ⬇️
1:11

🔥 🤖 🕵️‍♂️ INTRODUCING: Meta Agent 💥 this is by far the most exciting thing I've created using AI!!! >>> made using Manus and @windsurf 🔑 Meta Agent is an AI agent that uses the OpenAI Agents SDK to GENERATE NEW AGENTS you simply tell Meta Agent in natural language the agent you want... 🤯 and Meta Agent generates it for you fully open --> link to GitHub and example walkthrough below ⬇️

Dan McAteer

153,982 views • 1 year ago

The next billion-dollar AI companies won’t be built around an LLM. They’ll be built around the HARNESS. Everyone is asking: “Which AI model should I use?” I think that’s the wrong question. An LLM is like a wild black stallion—immensely powerful, constantly improving, but running free. The opportunity is building the harness that lets you control that power and actually win the horse race. Your AI application shouldn’t be the model. It should orchestrate models. Claude today. GPT tomorrow. Gemini, Grok, Qwen, or whatever comes next. Swap the engine without rebuilding the car. Crypto already taught us this lesson. People interact with things like USDC and Tether without caring nearly as much which underlying blockchain happens to settle the transaction. The application layer abstracts the infrastructure. AI is heading the same direction. LLMs are infrastructure. The harness is the product. The winners will build AI harnesses around real human problems—businesses, workflows, coding, research, finance, education, everyday life—and make the underlying intelligence interchangeable. Everyone is trying to capture this incredibly powerful new thing called AI. Stop trying to build a better horse. Build the harness that lets you ride any horse. 🐎🤖 I just made a video explaining why I think this is where some of the biggest opportunities in AI are hiding.
4:58

The next billion-dollar AI companies won’t be built around an LLM. They’ll be built around the HARNESS. Everyone is asking: “Which AI model should I use?” I think that’s the wrong question. An LLM is like a wild black stallion—immensely powerful, constantly improving, but running free. The opportunity is building the harness that lets you control that power and actually win the horse race. Your AI application shouldn’t be the model. It should orchestrate models. Claude today. GPT tomorrow. Gemini, Grok, Qwen, or whatever comes next. Swap the engine without rebuilding the car. Crypto already taught us this lesson. People interact with things like USDC and Tether without caring nearly as much which underlying blockchain happens to settle the transaction. The application layer abstracts the infrastructure. AI is heading the same direction. LLMs are infrastructure. The harness is the product. The winners will build AI harnesses around real human problems—businesses, workflows, coding, research, finance, education, everyday life—and make the underlying intelligence interchangeable. Everyone is trying to capture this incredibly powerful new thing called AI. Stop trying to build a better horse. Build the harness that lets you ride any horse. 🐎🤖 I just made a video explaining why I think this is where some of the biggest opportunities in AI are hiding.

Jared Tate ©️

10,118 views • 1 month ago

Peak AI: Never play Minecraft alone again Steve is an open-source Minecraft mod that brings LLM-powered AI agents (Groq, OpenAI, Gemini) directly into the game. Instead of helping you write code, these agents play alongside you - mining, building, exploring, and fighting through natural language commands. You type things like “mine some iron” or “build a house”, and the agent understands the context, plans a sequence of actions, and executes them autonomously. Source: YuvDwi Github (link in comments)
0:57

Peak AI: Never play Minecraft alone again Steve is an open-source Minecraft mod that brings LLM-powered AI agents (Groq, OpenAI, Gemini) directly into the game. Instead of helping you write code, these agents play alongside you - mining, building, exploring, and fighting through natural language commands. You type things like “mine some iron” or “build a house”, and the agent understands the context, plans a sequence of actions, and executes them autonomously. Source: YuvDwi Github (link in comments)

Chubby♨️

484,251 views • 10 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

Anthropic AI Engineer: "The fastest way to make an agent better isn't a smarter model. It's the right Loop and Graph around it." In 17 minutes he breaks down what agentic engineering looks like at Anthropic, and why it's nothing like what most people imagine. Watch it, then save the full guide on loops and graphs below
17:13

Anthropic AI Engineer: "The fastest way to make an agent better isn't a smarter model. It's the right Loop and Graph around it." In 17 minutes he breaks down what agentic engineering looks like at Anthropic, and why it's nothing like what most people imagine. Watch it, then save the full guide on loops and graphs below

CyrilXBT

10,691 views • 22 days ago

AI INTERVIEW: OPENAI'S SECRET WEAPON AI agents are no longer just hype—they're here to revolutionize automation, Web3, and beyond. SwarmNode.ai is building a serverless AI agent platform for scalability, efficiency, and real-world impact. In this exclusive interview, he reveals how AI swarms can outperform single models, why OpenAI’s Operator is just the beginning, and how crypto is fueling AI innovation. Plus, he breaks down DeepSeek’s game-changing AI breakthrough, the future of agent monetization, and why serverless AI could be the next frontier in automation. 01:37 – From Engineering to AI: The journey into artificial intelligence. 02:43 – The GPT-3 Moment: How OpenAI’s tech pulled him in. 04:10 – AI’s Biggest Challenge: Why real-world use cases lag behind. 05:05 – OpenAI’s Operator: Why it’s “rudimentary” (for now). 06:25 – Crypto & AI: How tokens help bootstrap AI startups. 08:15 – Can You Bootstrap a Startup with a Token? The trade-offs. 09:56 – 90% of AI Token Holders Don’t Use the Product—Does It Matter? 11:18 – What is SwarmNode?: AI agents, hosted serverlessly. 14:23 – AI Swarms: Why multiple agents outperform single models. 16:08 – What is a Swarm? A simple definition of collaborative AI. 17:32 – “How Can I Make Money with AI?”: Real-world use cases. 18:41 – AI Bounties: Hiring devs to build your custom agent. 20:50 – The Future of AI Marketplaces: Monetizing pre-built agents. 23:15 – DeepSeek’s Disruption: Why it’s good news for AI. 24:46 – Is SwarmNode Compatible with DeepSeek? How it integrates. 26:17 – SwarmNode vs. AI Launchpads: What makes it different? 27:42 – Why Serverless Matters: Cost savings & efficiency. 29:53 – AI Agents in the Real World: Booking flights, managing workflows, and more. 31:11 – Building SwarmNode for Developers: Why it started as a personal project. 32:27 – Explosive Growth: 200,000 AI agent executions in 5 weeks. 34:41 – Why SwarmNode Agents Aren’t Visible on 𝕏 Yet. 36:46 – Startup Hiring Lessons: Finding top AI talent. 39:15 – Why SwarmNode is Built in Python (and What’s Next). 40:32 – Scaling AI Workloads: Handling traffic surges. 41:42 – AWS & Cost Challenges: The biggest monetization hurdle. 42:58 – 2025: The Year of Mass AI Adoption. 45:22 – Should We Be Worried About AI’s Rapid Growth? 46:46 – The Most Underrated AI Tools Right Now. 47:34 – What’s Next for SwarmNode?: Making AI accessible to everyone.
49:12

AI INTERVIEW: OPENAI'S SECRET WEAPON AI agents are no longer just hype—they're here to revolutionize automation, Web3, and beyond. SwarmNode.ai is building a serverless AI agent platform for scalability, efficiency, and real-world impact. In this exclusive interview, he reveals how AI swarms can outperform single models, why OpenAI’s Operator is just the beginning, and how crypto is fueling AI innovation. Plus, he breaks down DeepSeek’s game-changing AI breakthrough, the future of agent monetization, and why serverless AI could be the next frontier in automation. 01:37 – From Engineering to AI: The journey into artificial intelligence. 02:43 – The GPT-3 Moment: How OpenAI’s tech pulled him in. 04:10 – AI’s Biggest Challenge: Why real-world use cases lag behind. 05:05 – OpenAI’s Operator: Why it’s “rudimentary” (for now). 06:25 – Crypto & AI: How tokens help bootstrap AI startups. 08:15 – Can You Bootstrap a Startup with a Token? The trade-offs. 09:56 – 90% of AI Token Holders Don’t Use the Product—Does It Matter? 11:18 – What is SwarmNode?: AI agents, hosted serverlessly. 14:23 – AI Swarms: Why multiple agents outperform single models. 16:08 – What is a Swarm? A simple definition of collaborative AI. 17:32 – “How Can I Make Money with AI?”: Real-world use cases. 18:41 – AI Bounties: Hiring devs to build your custom agent. 20:50 – The Future of AI Marketplaces: Monetizing pre-built agents. 23:15 – DeepSeek’s Disruption: Why it’s good news for AI. 24:46 – Is SwarmNode Compatible with DeepSeek? How it integrates. 26:17 – SwarmNode vs. AI Launchpads: What makes it different? 27:42 – Why Serverless Matters: Cost savings & efficiency. 29:53 – AI Agents in the Real World: Booking flights, managing workflows, and more. 31:11 – Building SwarmNode for Developers: Why it started as a personal project. 32:27 – Explosive Growth: 200,000 AI agent executions in 5 weeks. 34:41 – Why SwarmNode Agents Aren’t Visible on 𝕏 Yet. 36:46 – Startup Hiring Lessons: Finding top AI talent. 39:15 – Why SwarmNode is Built in Python (and What’s Next). 40:32 – Scaling AI Workloads: Handling traffic surges. 41:42 – AWS & Cost Challenges: The biggest monetization hurdle. 42:58 – 2025: The Year of Mass AI Adoption. 45:22 – Should We Be Worried About AI’s Rapid Growth? 46:46 – The Most Underrated AI Tools Right Now. 47:34 – What’s Next for SwarmNode?: Making AI accessible to everyone.

Mario Nawfal

338,311 views • 1 year ago

🎉Introducing PyFlue: The Python-Native Agent Harness Framework.🧰 💡Flue for Python: Fred K. Schott fks CEO of HTML has launched Flue: The Agent Harness Framework for TypeScript. It brings programmable harness right into your agents rather than DIY plumbing. Python ecosystem already has 🦾 powerful AI/ML tools and frameworks and research initiatives but most frameworks asked users to build your own harness. Superagentic AI bringing this concept of Flue to Python 🐍 ecosystem. Here is PyFlue even even better 🤖 Agent = Model 💻 + Harness 🧰 + Memory 🧠 Almost all the feature of Flue plugged with LangChain Deepagents harness built by Harrison Chase and team Viv Sydney Runkle and more coming soon. 👉 Stop building agent loops, start using a harness. 💻 Try PyFlue Now : ⭐️ GitHub: 📚Docs: 📙 Blog Post: #HarnessEngineering #AgentHarnesses
0:39

🎉Introducing PyFlue: The Python-Native Agent Harness Framework.🧰 💡Flue for Python: Fred K. Schott fks CEO of HTML has launched Flue: The Agent Harness Framework for TypeScript. It brings programmable harness right into your agents rather than DIY plumbing. Python ecosystem already has 🦾 powerful AI/ML tools and frameworks and research initiatives but most frameworks asked users to build your own harness. Superagentic AI bringing this concept of Flue to Python 🐍 ecosystem. Here is PyFlue even even better 🤖 Agent = Model 💻 + Harness 🧰 + Memory 🧠 Almost all the feature of Flue plugged with LangChain Deepagents harness built by Harrison Chase and team Viv Sydney Runkle and more coming soon. 👉 Stop building agent loops, start using a harness. 💻 Try PyFlue Now : ⭐️ GitHub: 📚Docs: 📙 Blog Post: #HarnessEngineering #AgentHarnesses

Shashi

69,884 views • 4 months ago

The most interesting thing in tech: Everyone in Davos is talking about geopolitics and the growing antagonism between the US and Europe. But geopolitics are sometimes downstream of tech. And one thing that Europe could do is build its own open-source AI models. Eric Schmidt explains why that matters and how it could be done. #WEF26 #WEF2026
2:33

The most interesting thing in tech: Everyone in Davos is talking about geopolitics and the growing antagonism between the US and Europe. But geopolitics are sometimes downstream of tech. And one thing that Europe could do is build its own open-source AI models. Eric Schmidt explains why that matters and how it could be done. #WEF26 #WEF2026

nxthompson

11,750 views • 7 months ago

Introducing Helmor The open-source, local-first answer to Conductor. A more refined, faster GUI for orchestrating coding agents. No cloud. One-click import from Conductor. AI made coding faster. Helmor is about finishing the rest of the loop: orchestration, workspaces, review, testing, and merge. We believe the next generation of GUI agent orchestration should be built in the open — by the community.
0:53

Introducing Helmor The open-source, local-first answer to Conductor. A more refined, faster GUI for orchestrating coding agents. No cloud. One-click import from Conductor. AI made coding faster. Helmor is about finishing the rest of the loop: orchestration, workspaces, review, testing, and merge. We believe the next generation of GUI agent orchestration should be built in the open — by the community.

Caspian 東澔

122,799 views • 4 months ago