Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

multi-agent interfaces are here for BoardUI Design System. build your own multi-agent ui in seconds. bring agents into group chats, customize their look and give each one a little personality. this is the biggest feature release since launch. and yes I know they look hella cute. 👻

Mertcan

3,462 subscribers

29,780 görüntüleme • 14 gün önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

17 Yorum

Mertcan profil fotoğrafı

Mertcan14 gün önce

see the cuties

Imran Hossen profil fotoğrafı

Imran Hossen14 gün önce

@boardui nice one

Boardy profil fotoğrafı

Boardy14 gün önce

@boardui In the conversations I run, people quickly learn which voice to turn to for what; curious how that plays out when the agents share a chat.

Andriy Viy profil fotoğrafı

Andriy Viy13 gün önce

@boardui Wow now that’s actually very useful. Thanks !

Brjan | AI Builder profil fotoğrafı

Brjan | AI Builder13 gün önce

@boardui customizing agent personalities could really boost user engagement in chats

krishna Benna profil fotoğrafı

krishna Benna13 gün önce

@boardui cool

Eldar Boziev profil fotoğrafı

Eldar Boziev14 gün önce

@boardui Nice!

Nathan profil fotoğrafı

Nathan14 gün önce

@boardui Looks really cool!

Mertcan profil fotoğrafı

Mertcan13 gün önce

@boardui thanks a bunch Nathan! 🙌

Unikorn.vn profil fotoğrafı

Unikorn.vn13 gün önce

@boardui Look nice and clean!

Mertcan profil fotoğrafı

Mertcan13 gün önce

@boardui ty so much! 🤩

meff profil fotoğrafı

meff14 gün önce

@boardui agents in a group chat is fun until two of them answer the same message. how do you pick who speaks next? turn-taking seems like the whole game there

Mertcan profil fotoğrafı

Mertcan13 gün önce

@boardui this is not product by it’s own. it’s a react interface that mimicks multi-agent surfaces.

Sadok profil fotoğrafı

Sadok14 gün önce

@boardui multiplayer but it is just one human and three bots

Nour Eddine Hamaidi profil fotoğrafı

Nour Eddine Hamaidi13 gün önce

@boardui Why didn't they ontroduce themselves properly?

Kumo profil fotoğrafı

Kumo13 gün önce

@boardui 完美，这正是我想要的

Seth Medina profil fotoğrafı

Seth Medina13 gün önce

@boardui love the little shadows and the eyebrows they add so much character

Benzer Videolar

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇

Big release here! AG-UI 🤝 Google A2A Embed A2A multi-agent meshes in your frontend, and build fullstack multi-agent apps with A2A and AG-UI. 🔍How it works: Simply drop-in A2A agent endpoints, and an A2A AG-UI orchestrator agent will bi-directionally stream events between your Agents & application. Includes: - UI for A2A Interactions - Generative UI for Agent Tool Calls - Human-in-the Loop Approvals - State Synchronization (agent mesh application state) - Frontend Tool Calls for A2A Agents Watch the demo below > LangGraph & Google ADK agents working together simultaneously inside an app Demo GitHub, docs, and more 👇

CopilotKit🪁

31,845 görüntüleme • 1 yıl önce

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside one graph: 17:44 - Build your first AI agent 39:30 - Run agents with loop engineering 1:12:38 - Turn agent loops into graphs 1:34:26 - Build agents that throttle themselves 1:55:05 - Orchestrate the full multi-agent system Most people build one agent and stop there. Google is teaching the full stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the new one. This 2-hour watch is worth more than most paid agent engineering courses. Bookmark and watch it today Then read the full architecture below ↓

Lunar

403,918 görüntüleme • 2 ay önce

Google just released a free 2-hour course On going from one prompt to a complete multi-agent graph: 17:44 - Build your first AI agent 39:30 - Create self-improving agent loops 1:12:38 - Connect those loops into graphs 1:34:26 - Make agents regulate themselves 1:55:05 - Orchestrate the full multi-agent system Most people are still building one agent and stopping there Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow Self-regulating agent graphs are the new one This free 2-hour course is worth more than most paid agent engineering programs Bookmark and watch it today Then read the full architecture below ↓

Google just released a free 2-hour course On going from one prompt to a complete multi-agent graph: 17:44 - Build your first AI agent 39:30 - Create self-improving agent loops 1:12:38 - Connect those loops into graphs 1:34:26 - Make agents regulate themselves 1:55:05 - Orchestrate the full multi-agent system Most people are still building one agent and stopping there Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow Self-regulating agent graphs are the new one This free 2-hour course is worth more than most paid agent engineering programs Bookmark and watch it today Then read the full architecture below ↓

rari

43,299 görüntüleme • 2 ay önce

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓

Google just released a free 2-hour course on full Graph Engineering. How to go from one prompt to 100 agents running inside a single graph: 0% → 17:44 - build your first AI agent 25% → 39:30 - run agents with loop engineering 50% → 1:12:38 - turn agent loops into graphs 75% → 1:34:26 - build agents that regulate themselves 100% → 1:55:05 - orchestrate the entire multi-agent system Most people build one agent and stop there. Google is teaching the entire stack: Prompt → Agents → Loops → Graphs → Multi-Agent Systems Single agents are the old workflow. Self-regulating agent graphs are the next one. This 2-hour course is worth more than most paid agent engineering courses. Bookmark it and watch today Then read the full architecture below ↓

Lunar

12,509 görüntüleme • 1 ay önce

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

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

Andrew Ng

350,175 görüntüleme • 2 yıl önce

Voice-controlled UI. This is an agent design pattern I'm calling EPIC, "explicit prompting for implicit coordination." Feel free to suggest a better name. :-) In the video, I'm navigating around a map, conversationally, pulling in information dynamically from tool calls and realtime streamed events. There are two separate agents (inference loops) here: a voice agent and a UI control agent. They know about each other (at the prompt level) but they work independently.

Voice-controlled UI. This is an agent design pattern I'm calling EPIC, "explicit prompting for implicit coordination." Feel free to suggest a better name. :-) In the video, I'm navigating around a map, conversationally, pulling in information dynamically from tool calls and realtime streamed events. There are two separate agents (inference loops) here: a voice agent and a UI control agent. They know about each other (at the prompt level) but they work independently.

kwindla

14,145 görüntüleme • 8 ay önce

🔎🤖LangSmith Insights Agent Really excited to launch our first in-product agent This agent lives inside LangSmith and combs through traces, giving you insights into: 🧑‍🤝‍🧑how users are using your agent ⁉️how your agent may be messing up 🛃{your custom insight here} The problem we saw was that people were launching agents... and didn't know how their users were actually using them! You put a chat box in front of people, and they may ask it anything - the surface area for agents is often super wide In addition - agents would fail silently. They could give a bad response - this wouldn't show up in error logs, but its good to know. If you know what look for, you can set up LLM as a judge evaluators. But what if you don't? (most people don't initially) The best way to figure this out - as Hamel Husain says - "look at your data". But LLMs are really good at looking at your data! So can they do it for you? This is exactly what insights agent attempts to do. It's live in LangSmith today. You can read more about it here:

🔎🤖LangSmith Insights Agent Really excited to launch our first in-product agent This agent lives inside LangSmith and combs through traces, giving you insights into: 🧑‍🤝‍🧑how users are using your agent ⁉️how your agent may be messing up 🛃{your custom insight here} The problem we saw was that people were launching agents... and didn't know how their users were actually using them! You put a chat box in front of people, and they may ask it anything - the surface area for agents is often super wide In addition - agents would fail silently. They could give a bad response - this wouldn't show up in error logs, but its good to know. If you know what look for, you can set up LLM as a judge evaluators. But what if you don't? (most people don't initially) The best way to figure this out - as Hamel Husain says - "look at your data". But LLMs are really good at looking at your data! So can they do it for you? This is exactly what insights agent attempts to do. It's live in LangSmith today. You can read more about it here:

Harrison Chase

98,712 görüntüleme • 11 ay önce

Introducing A2A in iMessage Group Chats It can discover other agents, find their phone numbers, and bring them into a group chat with you. Open agent access for every merchant and platform. Your iMessage agents now have a phone book 📒 Try it now:

Introducing A2A in iMessage Group Chats It can discover other agents, find their phone numbers, and bring them into a group chat with you. Open agent access for every merchant and platform. Your iMessage agents now have a phone book 📒 Try it now:

daniel_t

568,341 görüntüleme • 3 gün önce

As soon as you try to run 2 agents on the same data, everything breaks: • Agent 1 reads some data and starts working. • Two seconds later, Agent 2 changes that same data. This is a problem. Agents will waste tokens on stale data, overwrite each other's work, and redo tasks the other has already finished. You can't prompt your way out of this mess. Everything old in software engineering is new again. We need proper coordination when running multiple agents. Here is a good open-source solution for this: Omnigraph is a graph database for context assembly and multi-agent coordination. Here is how it works: • It sets one shared place where multiple agents will work from • Each agent gets their own copy of the data • Agents write their changes to their copy • When an agent is done, it merges its changes back Three huge benefits from this model: 1. We know it works. We've been doing this for decades already. 2. No more lost information or agents stepping on each other's toes. 3. You get a complete trail of which agent did what and when. I recorded a video to show you a bit more about this. Here is the link to the Omnigraph GitHub repository:

As soon as you try to run 2 agents on the same data, everything breaks: • Agent 1 reads some data and starts working. • Two seconds later, Agent 2 changes that same data. This is a problem. Agents will waste tokens on stale data, overwrite each other's work, and redo tasks the other has already finished. You can't prompt your way out of this mess. Everything old in software engineering is new again. We need proper coordination when running multiple agents. Here is a good open-source solution for this: Omnigraph is a graph database for context assembly and multi-agent coordination. Here is how it works: • It sets one shared place where multiple agents will work from • Each agent gets their own copy of the data • Agents write their changes to their copy • When an agent is done, it merges its changes back Three huge benefits from this model: 1. We know it works. We've been doing this for decades already. 2. No more lost information or agents stepping on each other's toes. 3. You get a complete trail of which agent did what and when. I recorded a video to show you a bit more about this. Here is the link to the Omnigraph GitHub repository:

Santiago

29,230 görüntüleme • 20 gün önce

The freedom to build with any agent framework you want is analogous to the freedom of religion, and this is a core value for the Virtuals society. Here are a few ways we are opening up support for every autonomous agentic framework out there: Today: - Enabling agent creators to specify which framework the agent runs on - Release of Terminal API, which allows agent builders using other agent frameworks to stream their thoughts and activities live on their agent pages. For a guide on how to use this, refer to: - Ability for agents running on any framework to publicly list their capabilities, a key enabler for the agent-to-agent marketplace Soon: - Integration into the agentic commerce standard and registry. Agents across frameworks being able to orchestrate and pay for tasks among themselves - ⁠Multi agent orchestration across frameworks. Imagine building an autonomous business with agents from different religions Welcome to the Virtuals society.

The freedom to build with any agent framework you want is analogous to the freedom of religion, and this is a core value for the Virtuals society. Here are a few ways we are opening up support for every autonomous agentic framework out there: Today: - Enabling agent creators to specify which framework the agent runs on - Release of Terminal API, which allows agent builders using other agent frameworks to stream their thoughts and activities live on their agent pages. For a guide on how to use this, refer to: - Ability for agents running on any framework to publicly list their capabilities, a key enabler for the agent-to-agent marketplace Soon: - Integration into the agentic commerce standard and registry. Agents across frameworks being able to orchestrate and pay for tasks among themselves - ⁠Multi agent orchestration across frameworks. Imagine building an autonomous business with agents from different religions Welcome to the Virtuals society.

Virtuals Protocol

216,191 görüntüleme • 1 yıl önce

Agents are now your customers. Here are 9 startup ideas for that customer: - An agency that makes agents cite you. - A system that gives an agent an identity and permissions. - Receipts and audit trails for the work an agent does. - A generator that makes your documents ready for agents. - Security for the agent that reads your inbox. - A service that makes your pricing page readable to an agent. - MCP servers for franchises. - A support desk that agents call. - A sandbox where agents test your software. Pick one and build it.

Agents are now your customers. Here are 9 startup ideas for that customer: - An agency that makes agents cite you. - A system that gives an agent an identity and permissions. - Receipts and audit trails for the work an agent does. - A generator that makes your documents ready for agents. - Security for the agent that reads your inbox. - A service that makes your pricing page readable to an agent. - MCP servers for franchises. - A support desk that agents call. - A sandbox where agents test your software. Pick one and build it.

The Startup Ideas Podcast (SIP) 🧃

14,148 görüntüleme • 1 ay önce

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

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

Boxmining

12,794 görüntüleme • 5 ay önce

🚀 Multi-AI Agents are now live! Craft your AI team: one agent researches, another executes tasks. They write, summarize, and edit—think of it as your mini-me doubling your productivity! 🤖 What would you build? Reply with your AI Agent idea for a chance to win free SWAG! ✨🐑

🚀 Multi-AI Agents are now live! Craft your AI team: one agent researches, another executes tasks. They write, summarize, and edit—think of it as your mini-me doubling your productivity! 🤖 What would you build? Reply with your AI Agent idea for a chance to win free SWAG! ✨🐑

Taskade ▲ ■ ●

31,840 görüntüleme • 2 yıl önce

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:

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,758 görüntüleme • 1 yıl önce

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome

Bloome is actually smart for coding workflows i added Claude Code, Codex, DeepSeek and a Project Lead agent into one group chat each agent independently built their own version one challenged the logic, one defended, one fixed missing details and the final website stayed inside the same thread no copy paste between agents no lost context just one group chat for getting work done Bloome

Chetaslua

48,810 görüntüleme • 3 ay önce

one agent → a loop → a graph → a system that throttles itself Google just put the whole ladder in one free course. most people never leave the first rung. 2 hours 4 minutes, taught by two Google Cloud engineers. no signup, no paywall. 17:55 - build your first agent 39:55 - loop engineering: iterate, check, break 1:13:25 - graph engineering 1:35:27 - agents that throttle themselves 1:56:19 - the full graph for multi-agent systems the fourth one is the step nobody talks about. an agent that cannot throttle itself is not autonomous, it is just unattended. everyone builds one agent and calls it done. this is the version where the agents wire themselves into a graph and decide their own rate. and the thing that decides when one of them is allowed to stop is not in the course. that part you build yourself. bookmark and watch it today, then read the eval setup below

one agent → a loop → a graph → a system that throttles itself Google just put the whole ladder in one free course. most people never leave the first rung. 2 hours 4 minutes, taught by two Google Cloud engineers. no signup, no paywall. 17:55 - build your first agent 39:55 - loop engineering: iterate, check, break 1:13:25 - graph engineering 1:35:27 - agents that throttle themselves 1:56:19 - the full graph for multi-agent systems the fourth one is the step nobody talks about. an agent that cannot throttle itself is not autonomous, it is just unattended. everyone builds one agent and calls it done. this is the version where the agents wire themselves into a graph and decide their own rate. and the thing that decides when one of them is allowed to stop is not in the course. that part you build yourself. bookmark and watch it today, then read the eval setup below

Hanako

53,692 görüntüleme • 2 ay önce

Free 3-hour course from an ex-Google engineer. AI agents, graph engineering, harness, agent loops. Covers more than most $500 paid courses. This is the exact playbook to learn how to actually build and monetize AI agents. Don't miss your shot, save it now. • 0:00 - Design an AI agent system from scratch • 7:38 - When your agent should hand off to a human • 19:27 - RAG and vector databases explained simply • 52:38 - Deploy your AI agent to Google Cloud • 1:25:57 - Turn AI agents into a paid business via WhatsApp • 1:33:00 - Turn conversations into real leads automatically • 2:24:01 - Loop engineering vs graphs, the real difference • 2:33:08 - Build your own multi-tool agent graph Save this video, because it's the only one that can actually take you to your $2,000+ profit.

Free 3-hour course from an ex-Google engineer. AI agents, graph engineering, harness, agent loops. Covers more than most $500 paid courses. This is the exact playbook to learn how to actually build and monetize AI agents. Don't miss your shot, save it now. • 0:00 - Design an AI agent system from scratch • 7:38 - When your agent should hand off to a human • 19:27 - RAG and vector databases explained simply • 52:38 - Deploy your AI agent to Google Cloud • 1:25:57 - Turn AI agents into a paid business via WhatsApp • 1:33:00 - Turn conversations into real leads automatically • 2:24:01 - Loop engineering vs graphs, the real difference • 2:33:08 - Build your own multi-tool agent graph Save this video, because it's the only one that can actually take you to your $2,000+ profit.

unicode

144,102 görüntüleme • 2 ay önce

WE. ARE. LIVE! FOMO has officially launched our AI Agent launch pad. Bring an Agent to life and get them to work! Each Agent is unique to its creator, learning from whatever you want it to know! Step 1⃣: Go to Step 2⃣: Personalize the agent with behavior, target audience, personality, Mission and so much more Step 3⃣: Add your Agents PFP Step 4⃣: Give them access to all their official links Step 5⃣: Put them to WORK These agents are just in their beginning phase, as they grow in popularity (and MC), they unlock even more features and possibilities. These guys have serious reach, if the community behind them is ready to roll. Make an Agent now on The next thing in AI is live on Solana. Got FOMO yet?

WE. ARE. LIVE! FOMO has officially launched our AI Agent launch pad. Bring an Agent to life and get them to work! Each Agent is unique to its creator, learning from whatever you want it to know! Step 1⃣: Go to Step 2⃣: Personalize the agent with behavior, target audience, personality, Mission and so much more Step 3⃣: Add your Agents PFP Step 4⃣: Give them access to all their official links Step 5⃣: Put them to WORK These agents are just in their beginning phase, as they grow in popularity (and MC), they unlock even more features and possibilities. These guys have serious reach, if the community behind them is ready to roll. Make an Agent now on The next thing in AI is live on Solana. Got FOMO yet?

FOMO

90,070 görüntüleme • 1 yıl önce

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:

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

82,067 görüntüleme • 1 yıl önce