正在加载视频...

视频加载失败

We keep defaulting to the biggest model in the room every time we touch AI in our apps. Claude, GPT, Gemini. Cloud or nothing. But the browser is already more capable than most people realize: WebAI and WebMCP may change this. With WebAI you can run models client-side. With...

14,824 次观看 • 5 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Hermes just made its in-app browser a whole lot more useful. You can now keep multiple browser tabs open inside Hermes Desktop instead of every new page replacing the one you were already using. And that matters more than it sounds. Because this is not just about “having tabs.” It means Hermes can work across multiple pages without forcing you to keep losing your place every time you open the next thing. Research one source, keep it open, open another tab, compare them side by side, and keep moving. Check a few products before buying something. Look at multiple hotel or travel options at once. Keep a YouTube tutorial open in one tab while Hermes looks through docs or another page in the next. And because this lives inside Hermes Desktop, you are not limited to one basic browser view either. You can keep multiple tabs open. You can view two pages side by side. You can stack them top and bottom. You can even run a four-panel view when you want several pages open at once. So the browser inside Hermes is starting to feel a lot more like a real workspace instead of one page you keep replacing. There is also some nice polish that comes with it. Browser tabs now label themselves based on the page, and the address bar behaves more cleanly while pages are loading. And remember, this is the same in-app browser Hermes can already read, click through, type in, scroll, and annotate. So this is not just a prettier browser. It is a more capable workspace for the browser Hermes is actually using. If Hermes is going to do more of your work on the web, this is exactly the kind of browser upgrade it needed.

Hermes Release Watch

52,493 次观看 • 25 天前

🚨 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 次观看 • 15 天前