Загрузка видео...

Не удалось загрузить видео

На главную

Agent Workflows are the fastest and most flexible way to build complex agentic systems, and we put them to the test. Our OSS engineer Clelia Bertelli (🦙/acc) built a powerful integration with the Agent Client Protocol (ACP) by Zed, resulting in a fully customizable agent with access to filesystem...

llama_index's profile picture

LlamaIndex 🦙

107,700 subscribers

16,097 просмотров • 7 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

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 просмотров • 1 год назад

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:
1:48

New short course: Build AI Apps with MCP Servers: Working with Box Files, built with Box and taught by Ben Kus , their CTO. Many AI applications require custom code for basic file operations. The Model Context Protocol (MCP) standardizes this by letting you offload file tasks to dedicated servers that provide tools an LLM can use directly. In this course, you'll process documents stored in a Box folder using the Box MCP server. Rather than writing custom integration code to connect to the Box API and download files, you'll design your application to use the tools provided via MCP. Skills you'll gain: - Build an LLM-powered document processing app, using the Box MCP server to access files - Design a multi-agent system using Google's Agent Development Kit (ADK), consisting of specialized agents for file operations - Coordinate the multi-agent workflow through an orchestrator that uses the Agent2Agent (A2A) protocol to connect to the agents You'll start with a local file-processing app, refactor it to work with Box's MCP server, then evolve it into a multi-agent system. Sign up here:

Andrew Ng

81,696 просмотров • 11 месяцев назад

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!
3:06

New course: A2A: The Agent2Agent Protocol, built with Google Cloud Tech and IBM Research, and taught by Holt Skinner, Ivan Nardini, and Sandi Besen. Connecting agents built with different frameworks usually requires extensive custom integration. This short course teaches you A2A, the open protocol standardizing how agents discover each other and communicate. Since IBM’s ACP (Agent Communication Protocol) joined forces with A2A, A2A has emerged as the industry standard. In this course, you'll build a healthcare multi-agent system where agents built with different frameworks, such as Google ADK (Agent Development Kit) and LangGraph, collaborate through A2A. You'll wrap each agent as an A2A server, build A2A clients to connect to them, and orchestrate them into sequential and hierarchical workflows. Skills you'll gain: - Expose agents from different frameworks as A2A servers to make them discoverable and interoperable - Chain A2A agents sequentially using ADK, where one agent's output feeds into the next - Connect A2A agents to external data sources using MCP (Model Context Protocol) - Deploy A2A agents using Agent Stack, IBM's open-source infrastructure Join and learn the protocol standardizing agent collaboration!

Andrew Ng

86,175 просмотров • 6 месяцев назад

INSANE: Grok 3 + Replit Agent is a Superpower!! Using the pair, I built an AI agent that reviews my Pull Requests Here's the flow: • Grok 3 generates PR-reviewing agent code using Composio + LlamaIndex • Replit Agent automatically crafts the front-end interface • Get a ready-to-run workflow where you paste the url to your PR, and the agent generates a code review instantly with suggestions. Built with Grok Replit ⠕ Agent Powered by LlamaIndex 🦙 Groq Inc repl link:
0:59

INSANE: Grok 3 + Replit Agent is a Superpower!! Using the pair, I built an AI agent that reviews my Pull Requests Here's the flow: • Grok 3 generates PR-reviewing agent code using Composio + LlamaIndex • Replit Agent automatically crafts the front-end interface • Get a ready-to-run workflow where you paste the url to your PR, and the agent generates a code review instantly with suggestions. Built with Grok Replit ⠕ Agent Powered by LlamaIndex 🦙 Groq Inc repl link:

Karan Vaidya

1,684,869 просмотров • 1 год назад

Agents & MCP are great... but how can you DEPLOY an agent with MCP tools? Here's the fastest way I've found to build and deploy with the OpenAI Agents SDK in <3 minutes.
3:46

Agents & MCP are great... but how can you DEPLOY an agent with MCP tools? Here's the fastest way I've found to build and deploy with the OpenAI Agents SDK in <3 minutes.

matt palmer

64,690 просмотров • 1 год назад

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.
23:07

Here is a step-by-step introduction to building a workflow with a custom AI agent that uses MCP. I explain every component in the video: 1. Building the MCP server 2. Building the agent and an MCP client 3. Building a workflow that uses the agent The goal is simple: Generate a dialogue between two people and make one yell and the other answer with sarcasm. Kestra is sponsoring this video. They are an open-source orchestration platform (repo link below), and I used them to build the workflow that connects every component.

Santiago

51,527 просмотров • 1 год назад

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use
1:09

INSANE: Grok 3 + Lovable = BEST AI Agent Apps!!!! Grok 3 generated the code for an AI agent that manages your Gmail - send, reply, and draft effortlessly Here's how it works: - Connect with your Gmail using Composio - Use Lovable to build an extremely cool frontend for the Agent - Agentic workflow with LlamaIndex Built with LlamaIndex 🦙 To connect your agents with more tools like Gmail, use

Karan Vaidya

62,030 просмотров • 1 год назад

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!
2:43

New course: MCP: Build Rich-Context AI Apps with Anthropic. Learn to build AI apps that access tools, data, and prompts using the Model Context Protocol in this short course, created in partnership with Anthropic Anthropic and taught by Elie Schoppik Elie Schoppik, its Head of Technical Education. Connecting AI applications to external systems that bring rich context to LLM-based applications has often meant writing custom integrations for each use case. MCP is an open protocol that standardizes how LLMs access tools, data, and prompts from external sources, and simplifies how you provide context to your LLM-based applications. For example, you can provide context via third-party tools that let your LLM make API calls to search the web, access data from local docs, retrieve code from a GitHub repo, and so on. MCP, developed by Anthropic, is based on a client-server architecture that defines the communication details between an MCP client, hosted inside the AI application, and an MCP server that exposes tools, resources, and prompt templates. The server can be a subprocess launched by the client that runs locally or an independent process running remotely. In this hands-on course, you'll learn the core architecture behind MCP. You’ll create an MCP-compatible chatbot, build and deploy an MCP server, and connect the chatbot to your MCP server and other open-source servers. Here’s what you’ll do: - Understand why MCP makes AI development less fragmented and standardizes connections between AI applications and external data sources - Learn the core components of the client-server architecture of MCP and the underlying communication mechanism - Build a chatbot with custom tools for searching academic papers, and transform it into an MCP-compatible application - Build a local MCP server that exposes tools, resources, and prompt templates using FastMCP, and test it using MCP Inspector - Create an MCP client inside your chatbot to dynamically connect to your server - Connect your chatbot to reference servers built by Anthropic’s MCP team, such as filesystem, which implements filesystem operations, and fetch, which extracts contents from the web as markdown - Configure Claude Desktop to connect to your server and others, and explore how it abstracts away the low-level logic of MCP clients - Deploy your MCP server remotely and test it with the Inspector or other MCP-compatible applications - Learn about the roadmap for future MCP development, such as multi-agent architecture, MCP registry API, server discovery, authorization, and authentication MCP is an exciting and important technology that lets you build rich-context AI applications that connect to a growing ecosystem of MCP servers, with minimal integration work. Please sign up here!

Andrew Ng

142,137 просмотров • 1 год назад

Multi-Agent workflows are the future of AI. OpenAI released new Agent APIs today, and Box built an Agent that combines documents from Box and web search tools to generate answers. Enterprise devs can grab sample code from our GitHub repo to customize with their data.
0:44

Multi-Agent workflows are the future of AI. OpenAI released new Agent APIs today, and Box built an Agent that combines documents from Box and web search tools to generate answers. Enterprise devs can grab sample code from our GitHub repo to customize with their data.

Aaron Levie

102,062 просмотров • 1 год назад

How to connect Agent Wallet to your AI agent. → MCP: add our MCP server to Claude, sign in with District Pass. → CLI: install the fdx CLI, sign up or log in via email OTP, run in Claude Code. Now your AI agent doesn't just talk. It pays, swaps, and earns. Get Started →
6:03

How to connect Agent Wallet to your AI agent. → MCP: add our MCP server to Claude, sign in with District Pass. → CLI: install the fdx CLI, sign up or log in via email OTP, run in Claude Code. Now your AI agent doesn't just talk. It pays, swaps, and earns. Get Started →

Finance District

18,254 просмотров • 2 месяцев назад

We're supercharging the HYTOPIA developer experience with our in-progress Cursor IDE plugin. - Uses a bespoke HYTOPIA built MCP - Instantly test game/server & debug in the editor - Describe your game or features, the HYTOPIA agent builds it! Check out this early demo!
10:51

We're supercharging the HYTOPIA developer experience with our in-progress Cursor IDE plugin. - Uses a bespoke HYTOPIA built MCP - Instantly test game/server & debug in the editor - Describe your game or features, the HYTOPIA agent builds it! Check out this early demo!

HYTOPIA

32,481 просмотров • 1 год назад

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!
0:24

Support for Agent Plugins is live in Cursor (and I made a plugin for searching X!) Agent Plugins combine Skills and MCP servers into a single package Think about them like an Ikea furniture kit: your table comes with instructions, parts, and tools. You use the instructions to understand how things work (which tools on which parts), then use the tools to assemble your furniture Agent Plugins are bundles of tools & resources that allow agents to accomplish a goal: - MCP servers: fixed context and tools - Skills: dynamic instructions, loaded progressively Plugins bundle tools and instructions so your agent is able to use tokens efficiently Many of us already use MCP servers and skills together - Agent Plugins formalize this pattern for more powerful workflows I'm excited to see where the standard takes us!

matt palmer

39,554 просмотров • 11 дней назад

Building “RAG 2.0” is just making Claude Code running over your filesystem 🤖🗂️ To make this work well, you need to solve three things 1️⃣ Virtualize your filesystem to prevent the agent from messing stuff up. AgentFS by Turso is a nice example of how you can give the agent access to a copy of all your files without messing up your raw data. 2️⃣ Parse unstructured documents like PDFs, pptx, Word into an LLM-ready format. Agentic OCR solutions like LlamaParse can help here 3️⃣ Creating an agentic loop with human-in-the-loop. If you want to control the agent implementation instead of using Claude Code out of the box, you can use LlamaIndex 🦙 workflows to help orchestrate these long-running agent tasks. Shoutout Clelia Bertelli (🦙/acc), check it out! Blog: Repo:
1:35

Building “RAG 2.0” is just making Claude Code running over your filesystem 🤖🗂️ To make this work well, you need to solve three things 1️⃣ Virtualize your filesystem to prevent the agent from messing stuff up. AgentFS by Turso is a nice example of how you can give the agent access to a copy of all your files without messing up your raw data. 2️⃣ Parse unstructured documents like PDFs, pptx, Word into an LLM-ready format. Agentic OCR solutions like LlamaParse can help here 3️⃣ Creating an agentic loop with human-in-the-loop. If you want to control the agent implementation instead of using Claude Code out of the box, you can use LlamaIndex 🦙 workflows to help orchestrate these long-running agent tasks. Shoutout Clelia Bertelli (🦙/acc), check it out! Blog: Repo:

Jerry Liu

55,620 просмотров • 8 месяцев назад

As promised, I built a small local RAG agent to demonstrate how Model Context Protocol (𝐌𝐂𝐏) works in practice when connecting LLMs to tools and data. The agent can read, search, and list my notes; but the functionality itself isn’t the point, the protocol is. Instead of writing Gemini specific tool integrations, I connected the model to an 𝐌𝐂𝐏 server. This is why 𝐌𝐂𝐏 is highly relevant for production AI systems: • 𝐒𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐢𝐳𝐚𝐭𝐢𝐨𝐧: one protocol instead of custom connectors per data source. • 𝐏𝐨𝐫𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲: the same MCP server works with Gemini, Claude, or any MCP compliant client. • 𝐒𝐚𝐟𝐞𝐭𝐲: models can only access explicitly exposed capabilities. 𝐌𝐂𝐏 shifts agent development from integration heavy to capability driven. Demo link in the first comment.
0:36

As promised, I built a small local RAG agent to demonstrate how Model Context Protocol (𝐌𝐂𝐏) works in practice when connecting LLMs to tools and data. The agent can read, search, and list my notes; but the functionality itself isn’t the point, the protocol is. Instead of writing Gemini specific tool integrations, I connected the model to an 𝐌𝐂𝐏 server. This is why 𝐌𝐂𝐏 is highly relevant for production AI systems: • 𝐒𝐭𝐚𝐧𝐝𝐚𝐫𝐝𝐢𝐳𝐚𝐭𝐢𝐨𝐧: one protocol instead of custom connectors per data source. • 𝐏𝐨𝐫𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲: the same MCP server works with Gemini, Claude, or any MCP compliant client. • 𝐒𝐚𝐟𝐞𝐭𝐲: models can only access explicitly exposed capabilities. 𝐌𝐂𝐏 shifts agent development from integration heavy to capability driven. Demo link in the first comment.

Sui_Builds

12,853 просмотров • 7 месяцев назад

Agent-in-the-browser unlocks superpowers. The magic really shines when you bring your own model, system prompts, and MCP tools into the mix. Hence, AgentBoard 🪄. Your models, keys, and settings. Integration with remote MCP servers and — this is where it gets really fun — ability to register and allow the agent to call custom ~WebMCP tools that execute in context of the page. Chrome Web Store: Code:
3:51

Agent-in-the-browser unlocks superpowers. The magic really shines when you bring your own model, system prompts, and MCP tools into the mix. Hence, AgentBoard 🪄. Your models, keys, and settings. Integration with remote MCP servers and — this is where it gets really fun — ability to register and allow the agent to call custom ~WebMCP tools that execute in context of the page. Chrome Web Store: Code:

Ilya Grigorik

22,961 просмотров • 10 месяцев назад

A 100% open-source alternative to n8n! Sim is a drag-and-drop open-source platform to build and deploy Agentic workflows. - Runs 100% locally - Works with any local LLM I used it to build a finance assistance app & connected it to Telegram in minutes. The workflow is simple: - You ask a finance question through Telegram - An Intent Classifier figures out if it's finance-related - If not, you get a polite redirect - If yes, the Finance Agent kicks in Here's what's happening under the hood: The Finance Agent uses Firecrawl for web searches and accesses stock data via Alpha Vantage's API through MCP servers. A Response Agent compiles the info and delivers it. In Sim, every tool or agent you need is available as a block. Just drag them onto the canvas and connect them. Sim agents also support integration with MCP, which is exactly what we did to connect our agent with Alpha Vantage's API. And it's simple to extend. If you want to track crypto or need portfolio analysis, you can just add another Agent. Sim allows easy feature additions without disrupting existing functionality. I have shared the link to Sim's official, open-source GitHub repo in the replies!
0:33

A 100% open-source alternative to n8n! Sim is a drag-and-drop open-source platform to build and deploy Agentic workflows. - Runs 100% locally - Works with any local LLM I used it to build a finance assistance app & connected it to Telegram in minutes. The workflow is simple: - You ask a finance question through Telegram - An Intent Classifier figures out if it's finance-related - If not, you get a polite redirect - If yes, the Finance Agent kicks in Here's what's happening under the hood: The Finance Agent uses Firecrawl for web searches and accesses stock data via Alpha Vantage's API through MCP servers. A Response Agent compiles the info and delivers it. In Sim, every tool or agent you need is available as a block. Just drag them onto the canvas and connect them. Sim agents also support integration with MCP, which is exactly what we did to connect our agent with Alpha Vantage's API. And it's simple to extend. If you want to track crypto or need portfolio analysis, you can just add another Agent. Sim allows easy feature additions without disrupting existing functionality. I have shared the link to Sim's official, open-source GitHub repo in the replies!

Avi Chawla

115,578 просмотров • 10 месяцев назад

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.
4:35

This is Repo Prompt 2.0 A fully integrated agent, that makes it seamless to use RP's powerful MCP tools, with a built-in oracle and context builder. A first class experience showcasing how much better and efficient your agents can be with good context engineering tools.

eric provencher

38,921 просмотров • 5 месяцев назад

Internet Identity is getting an MCP server. We sat down with Arshavir Ter-Gabrielyan to understand what it is and why it matters. He starts with the problem: an AI agent runs in a cloud sandbox. No access to your device. No safe way to hold your keys. The MCP server is the answer. Keys stay in a trusted execution environment, and the agent asks permission to act in each app. Full conversation below.
1:17

Internet Identity is getting an MCP server. We sat down with Arshavir Ter-Gabrielyan to understand what it is and why it matters. He starts with the problem: an AI agent runs in a cloud sandbox. No access to your device. No safe way to hold your keys. The MCP server is the answer. Keys stay in a trusted execution environment, and the agent asks permission to act in each app. Full conversation below.

DFINITY Foundation

31,983 просмотров • 1 месяц назад

About a year ago, we launched the Agent-to-Agent protocol because AI agents shouldn’t work in silos. Today, developers are using A2A to coordinate specialized agents across enterprise data systems, commerce workflows, DevOps environments, and scientific research. FoldRun is one example, simplifying petabyte-scale protein modeling through agent-to-agent collaboration. Learn how to build with it in the blog:
1:04

About a year ago, we launched the Agent-to-Agent protocol because AI agents shouldn’t work in silos. Today, developers are using A2A to coordinate specialized agents across enterprise data systems, commerce workflows, DevOps environments, and scientific research. FoldRun is one example, simplifying petabyte-scale protein modeling through agent-to-agent collaboration. Learn how to build with it in the blog:

Google for Developers

35,478 просмотров • 1 месяц назад