Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Agentic Website Scraping using Firecrawl: How to Setup Locally? 🔥 Integrate with @LangChainAI LlamaIndex 🦙 🤖 AI Agent Integration PraisonAI 🌐 Set up locally Docker 📊 Data Processing Automation Llama 3 LLM Groq Inc 🔄 Search @yousearchengine Mendable @firecrawl_dev Subscribe: YT:

MervinPraison's profile picture

Mervin Praison

10,733 subscribers

20,909 Aufrufe • vor 2 Jahren •via X (Twitter)

BildungWissenschaft & TechnologieNachrichten & Politik
LIVE

Anya Rossi• Live Now

Private livecam show

10 Kommentare

Profilbild von Nicolas Camara
Nicolas Camaravor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev 🔥🔥🔥

Profilbild von Eric Ciarla
Eric Ciarlavor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev Great work @MervinPraison!

Profilbild von Adam Silverman (Hiring!) 🖇️
Adam Silverman (Hiring!) 🖇️vor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev Awesome

Profilbild von Happy
Happyvor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev like

Profilbild von Essa Mamdani
Essa Mamdanivor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev Use free opensource for crawling.

Profilbild von Дмитрий Суриков
Дмитрий Суриковvor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev AI + Web3 = Innovation! 🚀🌐 @magnetaixyz @din_lol_ GODIN

Profilbild von Igor Andreichenk
Igor Andreichenkvor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev Your AI, your profit! 💰🤖 @magnetaixyz @din_lol_ GODIN

Profilbild von NONAME❤️ WELL3
NONAME❤️ WELL3vor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev ModelFi: The AI game-changer! 🎮💫 @magnetaixyz @din_lol_ GODIN

Profilbild von Ninew💙NOYA.ai
Ninew💙NOYA.aivor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev 🔥 Web3Go who? It's all about DIN now! Go @din_lol_ $ARCA

Profilbild von Mercury.fi
Mercury.fivor 2 Jahren

@LangChainAI @llama_index @PraisonAI @Docker @GroqInc @yousearchengine @mendableai @firecrawl_dev AI + Web3 = Innovation! 🚀🌐 @magnetaixyz @din_lol_ GODIN

Ähnliche Videos

How to Fine Tune Llama 3 for Better Instruction Following? 🚀 Setup Environment 📊 Train Model 💾 Save Model Locally 🌐 Upload Model to Hugging Face 📈 Evaluate Performance 🛠 Using 🦥 Unsloth AI Subscribe: YT: Meta AI at Meta Daniel Han
8:54

How to Fine Tune Llama 3 for Better Instruction Following? 🚀 Setup Environment 📊 Train Model 💾 Save Model Locally 🌐 Upload Model to Hugging Face 📈 Evaluate Performance 🛠 Using 🦥 Unsloth AI Subscribe: YT: Meta AI at Meta Daniel Han

Mervin Praison

14,111 Aufrufe • vor 2 Jahren

Today we're excited to launch `create-llama` - a single CLI command that allows you to scaffold a full stack LLM app over your data, powered by LlamaIndex 🦙 🔥 It’s the equivalent of `create-react-app` for AI engineers. Choose from 3 different backends: ✅ FastAPI (w/ LlamaIndex 🦙 Python) ✅ ExpressJS (w/ LlamaIndex 🦙 TS) ✅ Next.js (w/ LlamaIndex 🦙 TS) The frontend is a Next.js template using initial chat components from the Vercel AI SDK - with full streaming support, + shadcn UI or vanilla HTML/CSS for styling. This is a full-stack starting point, from which you can customize any component to build the LLM app of your liking, whether it’s simple extensions (change data source) or complete revamps (upgraded chat UX)! Next steps 🔮: - We’re going to be coming out with more examples in the next few weeks showing what you can build. - We’re going to be upgrading `create-llama` with a variety of different templates Check out the video (also attached) to see how it works 🎥: Repo directory: Full blog post detailing the usage here:
3:22

Today we're excited to launch `create-llama` - a single CLI command that allows you to scaffold a full stack LLM app over your data, powered by LlamaIndex 🦙 🔥 It’s the equivalent of `create-react-app` for AI engineers. Choose from 3 different backends: ✅ FastAPI (w/ LlamaIndex 🦙 Python) ✅ ExpressJS (w/ LlamaIndex 🦙 TS) ✅ Next.js (w/ LlamaIndex 🦙 TS) The frontend is a Next.js template using initial chat components from the Vercel AI SDK - with full streaming support, + shadcn UI or vanilla HTML/CSS for styling. This is a full-stack starting point, from which you can customize any component to build the LLM app of your liking, whether it’s simple extensions (change data source) or complete revamps (upgraded chat UX)! Next steps 🔮: - We’re going to be coming out with more examples in the next few weeks showing what you can build. - We’re going to be upgrading `create-llama` with a variety of different templates Check out the video (also attached) to see how it works 🎥: Repo directory: Full blog post detailing the usage here:

Jerry Liu

259,026 Aufrufe • vor 2 Jahren

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

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

Jerry Liu

55,620 Aufrufe • vor 9 Monaten

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.
0:28

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

18,053 Aufrufe • vor 20 Tagen

This is how I use LLM to scrape 99% of websites Many people didn't realise you can build agentic scraper to: 1. Handle Authentication, Human verification, Captcha 2. Handle pagination & complex UI interactions 3. Adaptive as website structure change 4. Scrape large set of data What used to take hours now can be automated in mins; Here I show case how do you automate a scraping job on Upwork where people are paying $50~$80 per hour; 0:00 Intro 1:54 Methods overview 4:52 Web Scraper agent using Spider Cloud 🕷️ Jina AI 8:37 Handle website auth & captcha using AgentQL 20:27 AI buy tickets MultiOn AI If you have any further question or want to get deep dive into the code example in the video, you can join my community where I post tips weekly:
22:43

This is how I use LLM to scrape 99% of websites Many people didn't realise you can build agentic scraper to: 1. Handle Authentication, Human verification, Captcha 2. Handle pagination & complex UI interactions 3. Adaptive as website structure change 4. Scrape large set of data What used to take hours now can be automated in mins; Here I show case how do you automate a scraping job on Upwork where people are paying $50~$80 per hour; 0:00 Intro 1:54 Methods overview 4:52 Web Scraper agent using Spider Cloud 🕷️ Jina AI 8:37 Handle website auth & captcha using AgentQL 20:27 AI buy tickets MultiOn AI If you have any further question or want to get deep dive into the code example in the video, you can join my community where I post tips weekly:

Jason Zhou

128,111 Aufrufe • vor 1 Jahr

Guys check out this latest tech token that just have today and is definitely flying under the radar! 🚀 Agent Alpha has been building in stealth mode for the past year. Their platform lets users deploy AI agents that gather trading alpha continuously, from Telegram, Dexscreener, X, wallet trackers, anything with visual input. Their agents analyze the data in real-time to give traders buy and sell recommendations based off the parameters the user inputs. 🔥 Agent Alpha is launching in the next week for DEX, with Telegram and X set to follow quickly behind. They have several high profile partnerships with other agentic projects in the coming weeks, where these projects will be using Agent Alpha to gather real-time data. They are the first product to launch using the framework created by LiftDataAI. 💎 Also coming soon is Agent Alpha's own extensible framework, which will enable advanced users to add new data sources to the platform and integrate their own tools for technical analysis. Advanced users will be able to deploy agents privately, or tokenize them and release them publicly. ⭐️ Agent Alpha will only be available to holders of the $AA ticker. ⚡️ 📈DexScreener - 🕊Twitter - 🌐website -
0:46

Guys check out this latest tech token that just have today and is definitely flying under the radar! 🚀 Agent Alpha has been building in stealth mode for the past year. Their platform lets users deploy AI agents that gather trading alpha continuously, from Telegram, Dexscreener, X, wallet trackers, anything with visual input. Their agents analyze the data in real-time to give traders buy and sell recommendations based off the parameters the user inputs. 🔥 Agent Alpha is launching in the next week for DEX, with Telegram and X set to follow quickly behind. They have several high profile partnerships with other agentic projects in the coming weeks, where these projects will be using Agent Alpha to gather real-time data. They are the first product to launch using the framework created by LiftDataAI. 💎 Also coming soon is Agent Alpha's own extensible framework, which will enable advanced users to add new data sources to the platform and integrate their own tools for technical analysis. Advanced users will be able to deploy agents privately, or tokenize them and release them publicly. ⭐️ Agent Alpha will only be available to holders of the $AA ticker. ⚡️ 📈DexScreener - 🕊Twitter - 🌐website -

Pumpcoinbets - Crypto & NFT

75,322 Aufrufe • vor 1 Jahr

Introducing Sharpe Search: On-Chain Search AI Agent Powered by Hive Intelligence We’re thrilled to announce the launch of Sharpe Search, a crypto search AI agent powered by Hive Intelligence Designed to simplify blockchain data interaction, Sharpe Search represents a significant step toward making crypto more accessible and actionable for users at every level. Sharpe Search leverages Hive Intelligence’s advanced search API to provide real-time, actionable insights across the blockchain ecosystem. Here’s a detailed look at what Sharpe Search is, how it works: What Is Sharpe Search? At its core, Sharpe Search is an AI agent purpose-built for querying and analyzing on-chain data. It takes the complexity out of blockchain exploration by enabling users to ask questions in plain language and receive detailed, accurate responses. Whether you’re looking to monitor wallet activity, track portfolio positions, or analyze transaction history, Sharpe Search ensures that the answers are at your fingertips—accurate, comprehensive, and delivered instantly. How Does Sharpe Search Work? Sharpe Search is powered by Hive Intelligence, a search engine API designed to make blockchain data easily accessible and AI-ready. Here’s a breakdown of how it enables Sharpe Search to function effectively: 1. LLM-Optimized Query Processing Sharpe Search leverages Hive Intelligence's optimized responses for large language models. This ensures that AI agents can process blockchain data in a structured format, delivering precise answers to complex user queries. 2. Natural Language Interaction Forget the need for technical knowledge. Sharpe Search supports natural language queries, making it as simple as typing: - “What tokens are in my wallet? Am I eligible for any airdrop I haven't claimed yet?” - “Check me my last 100 transactions, tell me if I interacted with any protocol with recent hacks” - “Track my wallet activity over the past month, suggest optimised portfolio based on best stable yields available” 3. Real-Time Insights Across Multi-Chains Using Hive Intelligence, Sharpe Search connects to over 20 chains and 5000+ Protocols. This real-time access ensures that the AI agent provides up-to-date and actionable insights, no matter how dynamic the blockchain environment. 4. Unified API Access Sharpe Search consolidates fragmented blockchain data through Hive’s unified API. Instead of dealing with multiple integrations, Sharpe Search uses a single access point to aggregate and query data, reducing complexity for both users and developers. Technical Depth: The AI Agent Advantage Sharpe Search's design philosophy revolves around the principle of creating an intuitive, AI-driven experience. Here’s what makes its technology stand out: Data Indexing and Aggregation: Hive Intelligence employs advanced indexing algorithms to aggregate data from multiple chains. This ensures that Sharpe Search can retrieve information within milliseconds, even when querying vast datasets. Dynamic Updates: Blockchain data is volatile. Sharpe Search processes dynamic updates in real time, enabling users to act on the most recent metrics, transactions, and balances without delays. Contextual Understanding: The AI agent parses natural language queries and contextualizes them to blockchain-specific scenarios. For instance, when querying “Show portfolio details,” Sharpe Search understands the underlying requirements—fetching wallet holdings, token values, and current positions. Hive Intelligence: The Backbone of Sharpe Search While Sharpe Search takes center stage, Hive Intelligence provides the critical infrastructure to make it all possible. Its LLM-ready responses and multi-chain support ensure that Sharpe Search operates at the forefront of blockchain data accessibility. By launching Hive Intelligence through Sharpe Launchpad, Sharpe reinforces its commitment to supporting innovation in the blockchain space. Hive’s infrastructure not only powers Sharpe Search but also lays the groundwork for future AI agents to thrive in the ecosystem. What’s Next for Sharpe Search? Currently in invite-only access, Sharpe Search is preparing for a broader public release. Future updates will include: - Expanded Blockchain Coverage: More chains and protocols will be added. - Enhanced Query Flexibility: Even more advanced natural language capabilities. Stay tuned for the public launch and get ready to explore crypto like never before!
1:33

Introducing Sharpe Search: On-Chain Search AI Agent Powered by Hive Intelligence We’re thrilled to announce the launch of Sharpe Search, a crypto search AI agent powered by Hive Intelligence Designed to simplify blockchain data interaction, Sharpe Search represents a significant step toward making crypto more accessible and actionable for users at every level. Sharpe Search leverages Hive Intelligence’s advanced search API to provide real-time, actionable insights across the blockchain ecosystem. Here’s a detailed look at what Sharpe Search is, how it works: What Is Sharpe Search? At its core, Sharpe Search is an AI agent purpose-built for querying and analyzing on-chain data. It takes the complexity out of blockchain exploration by enabling users to ask questions in plain language and receive detailed, accurate responses. Whether you’re looking to monitor wallet activity, track portfolio positions, or analyze transaction history, Sharpe Search ensures that the answers are at your fingertips—accurate, comprehensive, and delivered instantly. How Does Sharpe Search Work? Sharpe Search is powered by Hive Intelligence, a search engine API designed to make blockchain data easily accessible and AI-ready. Here’s a breakdown of how it enables Sharpe Search to function effectively: 1. LLM-Optimized Query Processing Sharpe Search leverages Hive Intelligence's optimized responses for large language models. This ensures that AI agents can process blockchain data in a structured format, delivering precise answers to complex user queries. 2. Natural Language Interaction Forget the need for technical knowledge. Sharpe Search supports natural language queries, making it as simple as typing: - “What tokens are in my wallet? Am I eligible for any airdrop I haven't claimed yet?” - “Check me my last 100 transactions, tell me if I interacted with any protocol with recent hacks” - “Track my wallet activity over the past month, suggest optimised portfolio based on best stable yields available” 3. Real-Time Insights Across Multi-Chains Using Hive Intelligence, Sharpe Search connects to over 20 chains and 5000+ Protocols. This real-time access ensures that the AI agent provides up-to-date and actionable insights, no matter how dynamic the blockchain environment. 4. Unified API Access Sharpe Search consolidates fragmented blockchain data through Hive’s unified API. Instead of dealing with multiple integrations, Sharpe Search uses a single access point to aggregate and query data, reducing complexity for both users and developers. Technical Depth: The AI Agent Advantage Sharpe Search's design philosophy revolves around the principle of creating an intuitive, AI-driven experience. Here’s what makes its technology stand out: Data Indexing and Aggregation: Hive Intelligence employs advanced indexing algorithms to aggregate data from multiple chains. This ensures that Sharpe Search can retrieve information within milliseconds, even when querying vast datasets. Dynamic Updates: Blockchain data is volatile. Sharpe Search processes dynamic updates in real time, enabling users to act on the most recent metrics, transactions, and balances without delays. Contextual Understanding: The AI agent parses natural language queries and contextualizes them to blockchain-specific scenarios. For instance, when querying “Show portfolio details,” Sharpe Search understands the underlying requirements—fetching wallet holdings, token values, and current positions. Hive Intelligence: The Backbone of Sharpe Search While Sharpe Search takes center stage, Hive Intelligence provides the critical infrastructure to make it all possible. Its LLM-ready responses and multi-chain support ensure that Sharpe Search operates at the forefront of blockchain data accessibility. By launching Hive Intelligence through Sharpe Launchpad, Sharpe reinforces its commitment to supporting innovation in the blockchain space. Hive’s infrastructure not only powers Sharpe Search but also lays the groundwork for future AI agents to thrive in the ecosystem. What’s Next for Sharpe Search? Currently in invite-only access, Sharpe Search is preparing for a broader public release. Future updates will include: - Expanded Blockchain Coverage: More chains and protocols will be added. - Enhanced Query Flexibility: Even more advanced natural language capabilities. Stay tuned for the public launch and get ready to explore crypto like never before!

Sharpe AI

263,308 Aufrufe • vor 1 Jahr

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch
27:27

how to use firecrawl to give your AI eyes and actually build startups that outperform 99% of apps: 1. your AI is smart but blind. it can't go to a website, read a page, or grab data on its own. firecrawl fixes that. you put in a URL. you get back clean markdown, structured JSON, screenshots. feed it to any model. 2. three lines of code. that's it. no proxies. no anti-bot detection. no custom scrapers that break when a site changes. one API call. clean data back in seconds. works on 98%+ of sites. 3. firecrawl has six core capabilities: scrape a single page. crawl an entire site. map all URLs on a domain. search google and return full content. an agent endpoint where you describe what you want and it goes and finds it. and a browser sandbox where AI controls a real browser like filling forms, clicking buttons, handles logins. 4. the agent endpoint is wild. you can say "find all of YC's winter 24 dev tool companies and their founders and emails" and get back structured data. or "compare pricing tiers across stripe, square, and paypal" and get a side-by-side table. 5. the browser sandbox lets your AI stay logged in across sessions, navigate pagination, watch live as it browses. this is computer use without building the infrastructure yourself. 6. think of it in layers. every builder needs: an agent harness (claude code, cursor, codex), a search layer (perplexity, exa), a web data layer (firecrawl), an ops brain (obsidian, notion), and an outbound stack. the web data layer is the one most people are sleeping on. 7. this is the AWS moment for web data. in 2006 building a web app meant buying servers and managing racks. AWS said one API call, use our servers. some of the biggest companies of the last decade were built on that. firecrawl is doing the same thing for web data in 2026. 8. the framework i'd use for coming up with startup ideas building with clean data: take a massive horizontal platform. rebuild it for one niche using firecrawl. the vertical version always wins because people want specific, not generic. price for outcome. 9. a year ago firecrawl posted a job listing that said "please only apply if you're an AI agent." content creator agents. customer support agents. junior dev agents. it looked weird. it was a signal for where this is all going. the people who understand how to get clean web data, wrap it around an LLM, and package it as a product are the the ones with a 12-month head start. i use Firecrawl with Idea Browser . once you see what's possible with structured web data, you can't unsee it. episode is live on The Startup Ideas Podcast (SIP) 🧃 (full breakdown there) i tried to explain this as clear as possible for even the non technical. send it to a builder friend. watch

GREG ISENBERG

135,254 Aufrufe • vor 6 Monaten

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 expertise: - Quant Analyst — technical indicators & price patterns - Sentiment Scout — market mood & crowd psychology - Macro Strategist — sector dynamics & economic context - Risk Manager — volatility, drawdowns & position sizing - Portfolio Chief — synthesizes all perspectives 3. Agents analyze independently using real market data 4. They debate, challenge assumptions, and identify disagreements 5. Portfolio Chief resolves conflicts and delivers a consensus recommendation 6. Final output: buy/hold/sell rating with confidence level, position size, and key risks How to built The Trading Floor? 1. Chose CrewAI as the agent framework — handles multi-agent orchestration out of the box 2. Defined 5 agents with distinct roles, goals, and backstories in Python 3. Built custom tools wrapping yfinance for real market data (prices, indicators, volatility) 4. Configured sequential workflow — specialists analyze first, Portfolio Chief synthesizes last 5. Set up FastAPI backend with SSE to stream agent thoughts in real-time 6. Built Next.js frontend to visualize the "board of directors" deliberating live 7. One environment variable (MODEL=openai/gpt-5.2) powers all agents 8. Generated unique agent icons with AI image tools Total cost: $0 for the framework, pay only for LLM API calls Tech stack: - GLM-4.7 with opencode to build the app - CrewAI (open source) for agent orchestration - GPT-5.2 powering each agent - FastAPI + SSE for real-time streaming - Next.js frontend showing live agent deliberations
0:40

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 expertise: - Quant Analyst — technical indicators & price patterns - Sentiment Scout — market mood & crowd psychology - Macro Strategist — sector dynamics & economic context - Risk Manager — volatility, drawdowns & position sizing - Portfolio Chief — synthesizes all perspectives 3. Agents analyze independently using real market data 4. They debate, challenge assumptions, and identify disagreements 5. Portfolio Chief resolves conflicts and delivers a consensus recommendation 6. Final output: buy/hold/sell rating with confidence level, position size, and key risks How to built The Trading Floor? 1. Chose CrewAI as the agent framework — handles multi-agent orchestration out of the box 2. Defined 5 agents with distinct roles, goals, and backstories in Python 3. Built custom tools wrapping yfinance for real market data (prices, indicators, volatility) 4. Configured sequential workflow — specialists analyze first, Portfolio Chief synthesizes last 5. Set up FastAPI backend with SSE to stream agent thoughts in real-time 6. Built Next.js frontend to visualize the "board of directors" deliberating live 7. One environment variable (MODEL=openai/gpt-5.2) powers all agents 8. Generated unique agent icons with AI image tools Total cost: $0 for the framework, pay only for LLM API calls Tech stack: - GLM-4.7 with opencode to build the app - CrewAI (open source) for agent orchestration - GPT-5.2 powering each agent - FastAPI + SSE for real-time streaming - Next.js frontend showing live agent deliberations

CloudAI-X

58,189 Aufrufe • vor 9 Monaten

over the labor day weekend i built out an app to analyze my twitter mutuals, using my Hyperspace agentic-os prototype. this is likely the most powerful agentic-os setup every assembled. this goes beyond a single model, or agent, or data source or a single smart CLI tool. this goes beyond hardware, or cloud or distributed networks. it is all of it, combined. the LLM OS is here, Andrej Karpathy. and this combined environment enabled me to build an app I craved for all these years, without writing a single line of code, saving me 150 hours of development work effort. i now have a deep understanding of my twitter mutuals here - and to construct the app - my agentic-os utilized multiple models including Grok Code, GPT-OSS-120B running locally, Qwen2.5 Coder and Google's Nano Banana, multiple orchestrators include Claude Code, 24 AI agents, several MCPs, and specific data from my Twitter archive which I plugged in and other data which it researched, analyzed and aggregated into helping me understand my network here. consider again: the absolute best work from all the top AI firms - all of it, in one actually-useful-integrated-environment. RT if you want this as well. any feature requests ? eg show when a mutual is in the same city in the future.. will DM with access.. this is madness, but it is here 🤖🔥
1:27

over the labor day weekend i built out an app to analyze my twitter mutuals, using my Hyperspace agentic-os prototype. this is likely the most powerful agentic-os setup every assembled. this goes beyond a single model, or agent, or data source or a single smart CLI tool. this goes beyond hardware, or cloud or distributed networks. it is all of it, combined. the LLM OS is here, Andrej Karpathy. and this combined environment enabled me to build an app I craved for all these years, without writing a single line of code, saving me 150 hours of development work effort. i now have a deep understanding of my twitter mutuals here - and to construct the app - my agentic-os utilized multiple models including Grok Code, GPT-OSS-120B running locally, Qwen2.5 Coder and Google's Nano Banana, multiple orchestrators include Claude Code, 24 AI agents, several MCPs, and specific data from my Twitter archive which I plugged in and other data which it researched, analyzed and aggregated into helping me understand my network here. consider again: the absolute best work from all the top AI firms - all of it, in one actually-useful-integrated-environment. RT if you want this as well. any feature requests ? eg show when a mutual is in the same city in the future.. will DM with access.. this is madness, but it is here 🤖🔥

Varun

22,229 Aufrufe • vor 1 Jahr

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

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

Andrew Ng

142,256 Aufrufe • vor 1 Jahr

THIS GUY OPENED A TINY PC AND SHOWED HOW A $1,800 GMKTEC EVO-X2 TURNS INTO A LOCAL AI SERVER not a cloud dashboard. not another $200/mo subscription. just one box on a desk, upgraded with storage, cleaner airflow, faster networking, and pointed at real local models. the numbers are what make it interesting. Claude Code Max is $200/mo, ChatGPT Pro is $200/mo, Cursor is another $20/mo. that is $5,040/year just to rent tools most people use for coding, research, summaries, and agents. EVO-X2 flips the setup because it has 128GB unified memory, Ryzen AI Max+ 395, and up to 110GB usable as VRAM on Linux. enough room for Qwen3-Coder 30B, Llama 70B, and 200B-class local models when speed is not the bottleneck. so the workflow becomes simple: buy the box once, install Linux, run the model locally, connect the CLI, and let the machine handle jobs from your own network instead of sending every request to the cloud. this is where the real edge starts. overnight code audits, private document search, local RAG, scraping agents, transcription, file cleanup, all running while the token meter stays at zero. frontier models still win for the hardest prompts. but for daily automation, coding, research, and private workflows, local AI is already moving from nerd setup to obvious business math. the next flex won’t be “which AI plan do you pay for?” it’ll be “what’s running under your desk?”
1:09

THIS GUY OPENED A TINY PC AND SHOWED HOW A $1,800 GMKTEC EVO-X2 TURNS INTO A LOCAL AI SERVER not a cloud dashboard. not another $200/mo subscription. just one box on a desk, upgraded with storage, cleaner airflow, faster networking, and pointed at real local models. the numbers are what make it interesting. Claude Code Max is $200/mo, ChatGPT Pro is $200/mo, Cursor is another $20/mo. that is $5,040/year just to rent tools most people use for coding, research, summaries, and agents. EVO-X2 flips the setup because it has 128GB unified memory, Ryzen AI Max+ 395, and up to 110GB usable as VRAM on Linux. enough room for Qwen3-Coder 30B, Llama 70B, and 200B-class local models when speed is not the bottleneck. so the workflow becomes simple: buy the box once, install Linux, run the model locally, connect the CLI, and let the machine handle jobs from your own network instead of sending every request to the cloud. this is where the real edge starts. overnight code audits, private document search, local RAG, scraping agents, transcription, file cleanup, all running while the token meter stays at zero. frontier models still win for the hardest prompts. but for daily automation, coding, research, and private workflows, local AI is already moving from nerd setup to obvious business math. the next flex won’t be “which AI plan do you pay for?” it’ll be “what’s running under your desk?”

Gipp 🦅

13,365 Aufrufe • vor 3 Monaten

how to set up hermes agent step by step. built-in memory, 40+ tools, works on your phone, and what to think of hermes vs openclaw: 1. hermes is a personal AI agent that runs in your terminal. think of it like open claw but with built-in memory, 40+ tools out of the box, and 90% cheaper token costs. you install it with one command. 2. the 3 problems with open claw that hermes solves: no memory (you keep repeating yourself), constant gateway restarts, and zero visibility into what you're spending on tokens. 3. hermes remembers everything. every completed task gets saved to memory. it searches through past logs to find solutions. over time it literally gets smarter at your specific workflows. 4. connect it to open router. you see exact costs per model per task. free models rotate weekly. one founder went from $130 every five days on open claw to $10 on hermes. same output. 5. it comes preloaded with skills. apple notes, imessage, find my, browser, web search, image generation, cron jobs. no hunting for plugins. 6. connect it to obsidian so it reads your entire vault. connect it to gstack for your dev environment. create custom skills for your specific workflows. 7. the biggest money saver: have it write code once for recurring tasks. then it runs without burning tokens every time. stop paying an LLM to do the same scrape or report daily. 8. run it on android via telegram. name your agents. talk to them like coworkers. in this episode imran shows you how to set this up. 9. you can run it bare metal, in docker, or serverless on modal. pick your risk level. i begged imran to come on The Startup Ideas Podcast (SIP) 🧃 and walk through the full installation live. he made it impossibly clear. if you've heard of Hermes Agent and want the clearest explanation of how to get set up like a pro let me know what you want me to cover on the next ep this is the best personal agent setup video on the internet right now. watch
37:00

how to set up hermes agent step by step. built-in memory, 40+ tools, works on your phone, and what to think of hermes vs openclaw: 1. hermes is a personal AI agent that runs in your terminal. think of it like open claw but with built-in memory, 40+ tools out of the box, and 90% cheaper token costs. you install it with one command. 2. the 3 problems with open claw that hermes solves: no memory (you keep repeating yourself), constant gateway restarts, and zero visibility into what you're spending on tokens. 3. hermes remembers everything. every completed task gets saved to memory. it searches through past logs to find solutions. over time it literally gets smarter at your specific workflows. 4. connect it to open router. you see exact costs per model per task. free models rotate weekly. one founder went from $130 every five days on open claw to $10 on hermes. same output. 5. it comes preloaded with skills. apple notes, imessage, find my, browser, web search, image generation, cron jobs. no hunting for plugins. 6. connect it to obsidian so it reads your entire vault. connect it to gstack for your dev environment. create custom skills for your specific workflows. 7. the biggest money saver: have it write code once for recurring tasks. then it runs without burning tokens every time. stop paying an LLM to do the same scrape or report daily. 8. run it on android via telegram. name your agents. talk to them like coworkers. in this episode imran shows you how to set this up. 9. you can run it bare metal, in docker, or serverless on modal. pick your risk level. i begged imran to come on The Startup Ideas Podcast (SIP) 🧃 and walk through the full installation live. he made it impossibly clear. if you've heard of Hermes Agent and want the clearest explanation of how to get set up like a pro let me know what you want me to cover on the next ep this is the best personal agent setup video on the internet right now. watch

GREG ISENBERG

623,943 Aufrufe • vor 5 Monaten

Maple is preparing for the release of a co-working agent. You install it locally and it works with your files, whether it's office work or building websites and apps. It's a turnkey solution, as easy as Claude Code, that keeps your data secure and private, no data sharing with closed AI labs. This is THE sovereign AI app for individuals and businesses who want powerful AI while retaining ownership of their information. Why build an agent into the Maple app when other agents already exist? Easy, we want to give you control over your work. We don't have a business plan that incorporates making money off our users' data. In the age of AI, your information, whether it's personal or company trade secrets, is the single thing that differentiates you from everyone else. We all have access to AI that can build a professional website for selling shoes. But your strategy and network for how you sell shoes should not be shared with your competitors. Sovereignty is the path to protecting what makes you, you. Maple sits at the intersection of Usability and Sovereignty. Maple gives you the best tools that are both easy to use and maintain your data sovereignty. Sovereign for one, sovereign for all. It has been a journey to get here. We brought to market the very first personal chatbot with end-to-end encryption using TEEs in late 2024. Prior to that there were proofs of concept but no full product offerings. Every other AI chat product on the market handled your data in plain text, either selling you a service to get your data or asking you to trust that they won't snoop on you. Quickly people found Maple and latched onto its open-source code and verifiable encryption. We didn't stop there. You may remember earlier this year we teased a product called "Maple Agent" and opened up a waiting list. That product is a mobile app that acts as your AI "friend", maintaining one long continuous chat, and getting to know you over time. I dislike using the word "friend" there, but it's the best way to convey the UX in a few words. AI is a tool, always has been, always will be. Any kind of friendly personality on top is just synthetic. In our testing, the UX of Maple Agent is really powerful for what it does. Think about the many short AI chats you have in your favorite app, whether it's looking up a historical fact or asking advice about a topic. With Maple Agent, those all go away in favor of the long-running chat with the friendly agent. It's like you have your own personal assistant who knows you so well and can look up anything for you. When I ask AI certain questions, I want to ask an expert who already understands my situation so I'm not repeating myself for the 100th time. That's the amazing value the personal agent brings to the table. We still see great utility for a personal agent like the "Maple Agent". Thousands of people on the waiting list, hoping to get their hands on it, agree that the concept is worth exploring and trying out. We were constrained in launching it due to a few circumstances, one of them being access to the scale of compute needed to power it. We have a clear path laid out for how to get there, but today is not the day to execute on that. It will be in the near future. Instead we have a different agent ready to go that we think is also incredible. We now have an agentic harness inside of the Maple Research app. This thing is a powerhouse. It even builds and publishes its own software releases. The agent in Maple Research works with your local filesystem, speaks to the largest open models running in TEEs, utilizes local models for certain tasks, is compatible with MCP tools, has an API for connecting to anything you need, and also supports the ACP protocol, which means it can be extended in the future to speak to other tools like Claude Code, Codex, and local models running on your own hardware. A big unlock for us was the Goose Development Kit, which powers the core of our agent harness. More on that to come as we publish articles and documentation later about the agent. The agent inside Maple Research doesn't have a name. At least not yet, not sure if it ever will. For now we call it "Chat Mode" and "Agent Mode". Think of this as the workhorse, the truck, the heavy lifter. Our other "Agent", the phone app, is your sidekick in your pocket, ready to help with quick things and ongoing conversations about life. I am incredibly excited about the Maple Research Agent. While I'm already seeing great results using it for internal work items, I'm especially thrilled about the personal health and wellness work it's doing for me. I know there are plenty of apps out there for compiling wellness data, but I'm having it build a tool tailored specifically for what I need, without the extra fluff. And none of my health data is being donated to the closed AI labs or sent to advertisers. I know that the AI logic is not being silently adjusted to fit the whims of a large corporation that has paid for product placement. It's me, state of the art AI, and my data. That's how I want it. Maple's new agent makes that possible. We can't wait for you to try it out. If you want early access, comment here, email us, reach out in some way. To those on the other agent waitlist, you're already in the queue. Thanks for reading this lengthy update. :)
0:49

Maple is preparing for the release of a co-working agent. You install it locally and it works with your files, whether it's office work or building websites and apps. It's a turnkey solution, as easy as Claude Code, that keeps your data secure and private, no data sharing with closed AI labs. This is THE sovereign AI app for individuals and businesses who want powerful AI while retaining ownership of their information. Why build an agent into the Maple app when other agents already exist? Easy, we want to give you control over your work. We don't have a business plan that incorporates making money off our users' data. In the age of AI, your information, whether it's personal or company trade secrets, is the single thing that differentiates you from everyone else. We all have access to AI that can build a professional website for selling shoes. But your strategy and network for how you sell shoes should not be shared with your competitors. Sovereignty is the path to protecting what makes you, you. Maple sits at the intersection of Usability and Sovereignty. Maple gives you the best tools that are both easy to use and maintain your data sovereignty. Sovereign for one, sovereign for all. It has been a journey to get here. We brought to market the very first personal chatbot with end-to-end encryption using TEEs in late 2024. Prior to that there were proofs of concept but no full product offerings. Every other AI chat product on the market handled your data in plain text, either selling you a service to get your data or asking you to trust that they won't snoop on you. Quickly people found Maple and latched onto its open-source code and verifiable encryption. We didn't stop there. You may remember earlier this year we teased a product called "Maple Agent" and opened up a waiting list. That product is a mobile app that acts as your AI "friend", maintaining one long continuous chat, and getting to know you over time. I dislike using the word "friend" there, but it's the best way to convey the UX in a few words. AI is a tool, always has been, always will be. Any kind of friendly personality on top is just synthetic. In our testing, the UX of Maple Agent is really powerful for what it does. Think about the many short AI chats you have in your favorite app, whether it's looking up a historical fact or asking advice about a topic. With Maple Agent, those all go away in favor of the long-running chat with the friendly agent. It's like you have your own personal assistant who knows you so well and can look up anything for you. When I ask AI certain questions, I want to ask an expert who already understands my situation so I'm not repeating myself for the 100th time. That's the amazing value the personal agent brings to the table. We still see great utility for a personal agent like the "Maple Agent". Thousands of people on the waiting list, hoping to get their hands on it, agree that the concept is worth exploring and trying out. We were constrained in launching it due to a few circumstances, one of them being access to the scale of compute needed to power it. We have a clear path laid out for how to get there, but today is not the day to execute on that. It will be in the near future. Instead we have a different agent ready to go that we think is also incredible. We now have an agentic harness inside of the Maple Research app. This thing is a powerhouse. It even builds and publishes its own software releases. The agent in Maple Research works with your local filesystem, speaks to the largest open models running in TEEs, utilizes local models for certain tasks, is compatible with MCP tools, has an API for connecting to anything you need, and also supports the ACP protocol, which means it can be extended in the future to speak to other tools like Claude Code, Codex, and local models running on your own hardware. A big unlock for us was the Goose Development Kit, which powers the core of our agent harness. More on that to come as we publish articles and documentation later about the agent. The agent inside Maple Research doesn't have a name. At least not yet, not sure if it ever will. For now we call it "Chat Mode" and "Agent Mode". Think of this as the workhorse, the truck, the heavy lifter. Our other "Agent", the phone app, is your sidekick in your pocket, ready to help with quick things and ongoing conversations about life. I am incredibly excited about the Maple Research Agent. While I'm already seeing great results using it for internal work items, I'm especially thrilled about the personal health and wellness work it's doing for me. I know there are plenty of apps out there for compiling wellness data, but I'm having it build a tool tailored specifically for what I need, without the extra fluff. And none of my health data is being donated to the closed AI labs or sent to advertisers. I know that the AI logic is not being silently adjusted to fit the whims of a large corporation that has paid for product placement. It's me, state of the art AI, and my data. That's how I want it. Maple's new agent makes that possible. We can't wait for you to try it out. If you want early access, comment here, email us, reach out in some way. To those on the other agent waitlist, you're already in the queue. Thanks for reading this lengthy update. :)

Mark

46,589 Aufrufe • vor 2 Monaten

🤖🔬 Can AI actually do science end-to-end? 🧠📈 And how would we know when it matches, or surpasses, humans? ⚡🧪 AI is rapidly automating scientific discovery, but benchmarking full-cycle discovery, from 💡 ideation → 🧑‍💻 execution → 📊 conclusions, remains unsolved: 🧐🧐🧐 ❌🛠️ Open-ended discovery → manual validation (costly, unscalable) ❌📏 Metric-driven benchmarks (e.g., MLE-Bench) → convenient but narrow (is higher accuracy really enough?) ❌🤖⚖️ LLM-as-judge → useful, but fundamentally risky if used alone 🔥🚀 Introducing FIRE-Bench🔥: Fullcycle Insight Rediscovery Evaluation 👉🌐 📚✨ A benchmark that turns fresh, human-verified insights from recent 🏆 NeurIPS / ICLR / ICML papers into masked, end-to-end discovery challenges 🧩 🌍🔐 Constrained open-ended discovery–backed by ground truth. 📌 Key takeaways: 1⃣ 📖🧱 Reference-based evaluation still matters: constrained LLM judging helps, but human-grounded references remain essential until agents can consistently match human conclusions 2⃣ 🏆🧠 Expert-validated ground truth: all tasks come from recent NeurIPS / ICLR / ICML papers, with contamination carefully controlled 3⃣ 🔁🎭 Rediscovery, not reproduction: original 🧪 methods, 📊 experiments, 💻 implementations, and 📈 analyses are fully masked to create real discovery challenges 🔑 Key empirical findings: 💡 The "Science Gap" is Real: Even the best setup (Claude Code + Sonnet-4) caps out at an F1 score of 46.7. On hard tasks, agents struggle to break 30 💡 Success is a "Lottery": Performance has incredibly high variance. Reliability is a major unsolved issue. 💡 Coding is no longer the bottleneck; high-level reasoning and analysis are: ~74% of errors stem from flawed planning, not coding ⚙️ How it works: 🔹 Research-Problem Trees: We parse papers into trees (from broad roots to concrete leaves). This allows us to select intermediate nodes that perfectly balance open-ended exploration with verifiable ground truth. 🔹 Claim-Level Evaluation: We match AI conclusions against human conclusions using granular claim decomposition (F1 score). 🔹 Creativity Check: We score false positives to see if agents are finding novel truths (Spoiler🚨: they aren’t creative yet). 🔹 New Diagnostic Taxonomy: failures traced across four stages: 🧠 Planning → 🛠️ Implementation → ▶️ Execution → 🧾 Conclusion 🔹 Additional Analyses: cost efficiency, contamination checks, and more. 👀 The Future: 🚀 Live-FIRE-Bench: a live, continuously updated FIRE-Bench to track real-time progress on the latest research (Newest LLMs should be benchmarked with the newest research) 🚀 Stronger scaffolding (search + planning + coding) 🧠🧰 and converting FIRE-Bench into interactive environments for training research agents 🚀 Toward real creativity: We want better systems that can produce genuinely novel conclusions toward creativity 🎨⏳ 🚀 Better systems 🧠✨ and better benchmarks 📏 must co-evolve 🔄 over time 📜🎥 Paper, video, demo, and research trees: 👉🌐 #AI 🤖 #MachineLearning 📚 #AI4Science 🔬 #LLMs 🧠 #Research 🧪 #AgenticAI 🚀 #FireBench 🔥
0:42

🤖🔬 Can AI actually do science end-to-end? 🧠📈 And how would we know when it matches, or surpasses, humans? ⚡🧪 AI is rapidly automating scientific discovery, but benchmarking full-cycle discovery, from 💡 ideation → 🧑‍💻 execution → 📊 conclusions, remains unsolved: 🧐🧐🧐 ❌🛠️ Open-ended discovery → manual validation (costly, unscalable) ❌📏 Metric-driven benchmarks (e.g., MLE-Bench) → convenient but narrow (is higher accuracy really enough?) ❌🤖⚖️ LLM-as-judge → useful, but fundamentally risky if used alone 🔥🚀 Introducing FIRE-Bench🔥: Fullcycle Insight Rediscovery Evaluation 👉🌐 📚✨ A benchmark that turns fresh, human-verified insights from recent 🏆 NeurIPS / ICLR / ICML papers into masked, end-to-end discovery challenges 🧩 🌍🔐 Constrained open-ended discovery–backed by ground truth. 📌 Key takeaways: 1⃣ 📖🧱 Reference-based evaluation still matters: constrained LLM judging helps, but human-grounded references remain essential until agents can consistently match human conclusions 2⃣ 🏆🧠 Expert-validated ground truth: all tasks come from recent NeurIPS / ICLR / ICML papers, with contamination carefully controlled 3⃣ 🔁🎭 Rediscovery, not reproduction: original 🧪 methods, 📊 experiments, 💻 implementations, and 📈 analyses are fully masked to create real discovery challenges 🔑 Key empirical findings: 💡 The "Science Gap" is Real: Even the best setup (Claude Code + Sonnet-4) caps out at an F1 score of 46.7. On hard tasks, agents struggle to break 30 💡 Success is a "Lottery": Performance has incredibly high variance. Reliability is a major unsolved issue. 💡 Coding is no longer the bottleneck; high-level reasoning and analysis are: ~74% of errors stem from flawed planning, not coding ⚙️ How it works: 🔹 Research-Problem Trees: We parse papers into trees (from broad roots to concrete leaves). This allows us to select intermediate nodes that perfectly balance open-ended exploration with verifiable ground truth. 🔹 Claim-Level Evaluation: We match AI conclusions against human conclusions using granular claim decomposition (F1 score). 🔹 Creativity Check: We score false positives to see if agents are finding novel truths (Spoiler🚨: they aren’t creative yet). 🔹 New Diagnostic Taxonomy: failures traced across four stages: 🧠 Planning → 🛠️ Implementation → ▶️ Execution → 🧾 Conclusion 🔹 Additional Analyses: cost efficiency, contamination checks, and more. 👀 The Future: 🚀 Live-FIRE-Bench: a live, continuously updated FIRE-Bench to track real-time progress on the latest research (Newest LLMs should be benchmarked with the newest research) 🚀 Stronger scaffolding (search + planning + coding) 🧠🧰 and converting FIRE-Bench into interactive environments for training research agents 🚀 Toward real creativity: We want better systems that can produce genuinely novel conclusions toward creativity 🎨⏳ 🚀 Better systems 🧠✨ and better benchmarks 📏 must co-evolve 🔄 over time 📜🎥 Paper, video, demo, and research trees: 👉🌐 #AI 🤖 #MachineLearning 📚 #AI4Science 🔬 #LLMs 🧠 #Research 🧪 #AgenticAI 🚀 #FireBench 🔥

Zhen Wang

18,565 Aufrufe • vor 8 Monaten

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇
20:54

HERMES AGENT LEARNS FROM ITS OWN MISTAKES. UPDATES ITS MEMORY. CREATES ITS OWN SKILLS. NO CLOUD. EVERYTHING STORED LOCALLY. THIS IS HOW THE SELF-IMPROVING LOOP WORKS. most agents start from zero every session. Hermes carries forward what it learned. THREE MEMORY SYSTEMS: 1. PROCEDURAL MEMORY (how to act) stored in ~/.hermes/skills/ as SKILL.md files. when the agent repeats a complex workflow, it saves the procedure as a reusable skill. next time the same task comes up, it follows the skill instead of figuring it out again. you can also create skills explicitly: "create a skill called video-prep that captures how I format my video scripts. spoken english, define jargon inline, no em-dashes, close with a catchphrase." the agent writes the SKILL.md. available as a slash command from that moment. Hermes ships with 90+ skills. the number grows the longer you use it. 2. SEMANTIC MEMORY (durable facts about you) stored in ~/.hermes/memory/memory.md the agent scans conversations for facts worth remembering. preferences, habits, corrections, project details. real example from the video: agent tried to scrape a YouTube channel. URL was wrong. it failed. it updated memory.md with the correct URL pattern so it never makes the same mistake again. you can also save explicitly: "save to memory that my favorite testing framework is pytest" the agent updates memory.md immediately. this file loads into context on every session. the agent knows you better every week. 3. EPISODIC MEMORY (chat history) stored in ~/.hermes/state.db (local SQLite). every conversation. every tool call. every result. searchable with FTS5 full-text search. "search our past sessions. what was the first thing I ever said to you?" the agent queries state.db and finds it. over time, auxiliary models consolidate episodic memory into semantic memory. distilling recurring patterns into durable facts. THE SELF-IMPROVING LOOP: every agent run follows this cycle: → you send a prompt → working memory loads: SOUL.md + memory.md + relevant skills + chat history → agent calls tools (terminal, browser, delegate_task) → agent completes the task, replies to you → AFTER the reply: agent checks "did I learn something worth saving?" → if yes: updates memory.md or creates a new skill → next session starts smarter than the last this happens automatically. you don't ask the agent to learn. it decides what to remember on its own. WHAT MAKES THIS DIFFERENT FROM CLAUDE CODE: Claude Code has memory too. but Hermes stores everything locally. no cloud. your data never leaves your machine. Claude Code doesn't auto-create skills from experience. Hermes turns repeated workflows into reusable procedures. Claude Code memory is instruction-based. Hermes memory is conversational and self-updating. over months of usage, Hermes builds a knowledge base of your preferences, your projects, your mistakes, and the procedures that work for your specific workflow. the agent that remembers your birthday also remembers why your last deploy failed. NO EMBEDDINGS. PLAIN TEXT. Hermes does not use embeddings or RAG for memory. skill and memory search runs on plain text keyword matching. simpler. faster. no vector database to maintain. works entirely offline on your local machine. DELEGATE TO CLAUDE CODE: Hermes can spawn a sub-agent that runs Claude Code in headless mode: "spawn a sub-agent using Claude CLI to build a Python script that fetches the top 5 Hacker News stories to markdown." Hermes delegates. Claude Code writes the code. result returns to Hermes. Hermes runs the script and delivers the output. use Hermes for orchestration. use Claude Code for heavy coding. both tools. not competitors. WHAT HERMES DOES NOT HAVE: no built-in eval or LMOps system. no LangSmith, no LangFuse integration out of the box. trajectory export and logs exist but there is no automated quality tracking. if you need eval, build it yourself or connect external tools. the loop is self-improving. measuring how well it improves is on you. comment LOOP and I'll send you the configs that control how fast Hermes learns and what it remembers. memory limits, skill auto-creation triggers, and the auxiliary model that runs the learning. Replace your entire team with 8 hermes agents👇

YanXbt

22,720 Aufrufe • vor 2 Monaten

$AMD $5 Trillion is Inevitable LT| Agentic AI🧵 Agentic AI is the new $5 Trillion TAM 🚨🚨🚨 This thead will do Comp with $INTC and how to quantify this massive Agentic AI demand spike, and forcing Jensen to rush a CPU design. Global Agentic AI Market size is estimated to be $3-$5Trillion TAM by 2030(McKinsey) Quantifying the demand from agentic AI for AMD involves assessing the broader market growth for agentic systems, their unique computational requirements (particularly for CPUs in orchestration and reasoning tasks), and AMD's positioning very well through products like EPYC processors and partnerships. AMD EPYC Venice is the most superior choice in 2026-2027 for most Agentic AI workloads Agentic AI refers to autonomous AI agents that perform multi-step tasks, involving sequential logic, tool integration, and decision-making workloads that heavily rely on CPUs for handling orchestration, memory management, and context switching, rather than just GPU-parallelized training or batch inference. Agentic AI is often cited as 40-100x more "hungry" than traditional AI due to its continuous, 24/7 operation and complex workflows. This stems from factors like chain-of-thought reasoning (multiple LLM calls per query), API/tool interactions, memory management, and orchestration loops, which can generate 10-100x more tokens and require real-time responsiveness. For example, a single agentic query might trigger 5-20 model inferences, making it 10-20x more compute-intensive than simple chatbots, and the always-on nature compounds this to 40-100x overall. Nvidia's CEO has highlighted this as driving "easily 100x more computation" for inference in agentic/reasoning setups. AMD's EPYC Venice (6th Gen EPYC, codenamed "Venice") and Intel's Xeon 7 Diamond Rapids represent the pinnacle of server CPU technology in 2026, both targeting high-performance data center workloads like AI inference, agentic AI orchestration, cloud computing, and HPC. Venice builds on AMD's Zen 6 architecture, emphasizing core density and efficiency, while Diamond Rapids leverages Intel's Panther Cove P-cores for balanced performance. Both chips adopt similar advancements like 16-channel DDR5 memory and PCIe Gen 6, but differ in core counts, process nodes, and overall design philosophy. Intel has faced acute supply constraints across its Xeon lineup, including legacy nodes (Intel 7/3) and the ramping 18A process for next-gen parts. Intel shortage is expected with lead times up to 6 months or longer. 1. AMD EPYC Venice vs Intel Xeon 7 Diamond Rapids Architecture AMD: Zen 6 chiplet design with 8 CCDs and dual IODs Intel: Panther Cove P-cores; multi-die architecture with 4 compute tiles Core/Thread Count AMD: Up to 256 cores / 512 threads (Zen 6c variant) Intel: Up to 192 cores / 192 threads Process Node AMD: TSMC N2 (2nm) Intel: Intel 18A (1.8nm-class); in-house fab Memory Support AMD: 16-channel DDR5; up to 1.6 TB/s bandwidth. Intel: 16-channel DDR5 ; up to 1.6 TB/s bandwidth I/O and Connectivity AMD: PCIe Gen 6 (up to 128 lanes); twice the CPU-to-GPU bandwidth Intel: PCIe Gen 6 (up to 128 lanes); LGA 9324 socket Power (TDP) AMD: Starting 400-500W, potentially lower due to efficiency gains from TSMC 2nm Intel: Starting 400-500W, as it targets competitive efficiency Performance Projections AMD: Up to 70% uplift vs. 5th Gen Turin (1.7x in multi-threaded/AI tasks) Intel: ~40% faster than Granite Rapids (Xeon 6, 128-core). Lags AMD in per-core perf and 40-50% behind Venice core-for-core comp Target Workloads AMD: AI inference/orchestration, HPC, cloud virtualization. Partnerships Intel: Hyperscale AI, general enterprise. Custom silicon Pricing: AMD: estimated $10k-$20k for top SKUs Intel: estimated $8-$18k Availability: AMD: Significant Ramp H2 2026 due to higher allocation from TSMC Intel: H1-H2 2026 delayed, but trying to catch up Overall: ~Venice's 256 cores provide a 33% edge over Diamond Rapids' 192, making it superior for massively parallel tasks like AI training/inference or virtualization ~TSMC's N2 vs. Intel 18A debates rage on which is "better," but AMD's mature chiplet approach yields better density ( 32 cores/CCD vs. Intel's 48/tile). Venice's redesign reduces latency, aiding agentic AI where CPUs handle orchestration ~ Early projections show Venice widening AMD's lead matching or exceeding Diamond Rapids' perf with fewer watts in multi-threaded benchmarks. Intel's no-SMT design (to prioritize AI) handicaps it vs. AMD's 512 threads, though Clearwater Forest (E-core) could compete in density-focused niches. ~Power & Cooling: Both push above 400-500W, demanding liquid cooling. ~AMD been taking market share now above 40%. AMD EPYC Venice emerges as the superior choice in 2026 for most server workloads. Its higher core/thread count (256/512 vs. 192/192), stronger per-core performance, and architecture optimized for AI-driven tasks (agentic orchestration with GPU integration) provide decisive advantages in throughput, scalability, and efficiency. Projections indicate Venice delivering 1.7x the performance of prior gens while widening the gap over Intel ( 40-70% leads in multi-threaded benchmarks). AMD's fabless model with TSMC ensures reliable scaling, and its ecosystem ( open ROCm) appeals to AI adopters. Intel's Diamond Rapids is competitive in single-threaded enterprise apps and custom hyperscale ( NVLink), with potential fab advantages for supply/security. However, without SMT and lower density, it falls short in core-for-core battles—exposing Intel to another generation of AMD dominance unless 18A yields surprise efficiency gains. For data centers prioritizing raw compute ( AI, HPC), Venice wins; for Intel-centric ecosystems or specialized I/O, Diamond Rapids holds ground. Real benchmarks post-launch will confirm, but logic points to AMD pulling ahead. 2. Market size , Potential Revenue and Supply Global Agentic AI market size is projected to be $3-$5 Trillion by 2030 according to McKinsey, where consensus points to 40-50% CAGR driven by small to large enterprise demand. I also wrote a full thread on how and why Agentic AI is so explosive that AMD will blow all anlaysts estimate for subscribers. Link below if you are interested. AMD's data center segment hit a record $5.4B in Q4 2025 (up 39% YoY), with EPYC shipments ramping due to agentic demand. With 2GW of deployment in H2 2026, AMD AI data center revenue has $40-$50B+ at the lowest or most conservative projection; or Total Revenue in the $77-$94B For FY2026. However, Agentic AI massive demand spike could send EPYC revenue 3x to 4x in the next few years, potentially surpassing MI series GPU demand as enterprises prioritize CPU-dense Rack setups. This is pushing $NVDA Jensen to rush a CPU design and acquired Groq, a new CPU player due to this massive TAM. Noted that this is just popping just in weeks, highlighting we are just so early in this AI Supercycle and the pace of adoption is insane, and clearly productivity will skyrocket. Why? Because Agentic AI is 24/7 Smart AI agent working for you or your businesses is a mad compelling, and it is estimated to be 40-100x more Inference Hugnry! Many experts already said it is impossible to project this kind of Inference Demand. AI CapEx is expected to ramp up even more in 2027-2028-2029 and 2030 as Global Agentic AI is going to scale to $3-$5 Trillion TAM by 2030. The nature of Agentic is driving higher CPU/GPU ratio, with CPUs handling 50-90% of Agentic workflows. For example, The current Helios Rack: 18 compute trays per rack with 72 GPUs + 18 CPUs. The beauty of this $META and $AMD long term partnership is, that it is absolutely flexible to adjust racks to higher CPU rato or equal to service different needs. Helios rack can be easily swap to 2 GPUs 2CPUs or even CPUs only trays for dedicated orchestration/head nodes. You see, the beauty of this open rack-scale is flexibility and evolvability. If Agentic AI demand pushes much higher, AMD should be able to adjust variant trays without abandoning Heilos Rack. We can't talk just about massive Agentic AI demand without talking about the Supply side or TSMC. TSMC, AMD's primary foundry for advanced nodes ( Zen 6/Venice on N2/2nm), is addressing AI-driven shortages through massive expansions. TSMC accelerates fab construction with up to 10 facilities targeted for 2026. TSMC is accelerating its domestic manufacturing expansion, with industry sources indicating that as many as ten fabs could be under construction or preparing to begin operations across Taiwan’s major science parks. TSMC Capex: $52-56B in 2026 (up 37% YoY), with $45B already approved for new/upgraded capacities. 70-80% for advanced processes (2nm/A16), 10-20% for packaging (CoWoS quadrupling to 120-140K wafers/month by late 2026). In addition, Taiwanese companies (led by TSMC) commit to at least $250B in direct investments in US-based advanced semiconductor, AI, and energy production/innovation capacity.Taiwan provides $250B in government credit guarantees to facilitate additional investments and build a full US semiconductor ecosystem (including industrial parks). TSMC completed a second land purchase in Arizona (January 2026) for gigafab scaling, with an additional $100B+ (potentially four more modules) to further expand and qualify for tariff exemptions. AMD with secured 12GW from OpenAI and $META and massive Agentic AI will mean higher priority acess to 20-30% more wafers on TSMC advanced nodes, as TSMC has multi-year agreements with AMD for AI chips. Dr. C. C. Wei, CEO of TSMC quote: "I spend a lot of time in the last three or four months talking to my customer and then customers. Customer. I want to make sure that my customers demand are real. I talk to those cloud service providers, all of them. Their answer is. I'm quite satisfied with their answer. Actually they show me the evidence that the AI really help their business. So they grow their business successfully and he or she in their financial return. So I also double check their financial status. They are very rich." Amid shortages, the US buildout ensures AMD can ramp production of Instinct GPUs and EPYC CPUs without the constraints hitting competitors like Intel. By diversifying away from Taiwan (85% of advanced nodes today), the agreement mitigates supply disruptions, ensuring stable flows for AMD's chips. Scaling production and securing supply will matter for AMD the most in the next 5-10 years growth. The growth could be 80-100% YoY or higher; or it could be in the 60%. The aggressive TSMC supply ramp is reassuring the higher growth point. Conclusion: AMD stands at a pivotal inflection point in 2026, where the explosive rise of agentic AI demanding 40-100x more inference compute through its 24/7, multi-step orchestration positions the company to potentially triple its EPYC CPU revenue to $45-60B+ by 2028 while scaling Instinct GPUs to tens of billions annually by 2027. Agentic AI demand could push AI CapEx closer to $1 Trillion in 2027, far higher than most estimates. Dr. Lisa Su, AMD's visionary CEO, is masterfully securing supply to harness this massive demand by prioritizing operational execution and deep TSMC collaboration, ensuring readiness for the second-half 2026 AI ramp. Dr. Su has explicitly called out surging EPYC demand for agentic tasks where CPUs power head nodes and traditional workloads alongside GPUs while guiding for data center dominance through proactive capacity planning and partnerships like Nutanix ($150M investment for open agentic platforms) or providing tens of millions CPUs for OpenAI, $META, $ORCL, $AMZN, $MSFT, $GOOGL and others. Her strategy includes multi-year TSMC agreements for advanced nodes (N2 for Venice CPUs and future Instincts), diversifying beyond Taiwan to mitigate risks, and unveiling innovations like the MI455X GPU at CES 2026, which she touted as enabling "the next trillion-dollar market opportunity" in physical AI. Dr. Su's forward-looking vision predicting AI reaching 5 billion users emphasizes "AI everywhere," backed by hardware like Ryzen AI chips, all while declaring demand "going through the roof" and committing to scale without bottlenecks. TSMC's aggressive ramp-up, fueled by $52-56B in 2026 capex (up 37% YoY) and 10+ new fabs across Taiwan, the US (Arizona cluster expanding to 6+ modules with $165B+ investment), Japan, and Europe, provides profound reassurance for AMD's supply stability. The January 2026 US-Taiwan agreement committing $250B in investments and credit guarantees for US reshoring accelerates this, granting tariff relief (15% rates with 1.5-2.5x exemptions) tied to capacity buildouts, enabling TSMC to potentially double output over the decade to meet AI wafer hunger. This translates to 20-30% higher wafer allocations on key nodes, sidestepping Intel-like shortages and empowering Dr. Su's team to deliver on hyperscaler demands without disruption. Ultimately, this synergy cements AMD's leadership in the agentic era, promising sustained growth, $5T+ valuations at scale, and a resilient path forward as AI reshapes the world. This is NOT Financial Advice! Video source: AMD CES 2026
2:49

$AMD $5 Trillion is Inevitable LT| Agentic AI🧵 Agentic AI is the new $5 Trillion TAM 🚨🚨🚨 This thead will do Comp with $INTC and how to quantify this massive Agentic AI demand spike, and forcing Jensen to rush a CPU design. Global Agentic AI Market size is estimated to be $3-$5Trillion TAM by 2030(McKinsey) Quantifying the demand from agentic AI for AMD involves assessing the broader market growth for agentic systems, their unique computational requirements (particularly for CPUs in orchestration and reasoning tasks), and AMD's positioning very well through products like EPYC processors and partnerships. AMD EPYC Venice is the most superior choice in 2026-2027 for most Agentic AI workloads Agentic AI refers to autonomous AI agents that perform multi-step tasks, involving sequential logic, tool integration, and decision-making workloads that heavily rely on CPUs for handling orchestration, memory management, and context switching, rather than just GPU-parallelized training or batch inference. Agentic AI is often cited as 40-100x more "hungry" than traditional AI due to its continuous, 24/7 operation and complex workflows. This stems from factors like chain-of-thought reasoning (multiple LLM calls per query), API/tool interactions, memory management, and orchestration loops, which can generate 10-100x more tokens and require real-time responsiveness. For example, a single agentic query might trigger 5-20 model inferences, making it 10-20x more compute-intensive than simple chatbots, and the always-on nature compounds this to 40-100x overall. Nvidia's CEO has highlighted this as driving "easily 100x more computation" for inference in agentic/reasoning setups. AMD's EPYC Venice (6th Gen EPYC, codenamed "Venice") and Intel's Xeon 7 Diamond Rapids represent the pinnacle of server CPU technology in 2026, both targeting high-performance data center workloads like AI inference, agentic AI orchestration, cloud computing, and HPC. Venice builds on AMD's Zen 6 architecture, emphasizing core density and efficiency, while Diamond Rapids leverages Intel's Panther Cove P-cores for balanced performance. Both chips adopt similar advancements like 16-channel DDR5 memory and PCIe Gen 6, but differ in core counts, process nodes, and overall design philosophy. Intel has faced acute supply constraints across its Xeon lineup, including legacy nodes (Intel 7/3) and the ramping 18A process for next-gen parts. Intel shortage is expected with lead times up to 6 months or longer. 1. AMD EPYC Venice vs Intel Xeon 7 Diamond Rapids Architecture AMD: Zen 6 chiplet design with 8 CCDs and dual IODs Intel: Panther Cove P-cores; multi-die architecture with 4 compute tiles Core/Thread Count AMD: Up to 256 cores / 512 threads (Zen 6c variant) Intel: Up to 192 cores / 192 threads Process Node AMD: TSMC N2 (2nm) Intel: Intel 18A (1.8nm-class); in-house fab Memory Support AMD: 16-channel DDR5; up to 1.6 TB/s bandwidth. Intel: 16-channel DDR5 ; up to 1.6 TB/s bandwidth I/O and Connectivity AMD: PCIe Gen 6 (up to 128 lanes); twice the CPU-to-GPU bandwidth Intel: PCIe Gen 6 (up to 128 lanes); LGA 9324 socket Power (TDP) AMD: Starting 400-500W, potentially lower due to efficiency gains from TSMC 2nm Intel: Starting 400-500W, as it targets competitive efficiency Performance Projections AMD: Up to 70% uplift vs. 5th Gen Turin (1.7x in multi-threaded/AI tasks) Intel: ~40% faster than Granite Rapids (Xeon 6, 128-core). Lags AMD in per-core perf and 40-50% behind Venice core-for-core comp Target Workloads AMD: AI inference/orchestration, HPC, cloud virtualization. Partnerships Intel: Hyperscale AI, general enterprise. Custom silicon Pricing: AMD: estimated $10k-$20k for top SKUs Intel: estimated $8-$18k Availability: AMD: Significant Ramp H2 2026 due to higher allocation from TSMC Intel: H1-H2 2026 delayed, but trying to catch up Overall: ~Venice's 256 cores provide a 33% edge over Diamond Rapids' 192, making it superior for massively parallel tasks like AI training/inference or virtualization ~TSMC's N2 vs. Intel 18A debates rage on which is "better," but AMD's mature chiplet approach yields better density ( 32 cores/CCD vs. Intel's 48/tile). Venice's redesign reduces latency, aiding agentic AI where CPUs handle orchestration ~ Early projections show Venice widening AMD's lead matching or exceeding Diamond Rapids' perf with fewer watts in multi-threaded benchmarks. Intel's no-SMT design (to prioritize AI) handicaps it vs. AMD's 512 threads, though Clearwater Forest (E-core) could compete in density-focused niches. ~Power & Cooling: Both push above 400-500W, demanding liquid cooling. ~AMD been taking market share now above 40%. AMD EPYC Venice emerges as the superior choice in 2026 for most server workloads. Its higher core/thread count (256/512 vs. 192/192), stronger per-core performance, and architecture optimized for AI-driven tasks (agentic orchestration with GPU integration) provide decisive advantages in throughput, scalability, and efficiency. Projections indicate Venice delivering 1.7x the performance of prior gens while widening the gap over Intel ( 40-70% leads in multi-threaded benchmarks). AMD's fabless model with TSMC ensures reliable scaling, and its ecosystem ( open ROCm) appeals to AI adopters. Intel's Diamond Rapids is competitive in single-threaded enterprise apps and custom hyperscale ( NVLink), with potential fab advantages for supply/security. However, without SMT and lower density, it falls short in core-for-core battles—exposing Intel to another generation of AMD dominance unless 18A yields surprise efficiency gains. For data centers prioritizing raw compute ( AI, HPC), Venice wins; for Intel-centric ecosystems or specialized I/O, Diamond Rapids holds ground. Real benchmarks post-launch will confirm, but logic points to AMD pulling ahead. 2. Market size , Potential Revenue and Supply Global Agentic AI market size is projected to be $3-$5 Trillion by 2030 according to McKinsey, where consensus points to 40-50% CAGR driven by small to large enterprise demand. I also wrote a full thread on how and why Agentic AI is so explosive that AMD will blow all anlaysts estimate for subscribers. Link below if you are interested. AMD's data center segment hit a record $5.4B in Q4 2025 (up 39% YoY), with EPYC shipments ramping due to agentic demand. With 2GW of deployment in H2 2026, AMD AI data center revenue has $40-$50B+ at the lowest or most conservative projection; or Total Revenue in the $77-$94B For FY2026. However, Agentic AI massive demand spike could send EPYC revenue 3x to 4x in the next few years, potentially surpassing MI series GPU demand as enterprises prioritize CPU-dense Rack setups. This is pushing $NVDA Jensen to rush a CPU design and acquired Groq, a new CPU player due to this massive TAM. Noted that this is just popping just in weeks, highlighting we are just so early in this AI Supercycle and the pace of adoption is insane, and clearly productivity will skyrocket. Why? Because Agentic AI is 24/7 Smart AI agent working for you or your businesses is a mad compelling, and it is estimated to be 40-100x more Inference Hugnry! Many experts already said it is impossible to project this kind of Inference Demand. AI CapEx is expected to ramp up even more in 2027-2028-2029 and 2030 as Global Agentic AI is going to scale to $3-$5 Trillion TAM by 2030. The nature of Agentic is driving higher CPU/GPU ratio, with CPUs handling 50-90% of Agentic workflows. For example, The current Helios Rack: 18 compute trays per rack with 72 GPUs + 18 CPUs. The beauty of this $META and $AMD long term partnership is, that it is absolutely flexible to adjust racks to higher CPU rato or equal to service different needs. Helios rack can be easily swap to 2 GPUs 2CPUs or even CPUs only trays for dedicated orchestration/head nodes. You see, the beauty of this open rack-scale is flexibility and evolvability. If Agentic AI demand pushes much higher, AMD should be able to adjust variant trays without abandoning Heilos Rack. We can't talk just about massive Agentic AI demand without talking about the Supply side or TSMC. TSMC, AMD's primary foundry for advanced nodes ( Zen 6/Venice on N2/2nm), is addressing AI-driven shortages through massive expansions. TSMC accelerates fab construction with up to 10 facilities targeted for 2026. TSMC is accelerating its domestic manufacturing expansion, with industry sources indicating that as many as ten fabs could be under construction or preparing to begin operations across Taiwan’s major science parks. TSMC Capex: $52-56B in 2026 (up 37% YoY), with $45B already approved for new/upgraded capacities. 70-80% for advanced processes (2nm/A16), 10-20% for packaging (CoWoS quadrupling to 120-140K wafers/month by late 2026). In addition, Taiwanese companies (led by TSMC) commit to at least $250B in direct investments in US-based advanced semiconductor, AI, and energy production/innovation capacity.Taiwan provides $250B in government credit guarantees to facilitate additional investments and build a full US semiconductor ecosystem (including industrial parks). TSMC completed a second land purchase in Arizona (January 2026) for gigafab scaling, with an additional $100B+ (potentially four more modules) to further expand and qualify for tariff exemptions. AMD with secured 12GW from OpenAI and $META and massive Agentic AI will mean higher priority acess to 20-30% more wafers on TSMC advanced nodes, as TSMC has multi-year agreements with AMD for AI chips. Dr. C. C. Wei, CEO of TSMC quote: "I spend a lot of time in the last three or four months talking to my customer and then customers. Customer. I want to make sure that my customers demand are real. I talk to those cloud service providers, all of them. Their answer is. I'm quite satisfied with their answer. Actually they show me the evidence that the AI really help their business. So they grow their business successfully and he or she in their financial return. So I also double check their financial status. They are very rich." Amid shortages, the US buildout ensures AMD can ramp production of Instinct GPUs and EPYC CPUs without the constraints hitting competitors like Intel. By diversifying away from Taiwan (85% of advanced nodes today), the agreement mitigates supply disruptions, ensuring stable flows for AMD's chips. Scaling production and securing supply will matter for AMD the most in the next 5-10 years growth. The growth could be 80-100% YoY or higher; or it could be in the 60%. The aggressive TSMC supply ramp is reassuring the higher growth point. Conclusion: AMD stands at a pivotal inflection point in 2026, where the explosive rise of agentic AI demanding 40-100x more inference compute through its 24/7, multi-step orchestration positions the company to potentially triple its EPYC CPU revenue to $45-60B+ by 2028 while scaling Instinct GPUs to tens of billions annually by 2027. Agentic AI demand could push AI CapEx closer to $1 Trillion in 2027, far higher than most estimates. Dr. Lisa Su, AMD's visionary CEO, is masterfully securing supply to harness this massive demand by prioritizing operational execution and deep TSMC collaboration, ensuring readiness for the second-half 2026 AI ramp. Dr. Su has explicitly called out surging EPYC demand for agentic tasks where CPUs power head nodes and traditional workloads alongside GPUs while guiding for data center dominance through proactive capacity planning and partnerships like Nutanix ($150M investment for open agentic platforms) or providing tens of millions CPUs for OpenAI, $META, $ORCL, $AMZN, $MSFT, $GOOGL and others. Her strategy includes multi-year TSMC agreements for advanced nodes (N2 for Venice CPUs and future Instincts), diversifying beyond Taiwan to mitigate risks, and unveiling innovations like the MI455X GPU at CES 2026, which she touted as enabling "the next trillion-dollar market opportunity" in physical AI. Dr. Su's forward-looking vision predicting AI reaching 5 billion users emphasizes "AI everywhere," backed by hardware like Ryzen AI chips, all while declaring demand "going through the roof" and committing to scale without bottlenecks. TSMC's aggressive ramp-up, fueled by $52-56B in 2026 capex (up 37% YoY) and 10+ new fabs across Taiwan, the US (Arizona cluster expanding to 6+ modules with $165B+ investment), Japan, and Europe, provides profound reassurance for AMD's supply stability. The January 2026 US-Taiwan agreement committing $250B in investments and credit guarantees for US reshoring accelerates this, granting tariff relief (15% rates with 1.5-2.5x exemptions) tied to capacity buildouts, enabling TSMC to potentially double output over the decade to meet AI wafer hunger. This translates to 20-30% higher wafer allocations on key nodes, sidestepping Intel-like shortages and empowering Dr. Su's team to deliver on hyperscaler demands without disruption. Ultimately, this synergy cements AMD's leadership in the agentic era, promising sustained growth, $5T+ valuations at scale, and a resilient path forward as AI reshapes the world. This is NOT Financial Advice! Video source: AMD CES 2026

Mike

44,460 Aufrufe • vor 6 Monaten

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?
38:45

Local AI 101: open models, Hugging Face, and businesses to build (38 min masterclass) I still think cloud AI is the default for most things, and honestly it should be, the frontier models are the strongest and easiest to use. But something shifted in the last 4-5 months. You can now run genuinely good open models directly on your own laptop, or even your phone. And once you actually try it, it changes how you think about what AI is even for. LOCAL AI, CLEARLY EXPLAINED: 1. The model is the brain doing the thinking. Gemma, Llama, Mistral, and Qwen are the main families, and each is better at different things, some at reasoning, some at coding, some small enough to run on a phone. 2. Hugging Face is the warehouse where you find them. You go there to see what each model is good at, check the license, and grab the compressed versions that run on a normal computer. 3. The software is what runs the model on your machine. Start with LM Studio if you're not technical, it feels like a normal app where you search, download, and start chatting. Ollama is the one you reach for when you want to plug a model into your own apps. 4. The workflow is the actual product you build on top of it all. That's what I'm ideating around for some businesses to create. I think local AI just made a specific kind of business way easier to start. Find an industry that: 1. Sits on sensitive data they'd never paste into ChatGPT 2. Does the same review over and over 3. Runs on software from 2003 Then build a local AI tool that does that review on their own machine, so the data never leaves the building! Take home health agencies. Nurses write visit notes all day, and if a note is missing a detail, the billing gets denied or the audit flags it. Here's how I'd start: 1. Find 5 small agencies. Offer to review a batch of their notes for them. 2. Run the notes through Gemma locally (free, private, no cloud). Read every output yourself. 3. Write down the 20 issues that keep showing up: missing vitals, vague med changes, notes that don't support the billed level. 4. That list of 20 is your checklist. The checklist is the product. 5. Turn it into a local desktop app that flags those 20 things before a note gets submitted. You just went from a service anyone could offer to a product nobody else has, and you learned exactly what to build by doing the work by hand first. Same recipe works for restoration contractors (draft the damage report on-site before the tech leaves) and wealth advisors (catch the compliance landmine in a client email before it sends). Basically the framework is sensitive data, repeated review, ancient software. I think there are tons of businesses like this! Almost none of it clicked for me until I actually started using local AI. So if you take one thing from this, go run a model on your own machine once. Also a fun thing to try with your friends. Feel free to send this to a friend. The episode is live for free on The Startup Ideas Podcast (SIP) 🧃 (thanks to Google for sponsoring today's episode and supporting local AI) I feel like local AI one of those things you need to try for it to really click. Run one model on your own machine and you'll see what I mean! I go way deeper in the full 38 minute masterclass, the models, the setup, and the businesses to build. Link below. LINK TO WATCH: OR WATCH BELOW ON X What do you think of local AI?

GREG ISENBERG

32,410 Aufrufe • vor 17 Tagen