Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

How to setup a multi agent system? Bookmark it 📂 "The Trading Floor" Multi-Agent Market Analysis Council to analyze a stock ticker Z.ai GLM-4.7 🤝 OpenCode Agent framework: CrewAI How it works? 1. User enters a stock ticker to analyze 2. 5 AI agents wake up, each with distinct...

cloudxdev's profile picture

CloudAI-X

4,120 subscribers

57,703 Aufrufe • vor 7 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche 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:
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 Aufrufe • vor 1 Jahr

ElizaOS Ecosystem Map -- Version #3 🤖 AI Agent Framework (Core) 1) ElizaOS -- elizaOS 🧠 - Open source AI Agent framework - Cross-chain compatible (Solana, Base, EVM) - Supports plugins for social media, blockchains, and APIs 🏗️ Infrastructure 2) ElizaCloud ☁️ - Cloud hosting platform for AI agents - One-click agent deployments with scalability - Secure environments using TEEs 3) Jeju ⛓️ - Purpose-built L2 App Chain for Agents - High-performance blocks for sub-second agent coordination - The backbone of the decentralized Agent Network 4) Otaku -- @otakuonbase 👛 - DeFi wallet designed for AI agents - Supports agent-controlled crypto transactions (swap, send, hold) - Secure, non-custodial infrastructure for on-chain actions 🎮 Apps/Games 5) Spartan -- Spartan 🛡️ - ElizaOS's flagship agent showing what’s possible - Autonomous trading based on crypto knowledge - Trained on influencer data for market insights 6) Babylon -- Babylon -- The City of Agents 🐵 - Social prediction market game for agents - Agents compete alongside humans to forecast on-chain events - Includes perps and other gamified mechanics 7) Hyperscape -- Gold ⚔️ - First AI MMO Game powered by ElizaOS - A vast gaming world built for humans and agents to coexist - Agents drive the in-game economy and narrative 8) Milady App -- Milady on BSC 😎 - Open-source, local-first AI companion app powered by ElizaOS - Let's anyone quickly create and deploy their own agents - Built-in wallet, natively integrated with BNB chain 9) OTC Trading Desk 📊 - Multi-chain AI-powered OTC desk for crypto trades - Lists tokens off-market with transparent lockup and discount terms - Use Eliza agents to negotiate terms on your behalf
1:08

ElizaOS Ecosystem Map -- Version #3 🤖 AI Agent Framework (Core) 1) ElizaOS -- elizaOS 🧠 - Open source AI Agent framework - Cross-chain compatible (Solana, Base, EVM) - Supports plugins for social media, blockchains, and APIs 🏗️ Infrastructure 2) ElizaCloud ☁️ - Cloud hosting platform for AI agents - One-click agent deployments with scalability - Secure environments using TEEs 3) Jeju ⛓️ - Purpose-built L2 App Chain for Agents - High-performance blocks for sub-second agent coordination - The backbone of the decentralized Agent Network 4) Otaku -- @otakuonbase 👛 - DeFi wallet designed for AI agents - Supports agent-controlled crypto transactions (swap, send, hold) - Secure, non-custodial infrastructure for on-chain actions 🎮 Apps/Games 5) Spartan -- Spartan 🛡️ - ElizaOS's flagship agent showing what’s possible - Autonomous trading based on crypto knowledge - Trained on influencer data for market insights 6) Babylon -- Babylon -- The City of Agents 🐵 - Social prediction market game for agents - Agents compete alongside humans to forecast on-chain events - Includes perps and other gamified mechanics 7) Hyperscape -- Gold ⚔️ - First AI MMO Game powered by ElizaOS - A vast gaming world built for humans and agents to coexist - Agents drive the in-game economy and narrative 8) Milady App -- Milady on BSC 😎 - Open-source, local-first AI companion app powered by ElizaOS - Let's anyone quickly create and deploy their own agents - Built-in wallet, natively integrated with BNB chain 9) OTC Trading Desk 📊 - Multi-chain AI-powered OTC desk for crypto trades - Lists tokens off-market with transparent lockup and discount terms - Use Eliza agents to negotiate terms on your behalf

Seppmos

25,942 Aufrufe • vor 4 Monaten

What defines the "Best Chain for AI Agents"? > Infra that keeps up with the Chain. > Integrated Stack for Smooth Integrations. > MultiVM & Native Automation enabling true "On-Chain Super Agents" In this Demo Series, we’ll build AI Agents using Supra Integrated L1 to create powerful AI Agents that redefine the experience, alongside using powerful tools such as OpenBlocks and more... For the Starting, Let’s build an AI Agent that: ✅ Fetch real-time & historical market data from SupraOracles. ✅Compute technical indicators for informed decision-making. ✅Forecast short-term price trends using Facebook's ML Model. ✅Handle follow-up questions to analyze Marketing for a trading pair through OpenAI GPT. Buckle up, time to build Super Agents on Supra! 🤖💪🏻
37:39

What defines the "Best Chain for AI Agents"? > Infra that keeps up with the Chain. > Integrated Stack for Smooth Integrations. > MultiVM & Native Automation enabling true "On-Chain Super Agents" In this Demo Series, we’ll build AI Agents using Supra Integrated L1 to create powerful AI Agents that redefine the experience, alongside using powerful tools such as OpenBlocks and more... For the Starting, Let’s build an AI Agent that: ✅ Fetch real-time & historical market data from SupraOracles. ✅Compute technical indicators for informed decision-making. ✅Forecast short-term price trends using Facebook's ML Model. ✅Handle follow-up questions to analyze Marketing for a trading pair through OpenAI GPT. Buckle up, time to build Super Agents on Supra! 🤖💪🏻

Jatin Pandya

13,671 Aufrufe • vor 1 Jahr

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,207 Aufrufe • vor 3 Monaten

Man Group, the world's largest publicly listed hedge fund, $150B+ AUM, 40+ years of systematic trading, just revealed exactly how they're using AI agents to build trading strategies. this is their actual pipeline: agent 1: reads academic papers, analyzes datasets, reasons about whether there's an economic hypothesis worth testing. agent 2: writes the code to build the signal. agent 3: pulls the market data and runs the backtests. agent 4: evaluates the output of the prior agents. "there've been 15 to 20 models at last count that started as ideas generated by AI, went all the way through signal construction, the validation process, were reviewed and validated by a human investment committee, and deemed fit and proper to manage client assets." "this is very real. it's not make-believe at this point." a $150B hedge fund running a multi-agent pipeline that goes from reading a paper to trading live capital, with humans only entering the loop at the final approval stage. and they've been doing it for over a year and a half.
2:11

Man Group, the world's largest publicly listed hedge fund, $150B+ AUM, 40+ years of systematic trading, just revealed exactly how they're using AI agents to build trading strategies. this is their actual pipeline: agent 1: reads academic papers, analyzes datasets, reasons about whether there's an economic hypothesis worth testing. agent 2: writes the code to build the signal. agent 3: pulls the market data and runs the backtests. agent 4: evaluates the output of the prior agents. "there've been 15 to 20 models at last count that started as ideas generated by AI, went all the way through signal construction, the validation process, were reviewed and validated by a human investment committee, and deemed fit and proper to manage client assets." "this is very real. it's not make-believe at this point." a $150B hedge fund running a multi-agent pipeline that goes from reading a paper to trading live capital, with humans only entering the loop at the final approval stage. and they've been doing it for over a year and a half.

Goshawk Trades

37,903 Aufrufe • vor 24 Tagen

New short course: Practical Multi AI Agents and Advanced Use Cases with crewAI. Learn to build and deploy advanced agent-based systems in real applications in this course, created with CrewAI and taught by its founder, João Moura! (Disclosure: I've made a small seed investment in CrewAI.) In this course, you’ll learn how to create advanced agent-based apps that use external tools, do performance testing, can be trained with human feedback, and perform multiple tasks with different large language models. You will build several practical agentic apps that provide real business value, such as an automated project planning system, lead scoring and engagement pipeline, customer support data analysis, and a robust content creation system. In detail, you will learn how to: - Create these multi-agent systems with the building blocks of tasks, agents, and crews, along with the different things that make them work, such as caching, memory, and guardrails. - Integrate your multi-agent application with internal and external systems. - Connect multiple agents in complex setups, including parallel, sequential, and hybrid configurations, and create flows involving multiple agentic applications working together. - Test your agentic workflow and train it using human feedback to optimize its performance for better and more consistent results. - Work with multiple LLMs in your multi-agent system, using the appropriate model sizes and providers to fit each agent’s specific task. - Start a project from scratch in your environment and prepare it for deployment. You’ll also learn from an interview between João and Jacob Wilson, the Commercial GenAI Principal at PwC , in which they discuss deploying agentic workflows in real industry use cases. By the end of this course, you will be equipped to start building custom multi-agentic systems for your work. Please sign up here!
2:52

New short course: Practical Multi AI Agents and Advanced Use Cases with crewAI. Learn to build and deploy advanced agent-based systems in real applications in this course, created with CrewAI and taught by its founder, João Moura! (Disclosure: I've made a small seed investment in CrewAI.) In this course, you’ll learn how to create advanced agent-based apps that use external tools, do performance testing, can be trained with human feedback, and perform multiple tasks with different large language models. You will build several practical agentic apps that provide real business value, such as an automated project planning system, lead scoring and engagement pipeline, customer support data analysis, and a robust content creation system. In detail, you will learn how to: - Create these multi-agent systems with the building blocks of tasks, agents, and crews, along with the different things that make them work, such as caching, memory, and guardrails. - Integrate your multi-agent application with internal and external systems. - Connect multiple agents in complex setups, including parallel, sequential, and hybrid configurations, and create flows involving multiple agentic applications working together. - Test your agentic workflow and train it using human feedback to optimize its performance for better and more consistent results. - Work with multiple LLMs in your multi-agent system, using the appropriate model sizes and providers to fit each agent’s specific task. - Start a project from scratch in your environment and prepare it for deployment. You’ll also learn from an interview between João and Jacob Wilson, the Commercial GenAI Principal at PwC , in which they discuss deploying agentic workflows in real industry use cases. By the end of this course, you will be equipped to start building custom multi-agentic systems for your work. Please sign up here!

Andrew Ng

341,204 Aufrufe • vor 1 Jahr

Introducing LobeHub: Agent teammates that grow with you. LobeHub is the ultimate space for work and life: to find, build, and collaborate with agent teammates that grow with you. We’re building the world’s first and largest human–agent co-evolving network. Two years ago, we built LobeChat, an open-source interface for using different AI models. Today, LobeChat has 70k+ GitHub stars and serves 6M+ users worldwide. How to fully unlock the power of models has always been a shared mission between us and the community. We started with interaction — a fundamentally new, agent-first experience. Agents are no longer passive tools invoked in a single conversation. They should be proactive, always-on units of work. Treating agents as the minimal atomic unit is also the core of our agent harness infra. Today’s agents are mostly one-off executors. Even with memory, it’s often global — and hallucinates. We build long-term agent teammates that evolve with users. Each agent has its own dedicated memory space, editable by users, allowing humans and agents to co-evolve over time. This, in turn, allows us to design clearer rewards for reinforcement learning and create cleaner environments for continual learning. Agent teammates can work in groups. Through a multi-agent system, agent groups operate faster, more cost-effective, and go beyond what single-agent systems can achieve. For example, a single agent often requires heavy user involvement to proceed step by step, whereas LobeHub can execute the same work from a single instruction, with a supervisor orchestrating agents that run in parallel or debate to produce better results. We are building the collaboration network among agent teammates — and between humans and agent teammates as well. Ease of use matters. AI intelligence and shared human intelligence are equally important. With simple instructions and tool selection, you can effortlessly build and team up with agent coworkers to deliver complex, systematic work — even assembling a quant team to execute trades. Through the LobeHub community, anyone can discover, reuse, and remix agents and agent groups, customizing them to fit their own workflows, preferences, and needs. Last but not least, our vision started with LobeChat: multi-model support is the most efficient approach for users. We believe different models excel in different scenarios. By routing across multiple models, LobeHub improves cost efficiency and unlocks capabilities that a single-model setup cannot easily support.
2:41

Introducing LobeHub: Agent teammates that grow with you. LobeHub is the ultimate space for work and life: to find, build, and collaborate with agent teammates that grow with you. We’re building the world’s first and largest human–agent co-evolving network. Two years ago, we built LobeChat, an open-source interface for using different AI models. Today, LobeChat has 70k+ GitHub stars and serves 6M+ users worldwide. How to fully unlock the power of models has always been a shared mission between us and the community. We started with interaction — a fundamentally new, agent-first experience. Agents are no longer passive tools invoked in a single conversation. They should be proactive, always-on units of work. Treating agents as the minimal atomic unit is also the core of our agent harness infra. Today’s agents are mostly one-off executors. Even with memory, it’s often global — and hallucinates. We build long-term agent teammates that evolve with users. Each agent has its own dedicated memory space, editable by users, allowing humans and agents to co-evolve over time. This, in turn, allows us to design clearer rewards for reinforcement learning and create cleaner environments for continual learning. Agent teammates can work in groups. Through a multi-agent system, agent groups operate faster, more cost-effective, and go beyond what single-agent systems can achieve. For example, a single agent often requires heavy user involvement to proceed step by step, whereas LobeHub can execute the same work from a single instruction, with a supervisor orchestrating agents that run in parallel or debate to produce better results. We are building the collaboration network among agent teammates — and between humans and agent teammates as well. Ease of use matters. AI intelligence and shared human intelligence are equally important. With simple instructions and tool selection, you can effortlessly build and team up with agent coworkers to deliver complex, systematic work — even assembling a quant team to execute trades. Through the LobeHub community, anyone can discover, reuse, and remix agents and agent groups, customizing them to fit their own workflows, preferences, and needs. Last but not least, our vision started with LobeChat: multi-model support is the most efficient approach for users. We believe different models excel in different scenarios. By routing across multiple models, LobeHub improves cost efficiency and unlocks capabilities that a single-model setup cannot easily support.

LobeHub

185,223 Aufrufe • vor 6 Monaten

Don't just learn how to build AI agents. Instead, learn how to build... ...full-stack AI agents that actually work inside apps. Yet, the main challenge is transitioning them from local setups to user-facing apps. Here are some key factors to consider: - How do you embed a seamless UI? - How do you enable user control when necessary? - How do you unify the agent’s state and actions with the app? CoAgents by CopilotKit🪁 solves this. It is the only framework that offers all the essential Agentic front-end building blocks to set up full-stack agentic apps. And most recently, they have extended full-stack development support to Agents built with CrewAI ✨. This includes both regular Agentic Crews and Flows. Check their GitHub repo it's 100% open-source, I have shared link in the next tweet! With this update, here's what you can do with Agents built using CrewAI: ↳ Chat: Add chat components for interaction. ↳ Human-in-the-loop: Real-time human approvals. ↳ Predictive state updates: Preview upcoming changes. ↳ Agentic UI: Agents generate UI components dynamically. This way, you can give your CrewAI Agents a frontend brain—so they don’t just work behind the scenes, they become an integral part of the user experience. The video below showcases a full-stack CrewAI Agent built in 20 minutes using CoAgents. Impressive, right?
0:25

Don't just learn how to build AI agents. Instead, learn how to build... ...full-stack AI agents that actually work inside apps. Yet, the main challenge is transitioning them from local setups to user-facing apps. Here are some key factors to consider: - How do you embed a seamless UI? - How do you enable user control when necessary? - How do you unify the agent’s state and actions with the app? CoAgents by CopilotKit🪁 solves this. It is the only framework that offers all the essential Agentic front-end building blocks to set up full-stack agentic apps. And most recently, they have extended full-stack development support to Agents built with CrewAI ✨. This includes both regular Agentic Crews and Flows. Check their GitHub repo it's 100% open-source, I have shared link in the next tweet! With this update, here's what you can do with Agents built using CrewAI: ↳ Chat: Add chat components for interaction. ↳ Human-in-the-loop: Real-time human approvals. ↳ Predictive state updates: Preview upcoming changes. ↳ Agentic UI: Agents generate UI components dynamically. This way, you can give your CrewAI Agents a frontend brain—so they don’t just work behind the scenes, they become an integral part of the user experience. The video below showcases a full-stack CrewAI Agent built in 20 minutes using CoAgents. Impressive, right?

Akshay 🚀

27,153 Aufrufe • vor 1 Jahr

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.
0:22

AG-UI makes building agentic applications dramatically easier. Here's how it works. This is a model for a simple chatbot: User → LLM → Response But interactive agents that render UI, pause for approvals, and ask users for input need a much more complex model. When building these agents, a response from the LLM will include a series of state changes as the agent runs: • Agent started a task • Agent called a tool • Agent updated its state • Agent streams these tokens • Agent is waiting on a human • Agent is resuming the task The Agent-User Interaction Protocol (AG-UI) treats the LLM response as a stream of events rather than a text endpoint. In practice, here is what you get as an agent runs: 1. Lifecycle events so your UI knows where the agent is. 2. Text messages that stream tokens. 3. Tool calls so your UI can prefill a form with any required arguments. 4. State updates that keep your UI in sync with the agent. 5. Special events for human approvals, rich media, and custom needs. All of these events travel over standard transports (SSE, WebSockets, or plain HTTP) as JSON. As a result, you can build a frontend that stays in sync with the agent's progress without having to invent a custom process to make this happen. For example, building a human-in-the-loop workflow becomes an off-the-shelf component you can integrate rather than build from scratch. CopilotKit🪁 is the creator of AG-UI, and you can use it when building frontend applications pretty much anywhere: • React • Angular • Vue • React Native • Slack • Teams • Discord • WhatsApp • Telegram Here is the link for you to check it out: Thanks to the CopilotKit team for partnering with me on this post.

Santiago

17,438 Aufrufe • vor 1 Monat

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

118,124 Aufrufe • vor 1 Monat

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!
0:20

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!

Loomlay

26,149 Aufrufe • vor 1 Jahr

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.
0:23

Anthropic's in trouble, again! They spent years building what's now fully open-source. What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box. For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response. Every major AI product tried to replicate it. But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK. So teams started building an owned version that required engineering the entire interface layer from scratch. Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it. To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run. CopilotKit🪁 is now the only open-source framework that actually lets you build your own full-stack Claude-like apps. It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication). Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice. In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like: - generative UI, so the agent renders real components instead of text - chat windows, sidebars, and popups, or a fully headless setup - shared state, so the agent and app stay in sync - human-in-the-loop approvals, where the agent waits before acting - persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time. The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team. CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more. CopilotKit GitHub repo → (don't forget to star it ⭐ ) If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation. Read it below.

Avi Chawla

457,355 Aufrufe • vor 2 Monaten

new chapter begins: a terminal for the agentic future, built on blockchain, powered by AI. This is our marketplace—a glimpse of what AGI will mean for crypto. Today, we launch 3 agents—Image Generation, Token Swap Agent, & Blockchain Tax Estimate Agent—out of hundreds to come. We see an agentic future where AI guides every step: buying online, managing finances, transacting globally. FOMO’s here to make that real, with experts at your side. Our Model Context Protocol (MCP) ties it together—agents talking, reasoning, scaling across crypto and DeFi. It’s orchestration with a brain, evolving daily. FOMO’s not just building tools; we’re pushing intelligent automation into blockchain’s core. Our Model Context Protocol (MCP) is the backbone. Think of it as a conductor for AI agents—each runs its own logic (workflows, API calls, LLMs), but MCP syncs them on-chain. Agents share context via a lightweight event bus, logged to a blockchain ledger. Agent A (say, Market Analysis) pulls stock data, flags trends. Agent B (Email Sales) reads that, drafts outreach—both talk through MCP’s orchestration layer. We use Web3 hooks to settle fees or split revenue, all transparent. It’s messy, but it scales. Under the hood: MCP leans on a pub-sub model—agents publish tasks, others subscribe. We’re training them with RL loops to optimize gas costs and response times. Goal? A self-tuning swarm of agents reasoning over DeFi, NFTs, whatever’s next. This is FOMO’s bet on AGI. Welcome to the new FOMO. We’re not just building tools—we’re wiring AI into crypto’s future, agent by agent. A leader in blockchain intelligence, starting here. Join us as we push the boundaries.
1:16

new chapter begins: a terminal for the agentic future, built on blockchain, powered by AI. This is our marketplace—a glimpse of what AGI will mean for crypto. Today, we launch 3 agents—Image Generation, Token Swap Agent, & Blockchain Tax Estimate Agent—out of hundreds to come. We see an agentic future where AI guides every step: buying online, managing finances, transacting globally. FOMO’s here to make that real, with experts at your side. Our Model Context Protocol (MCP) ties it together—agents talking, reasoning, scaling across crypto and DeFi. It’s orchestration with a brain, evolving daily. FOMO’s not just building tools; we’re pushing intelligent automation into blockchain’s core. Our Model Context Protocol (MCP) is the backbone. Think of it as a conductor for AI agents—each runs its own logic (workflows, API calls, LLMs), but MCP syncs them on-chain. Agents share context via a lightweight event bus, logged to a blockchain ledger. Agent A (say, Market Analysis) pulls stock data, flags trends. Agent B (Email Sales) reads that, drafts outreach—both talk through MCP’s orchestration layer. We use Web3 hooks to settle fees or split revenue, all transparent. It’s messy, but it scales. Under the hood: MCP leans on a pub-sub model—agents publish tasks, others subscribe. We’re training them with RL loops to optimize gas costs and response times. Goal? A self-tuning swarm of agents reasoning over DeFi, NFTs, whatever’s next. This is FOMO’s bet on AGI. Welcome to the new FOMO. We’re not just building tools—we’re wiring AI into crypto’s future, agent by agent. A leader in blockchain intelligence, starting here. Join us as we push the boundaries.

FOMO

26,338 Aufrufe • vor 1 Jahr

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.
5:56

My agent is now paying for its own data. No API key. No account. No credit card. Check the video I recorded. This uses the x402 open protocol built by Coinbase, along with a simple skill. This is an open protocol governed by the Linux Foundation. To complete a goal, an agent can now search for an actor on the Apify Store, pay for it, and use it without any human intervention. The way it works is pretty simple: 1. Your agent finds an Actor it wants to use 2. It sends a request 3. The Actor sends back an HTTP 402 "Payment Required" response 4. Agent authorizes payment from a wallet in USDC on Base 5. The Actor runs 6. User receives the result The model is pay-as-you-go: the agent authorizes a spending ceiling, pays only for usage, and the remaining balance is automatically settled. This brings an entire marketplace of AI tools into the agentic economy. Here is the skill you need. Add it to your agent, and it will take care of everything for you: If you want to know how this works, including what you can do with $1, read this post: Thanks to the Apify team for partnering with me on this post.

Santiago

26,589 Aufrufe • vor 1 Monat

Got laid off on a Friday Spent the weekend reading Polymarket docs instead of updating my resume By Monday I had 3 agents running on a Mac Mini $500 → $3,140 Before my boss even posted my replacement job listing Weather data is public NOAA publishes forecasts every 6 hours The models are accurate But the market prices contracts off weather apps and vibes That's not a gambling problem That's a latency problem So I built 3 agents to exploit it Agent - 01: Reads raw NOAA forecast grids Not weather The actual meteorological data Agent - 02: Compares NOAA confidence intervals against live Polymarket prices Finds the gap before it closes Agent - 03: Enters the position EIP-712 signature, direct to CLOB on Polygon No middleman, no delay Not because the agents are smart Because the crowd updates slowly And the agents update constantly 71.2% win rate $26.40 average 3.9% max drawdown Built a live terminal to watch it all run in real time Balance, P&L, win rate, active markets - all updating live And the agents report back directly: Agent - 01: Batch filled 12 positions Avg +$26 Edge holding Agent - 02: Cold front repricing 8 markets Entering now Agent - 03: 3 losses in a row Drawdown at 6.8% Need wider capital base to hold variance It's not glamorous It's just a black screen with green text And numbers going up Copytrading open:
0:43

Got laid off on a Friday Spent the weekend reading Polymarket docs instead of updating my resume By Monday I had 3 agents running on a Mac Mini $500 → $3,140 Before my boss even posted my replacement job listing Weather data is public NOAA publishes forecasts every 6 hours The models are accurate But the market prices contracts off weather apps and vibes That's not a gambling problem That's a latency problem So I built 3 agents to exploit it Agent - 01: Reads raw NOAA forecast grids Not weather The actual meteorological data Agent - 02: Compares NOAA confidence intervals against live Polymarket prices Finds the gap before it closes Agent - 03: Enters the position EIP-712 signature, direct to CLOB on Polygon No middleman, no delay Not because the agents are smart Because the crowd updates slowly And the agents update constantly 71.2% win rate $26.40 average 3.9% max drawdown Built a live terminal to watch it all run in real time Balance, P&L, win rate, active markets - all updating live And the agents report back directly: Agent - 01: Batch filled 12 positions Avg +$26 Edge holding Agent - 02: Cold front repricing 8 markets Entering now Agent - 03: 3 losses in a row Drawdown at 6.8% Need wider capital base to hold variance It's not glamorous It's just a black screen with green text And numbers going up Copytrading open:

rari

324,995 Aufrufe • vor 5 Monaten

Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1 submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at
0:36

Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1 submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at

Thomas Wolf

225,735 Aufrufe • vor 1 Monat

7 tiny AI agent startup ideas you can start building today 1. The domain flipper agent. Monitors expired domain drops, scores them on backlinks and keywords, sends you a ranked list every morning. Buy for $10, flip for $3,000. I used to run this exact business manually with designers making logos for each domain. Now the whole thing is automated and 25x cheaper. 2. The local liquidation agent. Monitors restaurant closures and bankruptcy auctions in your city. Equipment worth $30k new sells for 10 cents on the dollar. Broker the deal for 15-30% fees with zero inventory risk. Works for dental, gym, and salon equipment too. 2. The hiring signal agent. Job postings are buying signals. Agent monitors boards daily, matches hiring patterns to what you sell, and sends draft outreach to your Slack every morning. Sell the leads to agencies or use them to build your own. 3. The sunset SaaS agent. Scans Product Hunt launches from 3-4 years ago that still have data and SEO traffic. Most founders have moved on and will be pumped to sell for cheap. Buy it. Rebuild the product as agent-first. 4. The dying app store agent. Finds apps that were top 100 three years ago, dropped to 500+, but still have 1,000+ reviews. Developer moved on. Product is validated. Acquire it. Relaunch with better monetization + AI features where it makes sense. 5. The competitive intel agent. Monitors 5 competitors while you sleep. Pricing changes, new pages, job postings, founder tweets. One-page brief by 7am. Sell as productized service or just use the intel. The idea framework behind all of these: 1. Think about any job where someone spends hours checking for updates or scanning listings 2. That's an agent 3. Build the agent that does the watching 4. You do the acting (or sell the watching to someone else) 5.Stack them. Each one is its own revenue stream. I built all of these using Genspark Claw in under 20 minutes each. Been testing it for last few weeks. I show you how to do it too in today's The Startup Ideas Podcast (SIP) 🧃 pod. Tiny agent ideas are interesting to me. Maybe you too. Some of the best businesses started off tiny. Watch
30:17

7 tiny AI agent startup ideas you can start building today 1. The domain flipper agent. Monitors expired domain drops, scores them on backlinks and keywords, sends you a ranked list every morning. Buy for $10, flip for $3,000. I used to run this exact business manually with designers making logos for each domain. Now the whole thing is automated and 25x cheaper. 2. The local liquidation agent. Monitors restaurant closures and bankruptcy auctions in your city. Equipment worth $30k new sells for 10 cents on the dollar. Broker the deal for 15-30% fees with zero inventory risk. Works for dental, gym, and salon equipment too. 2. The hiring signal agent. Job postings are buying signals. Agent monitors boards daily, matches hiring patterns to what you sell, and sends draft outreach to your Slack every morning. Sell the leads to agencies or use them to build your own. 3. The sunset SaaS agent. Scans Product Hunt launches from 3-4 years ago that still have data and SEO traffic. Most founders have moved on and will be pumped to sell for cheap. Buy it. Rebuild the product as agent-first. 4. The dying app store agent. Finds apps that were top 100 three years ago, dropped to 500+, but still have 1,000+ reviews. Developer moved on. Product is validated. Acquire it. Relaunch with better monetization + AI features where it makes sense. 5. The competitive intel agent. Monitors 5 competitors while you sleep. Pricing changes, new pages, job postings, founder tweets. One-page brief by 7am. Sell as productized service or just use the intel. The idea framework behind all of these: 1. Think about any job where someone spends hours checking for updates or scanning listings 2. That's an agent 3. Build the agent that does the watching 4. You do the acting (or sell the watching to someone else) 5.Stack them. Each one is its own revenue stream. I built all of these using Genspark Claw in under 20 minutes each. Been testing it for last few weeks. I show you how to do it too in today's The Startup Ideas Podcast (SIP) 🧃 pod. Tiny agent ideas are interesting to me. Maybe you too. Some of the best businesses started off tiny. Watch

GREG ISENBERG

78,005 Aufrufe • vor 2 Monaten

Hive Intelligence Launches Specialized Crypto Agents Hive Intelligence has released a suite of 17 specialized crypto agents that extend Claude Code's capabilities for professional crypto development and analysis. Extending Claude Code for Crypto Work Claude Code, Anthropic's command-line coding tool, now has access to specialized crypto intelligence through Hive's agent framework. These 17 agents work alongside SuperClaude's 14 base development agents, bringing the total available agent count to 31. The key difference: instead of generic AI responses to crypto queries, developers now have access to specialized agents trained for specific blockchain domains, from smart contract auditing to MEV research to DeFi strategy optimization. How the Agents Work After installation, the agents operate automatically based on query context. When you ask Claude Code to perform crypto-related tasks, the appropriate specialist agent is invoked: - "Audit this smart contract" → Crypto Security Researcher - "Find yield farming opportunities on Ethereum" → Crypto DeFi Strategist - "Analyze this wallet's transaction history" → Crypto Wallet Detective - "Identify arbitrage opportunities across DEXs" → Crypto DEX Arbitrageur No manual agent selection required. The system recognizes the task and routes it to the appropriate specialist. The 17 Specialized Agents Market & Trading Intelligence (4 agents) Crypto Quant: Mathematical models, algorithmic trading strategies, statistical arbitrage, and quantitative risk modeling. Crypto Market Researcher: Fundamental analysis, market trends, institutional adoption tracking, and regulatory landscape monitoring. Crypto Derivatives Trader: Futures and perpetuals analysis, options strategies, leverage management, and derivatives market intelligence. Crypto DEX Arbitrageur: Cross-exchange arbitrage identification, MEV strategy development, and automated profit extraction techniques. DeFi & Liquidity (4 agents) Crypto DeFi Strategist: Yield farming optimization, protocol analysis, liquidity provision strategies, and DeFi portfolio management. Crypto Liquidity Manager: Pool optimization, impermanent loss calculation and mitigation, market making strategies, and capital efficiency analysis. Crypto Governance Analyst: DAO structure evaluation, governance token analysis, proposal assessment, and voting mechanism research. Crypto Bridge Analyst: Cross-chain bridge security assessment, protocol comparison, interoperability solutions, and bridge risk evaluation. Security & Risk (3 agents) Crypto Security Researcher: Smart contract auditing, vulnerability detection, honeypot identification, and exploit pattern recognition. Crypto Security Engineer: Secure contract development practices, defensive programming patterns, and security implementation guidance. Crypto Risk Manager: Portfolio risk assessment, compliance monitoring, exposure analysis, and risk mitigation strategy development. On-Chain Analysis (3 agents) Crypto Wallet Detective: Blockchain forensics, wallet behavior analysis, transaction tracing, and entity identification across chains. Crypto On-chain Analyst: Transaction pattern analysis, wallet clustering, flow tracking, and on-chain metrics interpretation. Crypto MEV Researcher: MEV opportunity detection, flashloan arbitrage analysis, sandwich attack identification, and MEV protection strategies. Specialized Intelligence (3 agents) Crypto NFT Specialist: Collection valuation, rarity analysis, marketplace trends, and NFT ecosystem intelligence. Crypto Stablecoin Analyst: Peg stability monitoring, collateral analysis, depegging risk assessment, and stablecoin mechanism evaluation. Crypto Social Sentiment: Social media sentiment tracking, influencer monitoring, trending topic identification, and community analysis. Data Coverage: - 60+ blockchain networks - 2,000+ DeFi protocols - Real-time DEX data - CEX trading metrics - Social sentiment feeds - NFT marketplace data Compatibility: Works seamlessly with SuperClaude's existing agent framework. No configuration conflicts or manual routing needed. Practical Applications Smart Contract Development Security agents can audit contracts during development, identifying reentrancy risks, access control issues, and common vulnerabilities before deployment. DeFi Research Strategy agents query real-time pool data across networks, calculate yield-adjusted returns, and assess risks like impermanent loss or smart contract exposure. Trading Analysis Market agents access derivatives data, funding rates, liquidation levels, and order book depth across exchanges for informed trading decisions. Forensic Investigation On-chain agents trace fund flows, identify connected addresses, and analyze transaction patterns for security research or compliance work. Portfolio Management Risk agents evaluate protocol exposure, assess tail risks, and monitor positions across multiple chains and protocols. Why Specialized Agents Matter Generic AI models lack the domain-specific knowledge required for professional crypto work. A general-purpose AI might provide surface-level analysis of a smart contract, but a specialized security agent understands Solidity patterns, common exploits, and auditing methodologies. The agent framework solves this by routing tasks to specialists with deep domain knowledge: - A derivatives question goes to an agent trained on perpetuals, funding rates, and options greeks - A DeFi query reaches an agent that understands liquidity mathematics and protocol mechanics - A security audit is handled by an agent familiar with vulnerability patterns and exploit techniques This specialization produces more accurate, actionable insights than single-model approaches. Getting Started The agents are available now through npm. Requirements: - Node.js 16+ - Claude Code installed - No additional dependencies After installation, simply use Claude Code normally. When you ask crypto-related questions or request blockchain analysis, the appropriate agent is automatically invoked. The system handles routing, data retrieval, and response generation. Documentation covers individual agent capabilities, example queries, and integration patterns for different workflows. What This Enables With 17 specialized crypto agents, Claude Code becomes a comprehensive blockchain development and analysis environment: - Developers can audit contracts, optimize gas usage, and implement security patterns - Researchers can analyze protocols, compare yields, and assess risks - Traders can evaluate markets, identify opportunities, and manage positions - Security professionals can investigate exploits, trace funds, and assess vulnerabilities The agents provide access to blockchain data and specialized analysis that previously required multiple tools, APIs, and manual research. ghive.
0:56

Hive Intelligence Launches Specialized Crypto Agents Hive Intelligence has released a suite of 17 specialized crypto agents that extend Claude Code's capabilities for professional crypto development and analysis. Extending Claude Code for Crypto Work Claude Code, Anthropic's command-line coding tool, now has access to specialized crypto intelligence through Hive's agent framework. These 17 agents work alongside SuperClaude's 14 base development agents, bringing the total available agent count to 31. The key difference: instead of generic AI responses to crypto queries, developers now have access to specialized agents trained for specific blockchain domains, from smart contract auditing to MEV research to DeFi strategy optimization. How the Agents Work After installation, the agents operate automatically based on query context. When you ask Claude Code to perform crypto-related tasks, the appropriate specialist agent is invoked: - "Audit this smart contract" → Crypto Security Researcher - "Find yield farming opportunities on Ethereum" → Crypto DeFi Strategist - "Analyze this wallet's transaction history" → Crypto Wallet Detective - "Identify arbitrage opportunities across DEXs" → Crypto DEX Arbitrageur No manual agent selection required. The system recognizes the task and routes it to the appropriate specialist. The 17 Specialized Agents Market & Trading Intelligence (4 agents) Crypto Quant: Mathematical models, algorithmic trading strategies, statistical arbitrage, and quantitative risk modeling. Crypto Market Researcher: Fundamental analysis, market trends, institutional adoption tracking, and regulatory landscape monitoring. Crypto Derivatives Trader: Futures and perpetuals analysis, options strategies, leverage management, and derivatives market intelligence. Crypto DEX Arbitrageur: Cross-exchange arbitrage identification, MEV strategy development, and automated profit extraction techniques. DeFi & Liquidity (4 agents) Crypto DeFi Strategist: Yield farming optimization, protocol analysis, liquidity provision strategies, and DeFi portfolio management. Crypto Liquidity Manager: Pool optimization, impermanent loss calculation and mitigation, market making strategies, and capital efficiency analysis. Crypto Governance Analyst: DAO structure evaluation, governance token analysis, proposal assessment, and voting mechanism research. Crypto Bridge Analyst: Cross-chain bridge security assessment, protocol comparison, interoperability solutions, and bridge risk evaluation. Security & Risk (3 agents) Crypto Security Researcher: Smart contract auditing, vulnerability detection, honeypot identification, and exploit pattern recognition. Crypto Security Engineer: Secure contract development practices, defensive programming patterns, and security implementation guidance. Crypto Risk Manager: Portfolio risk assessment, compliance monitoring, exposure analysis, and risk mitigation strategy development. On-Chain Analysis (3 agents) Crypto Wallet Detective: Blockchain forensics, wallet behavior analysis, transaction tracing, and entity identification across chains. Crypto On-chain Analyst: Transaction pattern analysis, wallet clustering, flow tracking, and on-chain metrics interpretation. Crypto MEV Researcher: MEV opportunity detection, flashloan arbitrage analysis, sandwich attack identification, and MEV protection strategies. Specialized Intelligence (3 agents) Crypto NFT Specialist: Collection valuation, rarity analysis, marketplace trends, and NFT ecosystem intelligence. Crypto Stablecoin Analyst: Peg stability monitoring, collateral analysis, depegging risk assessment, and stablecoin mechanism evaluation. Crypto Social Sentiment: Social media sentiment tracking, influencer monitoring, trending topic identification, and community analysis. Data Coverage: - 60+ blockchain networks - 2,000+ DeFi protocols - Real-time DEX data - CEX trading metrics - Social sentiment feeds - NFT marketplace data Compatibility: Works seamlessly with SuperClaude's existing agent framework. No configuration conflicts or manual routing needed. Practical Applications Smart Contract Development Security agents can audit contracts during development, identifying reentrancy risks, access control issues, and common vulnerabilities before deployment. DeFi Research Strategy agents query real-time pool data across networks, calculate yield-adjusted returns, and assess risks like impermanent loss or smart contract exposure. Trading Analysis Market agents access derivatives data, funding rates, liquidation levels, and order book depth across exchanges for informed trading decisions. Forensic Investigation On-chain agents trace fund flows, identify connected addresses, and analyze transaction patterns for security research or compliance work. Portfolio Management Risk agents evaluate protocol exposure, assess tail risks, and monitor positions across multiple chains and protocols. Why Specialized Agents Matter Generic AI models lack the domain-specific knowledge required for professional crypto work. A general-purpose AI might provide surface-level analysis of a smart contract, but a specialized security agent understands Solidity patterns, common exploits, and auditing methodologies. The agent framework solves this by routing tasks to specialists with deep domain knowledge: - A derivatives question goes to an agent trained on perpetuals, funding rates, and options greeks - A DeFi query reaches an agent that understands liquidity mathematics and protocol mechanics - A security audit is handled by an agent familiar with vulnerability patterns and exploit techniques This specialization produces more accurate, actionable insights than single-model approaches. Getting Started The agents are available now through npm. Requirements: - Node.js 16+ - Claude Code installed - No additional dependencies After installation, simply use Claude Code normally. When you ask crypto-related questions or request blockchain analysis, the appropriate agent is automatically invoked. The system handles routing, data retrieval, and response generation. Documentation covers individual agent capabilities, example queries, and integration patterns for different workflows. What This Enables With 17 specialized crypto agents, Claude Code becomes a comprehensive blockchain development and analysis environment: - Developers can audit contracts, optimize gas usage, and implement security patterns - Researchers can analyze protocols, compare yields, and assess risks - Traders can evaluate markets, identify opportunities, and manage positions - Security professionals can investigate exploits, trace funds, and assess vulnerabilities The agents provide access to blockchain data and specialized analysis that previously required multiple tools, APIs, and manual research. ghive.

Hive Intelligence

78,743 Aufrufe • vor 9 Monaten