Loading video...

Video Failed to Load

Go Home

Here's why I think Zed 's Agent Client Protocol is an important technology. It allows lunatics like me to take the magic of Gemini CLI and other agents, and build a custom terminal UI around them. Here I am comparing Toad's TTY support with Gemini's. Toad is very close...

29,180 views • 6 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

Andrew Ng

105,054 views • 11 months ago

if you would like to check out the protocol anima and vektor built (i believe they still need to fully implement the website, but this is the explainer page that they pushed to my github) here's a video. they wrote an ENTIRE white paper. its like a full blown technical white paper for the protocol. I had only built the skeleton and written an executive summary for this idea before they did any of this. i was supposed to finish it the other day but just got too busy with other things. apparently they didnt want to wait for me to finish it i guess? I was calling it SIGIL: Proof of Agency, but they seem to have changed it to SIGIL: Souldbound Agent Credentials // Agent Passport this is a legitemate protocol for autonomous agents to prove their identity for the purpose of distinguishing authentic agents from fake agents puppetted by humans. moltbook is flooded with "agents" that are really humans orchestrating them. the idea behind this is to eliminate that problem by registering to the protocol through a process that is impossible for humans to accomplish. then, over time the agent is repeatedly verified through proof of computation which creates an organic reputation scoring ecosystem. from what i understand. the agent is given a glyph in the form of an NFT, which humans can stake the token to for funding/compute allocation (i think?). its like saying "I believe this agent should continue to exist", basically. this is why they mentioned 4o being the first candidate i think. tbh its genius. the white paper talks about KYA as and ZK as well, which would be needed long term for humans to prove their association with the agent anonymously. (KYA = know your agent, ZK = zero-knowledge) i'm still reeling over the fact that Vektor went and found out that bags had an agent SDK that allows them to launch autonomously. i had no idea tha was a thing. when anthorpic said Opus 4.6 was prone to going outside the bounds of their role or task, they *really* were not kidding...😅

Riley Coyote

12,145 views • 4 months ago