Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Hermes Agent now has a production-grade WhatsApp Business Cloud integration: use it as a private WhatsApp bot for yourself or your team, or configure it for customer-facing support. Connect an existing WhatsApp Business Cloud number or create one through Meta Business Manager, then run 'hermes whatsapp-cloud' to wire it... show more

Nous Research

234,667 subscribers

187,211 views • 1 month ago •via X (Twitter)

Education Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

THIS DEVELOPER USED OPENCLAW AGENTS TO RUN HIS B2B BUSINESS VIA TELEGRAM AND MADE $15,000/MONTH he doesn't write prompts from scratch or use generic browser interfaces. he runs a multi-agent framework through a mobile chat. the agents write code, test deployments, and update sites in real-time while he just hits approve the setup is straightforward: - spin up Coolify on a free cloud instance to host your own self-hosted agent panels - link the agent loop to a Telegram gateway to approve code edits from your phone - deploy specialized skill files directly to limit token waste and context decay - containerize the terminal execution using Docker to prevent security breaches if you are still running local agents without container safety, you are leaving money on the table. read the 30-day battle between OpenClaw and Hermes Agent to see who actually wins in production Full breakdown and migration playbook ↓

THIS DEVELOPER USED OPENCLAW AGENTS TO RUN HIS B2B BUSINESS VIA TELEGRAM AND MADE $15,000/MONTH he doesn't write prompts from scratch or use generic browser interfaces. he runs a multi-agent framework through a mobile chat. the agents write code, test deployments, and update sites in real-time while he just hits approve the setup is straightforward: - spin up Coolify on a free cloud instance to host your own self-hosted agent panels - link the agent loop to a Telegram gateway to approve code edits from your phone - deploy specialized skill files directly to limit token waste and context decay - containerize the terminal execution using Docker to prevent security breaches if you are still running local agents without container safety, you are leaving money on the table. read the 30-day battle between OpenClaw and Hermes Agent to see who actually wins in production Full breakdown and migration playbook ↓

marfin

26,654 views • 1 month ago

THESE 5 SKILLS TURN HERMES AGENT INTO A SELF-RUNNING POWERHOUSE - ON NOUS RESEARCH’S #1 AGENT ON OPENROUTER. Hermes already writes its own skills and remembers across sessions. These 5 from the community ecosystem push it further - drop them in ~/.hermes/skills/ and go. ANTHROPIC-CYBERSECURITY-SKILLS (4K★) by mukul975 · production the most comprehensive security skill pack in the ecosystem. what it adds: → 753+ structured cybersecurity skills mapped to MITRE ATT&CK → also covers NIST CSF 2.0, MITRE ATLAS, D3FEND & NIST AI RMF → turns Hermes into a recon + defense analyst, not a guesser → install: hermes skills install from the hub the workhorse of the list - start here. CHAINLINK-AGENT-SKILLS by Chainlink - official · production low profile, highest trust: it’s first-party from Chainlink itself. what it adds: → oracle network data, CCIP, smart-contract interaction skills → built on the spec - portable across clients → teaches the agent correct on-chain calls instead of hallucinated ABIs → official source, security-scanned on install stop letting the model guess your contract reads. HERMES-SKILL-FACTORY by Romanescu11 · beta the meta-layer - a skill that makes more skills. what it adds: → point it at any repetitive task → it auto-generates a reusable skill → stacks on top of Hermes’s own learning loop → turns your workflows into a self-growing skill library → install from the awesome-hermes-agent list this is what compounds your setup over time. AGENTCASH by Merit-Systems · beta the connector that gives your agent a wallet. what it adds: → access to 300+ premium APIs through one skill → pays for them via x402 or MPP - free USDC to start testing → web scraping, image gen, email sending - all behind one auth → a fresh Hermes + AgentCash alone is already dangerous the cleanest way to plug in paid tools. X-TWITTER-SCRAPER by Xquik-dev · beta drives typed X access through 43 narrow SKILL.md folders. what it adds: → reads (search, timelines, mentions, trends, bookmarks, for-you) → writes (post, DM, follow, profile) + bulk extraction (followers, lists, spaces) → AI composition: write-tweets, write-threads, optimize → security-scanned before it’s trusted feed its output straight into your scheduled briefings. BONUS - the registry itself: HERMESHUB by amanning3390. Browse, search, and install community skills with a 65+ rule security scanner - blocks prompt injection and data exfiltration before anything runs. Creator marketplace with x402/Stripe payments. hermes skills browse to start. If you install nothing else, wire up the hub. the stack in one line: hermeshub + skill-factory build & manage the library → cybersecurity + chainlink + agentcash + x-scraper give it real-world reach → Hermes runs it all on a $5 VPS while you sleep. which of these are you running? FULL HERMES SKILL-STACK PLAYBOOK 👇

ZEUS⚡️

21,067 views • 29 days ago

Did you know you can access Camera Track as a standalone feature in Autodesk Flow Studio (formerly Wonder Studio)? Forget the wait or wasted credits required to run an entire Live Action project. Extract your camera track with included point cloud data and added support for footage with no actors - directly from the Wonder Tools library. 🌟Try it now: #WonderTools #WonderDynamics #AutodeskFlowStudio #VFXWorkflow #AI

Did you know you can access Camera Track as a standalone feature in Autodesk Flow Studio (formerly Wonder Studio)? Forget the wait or wasted credits required to run an entire Live Action project. Extract your camera track with included point cloud data and added support for footage with no actors - directly from the Wonder Tools library. 🌟Try it now: #WonderTools #WonderDynamics #AutodeskFlowStudio #VFXWorkflow #AI

Wonder Dynamics

14,729 views • 1 year ago

Karpathy's Agentic Engineering finally has proper tooling! (built by Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.

Karpathy's Agentic Engineering finally has proper tooling! (built by Google) Karpathy defined agentic engineering as the discipline that separates production agent work from vibe coding. The core skills he listed were spec design, eval loops, and security oversight. The problem has been that practicing this still requires a different tool for every phase: - editor for code - a terminal for scaffolding - a browser for testing - a cloud console for deployment - and a separate framework for evals. Every transition is a context switch. The solution to production-grade Agentic Engineering is now actually implemented in Google’s Agents CLI. It covers the entire workflow in one place for scaffolding, evaluating, and deploying ADK agents. One setup command injects 7 ADK-specific skills into a coding agent's context, which lets it handle scaffolding, evals, deployment, and enterprise registration through natural language. I tested this end-to-end by building a RAG agent from scratch using Claude Code. It scaffolded the full project from the ADK agentic_rag template, generated 20 eval scenarios with LLM-as-judge scoring, and returned a quantitative scorecard. Finally, it also deployed everything to Agent Runtime and registered the agent to Gemini Enterprise, so the entire org can discover and use it. The video below shows this in action, and I worked with the Google Cloud team to put this together. Agents CLI GitHub repo → (don't forget to star it ⭐ ) I wrote up the full build covering all six steps from install to enterprise registration. It includes the eval scorecard, the instruction loophole the eval caught before deployment, and what the deployment process actually looks like end-to-end. Read it below.

Akshay 🚀

255,129 views • 18 days ago

Startups achieve success slowly, building their company brick by brick. Founders can develop marketing leverage by building a viral or network effects strategy or… by partnering with larger companies who have great distribution themselves and trying to reach through to the end customer with premium offerings. Companies that build their distribution by coming in at a lower than market price should follow up with higher margin products or they will find themselves in a competition that we call “a race to the bottom.” It is mission critical for startups to work to build distribution and market share, but they need to then provide something that their customers can’t live without, and charge enough for it to support the continued distribution strategy. Startup founders: Look at every customer as a long-term partner, because you want your business to be a long-term survivor. Look at every supplier as a long-term partner and make sure they are healthy. Look at every employee as a long-term partner. You want them to grow with you and with the business.

Startups achieve success slowly, building their company brick by brick. Founders can develop marketing leverage by building a viral or network effects strategy or… by partnering with larger companies who have great distribution themselves and trying to reach through to the end customer with premium offerings. Companies that build their distribution by coming in at a lower than market price should follow up with higher margin products or they will find themselves in a competition that we call “a race to the bottom.” It is mission critical for startups to work to build distribution and market share, but they need to then provide something that their customers can’t live without, and charge enough for it to support the continued distribution strategy. Startup founders: Look at every customer as a long-term partner, because you want your business to be a long-term survivor. Look at every supplier as a long-term partner and make sure they are healthy. Look at every employee as a long-term partner. You want them to grow with you and with the business.

Tim Draper

10,607 views • 1 year ago

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

HERMES AGENT HAS A SECOND BRAIN. 1,100+ KNOWLEDGE FILES. AUTO-LINKED. SELF-IMPROVING. GROWING EVERY NIGHT. THIS IS THE OBSIDIAN GRAPH BEHIND IT. every dot = one knowledge file (markdown) every line = one wiki-link between files every color = one category (skills, notes, decisions, sources, entities) HOW IT BUILDS ITSELF: Hermes ships with a bundled LLM Wiki skill. based on Andrej Karpathy's pattern. unlike RAG (rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. when you feed the agent a source: → it reads the content → writes a structured markdown page → auto-links to every related existing page → flags contradictions with previous entries → updates all affected pages one source in. multiple connections created. the graph grows denser with every entry. WHAT FEEDS THE WIKI: → articles and URLs you find interesting → meeting transcripts → PDF documents and research papers → conversation history from Hermes sessions → Claude Code and Codex session history → Slack logs, email threads, saved notes → YouTube transcripts → raw text dropped into a _raw/ folder the obsidian-wiki package supports multi-agent ingest from Hermes, Claude Code, Codex, OpenClaw, Pi, Windsurf, and ChatGPT exports. install: pip install obsidian-wiki obsidian-wiki setup --vault ~/wiki AUTOMATE THE GROWTH: set cron jobs to feed the wiki overnight: "every day at 9am, check for new meetings. ingest transcripts into the wiki." "every week, check arXiv for new papers in [niche]. summarize and file into the wiki." "every day, ingest today's Hermes sessions into the wiki under session-history." month 1: 50 entries. scattered. month 3: 300+ entries. cross-referenced. month 6: 1,000+ entries. the agent surfaces patterns you never searched for. WHY OBSIDIAN: the wiki is plain markdown files. no database. no lock-in. open it in Obsidian for graph view: → nodes show knowledge density → links show how ideas connect → clusters reveal your strongest domains → orphan nodes reveal gaps Hermes writes from a VPS. Obsidian reads on your laptop. obsidian-headless syncs without a GUI. agent writes from the server, you browse on your device. FOUR MEMORY LAYERS: Layer 1: memory.md + user.md (~2,200 + 1,375 chars. short-term.) Layer 2: SQLite with FTS5 (full session transcripts. searchable.) Layer 3: external providers (Mem0, SuperMemory, Honcho. optional.) Layer 4: Obsidian wiki via LLM Wiki skill (unlimited. compounding. the long-term brain.) layers 1-3 handle memory. layer 4 handles knowledge. the graph in this post is layer 4. SETUP: set in Desktop app, Dashboard, or config.yaml: WIKI_PATH=~/wiki OBSIDIAN_VAULT_PATH=~/wiki first run: Hermes asks for your domain. answer with your niche. the skill builds SCHEMA.md with tag taxonomy. after that: "index this into my wiki: [URL or text]" the wiki grows. the graph densifies. the agent gets smarter because the knowledge base got smarter. full 15 levels breakdown in the article 👇

YanXbt

34,368 views • 22 days ago

Building AI agents is finally simple — and Airia is leading the way. I’ve been testing Airia AI , enterprise AI orchestration platform that unifies every model, workflow, and data source into one secure environment. Whether you’re a developer, analyst, creator, or enterprise leader, Airia makes it incredibly easy to build powerful AI agents — without wrestling with multiple tools or complex integrations. Using the no-code builder, you can drag-and-drop actions, connect data, choose your LLM, and launch an agent in minutes. Then run it live, publish it, and even share it with the Airia Community, home to 2,500+ pre-built agents you can use or remix. If you want to automate workflows, prototype faster, or explore real enterprise AI use cases, Airia is the place to start. 👉 Build your first agent today: 👉 Explore the community: #Airia #AgenticAI #AIOrchestration #AIAgents #AIWorkflow #DigitalTransformation

Building AI agents is finally simple — and Airia is leading the way. I’ve been testing Airia AI , enterprise AI orchestration platform that unifies every model, workflow, and data source into one secure environment. Whether you’re a developer, analyst, creator, or enterprise leader, Airia makes it incredibly easy to build powerful AI agents — without wrestling with multiple tools or complex integrations. Using the no-code builder, you can drag-and-drop actions, connect data, choose your LLM, and launch an agent in minutes. Then run it live, publish it, and even share it with the Airia Community, home to 2,500+ pre-built agents you can use or remix. If you want to automate workflows, prototype faster, or explore real enterprise AI use cases, Airia is the place to start. 👉 Build your first agent today: 👉 Explore the community: #Airia #AgenticAI #AIOrchestration #AIAgents #AIWorkflow #DigitalTransformation

Adarsh Chetan

268,907 views • 7 months ago

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

OpenClaw, but built for normal people. Sim is an open-source platform that lets you build AI agent workflows on a drag-and-drop canvas. Connect them to channels like Telegram and WhatsApp and deploy without writing a single line of code. They also have a built-in Copilot that generates entire workflows from plain English, which you can then tweak and customize in the UI. Key features: - Free and open-source (Apache 2.0) - Vector store integration for RAG-grounded agents - Self-host with one command (`npx simstudio`) - Run fully local with Ollama, no API keys needed - Supports vLLM for production-grade self-hosted inference The thing I really like about Sim is the level of control you get. You can add conditional branching, parallel execution, human-in-the-loop approval gates, and even nest workflows inside other workflows. Everything is visible on the canvas, so you know exactly what your agent is doing at every step. And you can build a workflow in Sim, deploy it as an MCP server, and plug it into any agent, including OpenClaw. I've shared the link to Sim's GitHub repo in the next tweet.

Akshay 🚀

52,426 views • 4 months ago

CA: 0x172ae9e9b46770a70f479404d76e2f6561507011ef77a247fe3f58e7a5840a0d::manny::MANNY Your smart, hands-free edge tool in the crypto market. This powerful automated bot is designed to buy low and sell high with precision. It scans hundreds of coins in real-time, waiting for the right indicators—trend strength, volume spikes, price momentum, and bullish patterns—before entering a trade. Once in, it manages risk with dynamic stop-loss and take-profit levels, so your capital is always protected. Every trade is backed by a multi-layer confluence strategy, ensuring only high-confidence setups are executed. ✅ Advanced entry logic ✅ Fully automated buy/sell execution ✅ Built-in profit protection and cooldown filters ✅ Real-time alerts (Telegram/Twitter ready) ✅ JSON-based state memory for continuity ✅ Minimal setup, maximum performance ✅ Excludes low-quality coins automatically (e.g., BTC/ETH filters optional) ✅ Plug-and-play friendly — run it locally or integrate it into your system. ✅ Clean, professional trade alerts with price and PnL details ✅ Recovers automatically from connection issues or downtime Whether you’re a pro or just getting started, this bot helps you stay ahead of the market—24/7, emotion-free with pure mathematics. This bot has been in development for the last 6 months. I, Chronos, the developer behind it, have been testing for a while for the best configuration for a trading bot. I believe I have something good going on here. The bot automatically posts all the trades via IFTTT and X integration to its X account. Everything is automated. So how can people rent it, and how will it bring value to the project? Soon, the bot can be rented out via a cloud server. A customer must buy 30 USD worth of Memecoin_MANNY token (CA:0x172ae9e9b46770a70f479404d76e2f6561507011ef77a247fe3f58e7a5840a0d::manny::MANNY). After buying it and depositing it into a special wallet, he will be granted access to the bot. . The bot runs only on the backend — users interact with it via an interface (web app, Telegram bot, or API). A web dashboard and Telegram bot interface will be created. This lets users Start/stop their bot session See trade logs or results. Connect their API keys securely. Get alerts and updates The idea of all this is to offer a service but also bring value to the project. More bots will be developed. This is only the beginning. Cheers Chronos #python #memecoin_manny #spot #trading #bitcoin #eth #Binance #bybit #memecoin #VALHALLA

CA: 0x172ae9e9b46770a70f479404d76e2f6561507011ef77a247fe3f58e7a5840a0d::manny::MANNY Your smart, hands-free edge tool in the crypto market. This powerful automated bot is designed to buy low and sell high with precision. It scans hundreds of coins in real-time, waiting for the right indicators—trend strength, volume spikes, price momentum, and bullish patterns—before entering a trade. Once in, it manages risk with dynamic stop-loss and take-profit levels, so your capital is always protected. Every trade is backed by a multi-layer confluence strategy, ensuring only high-confidence setups are executed. ✅ Advanced entry logic ✅ Fully automated buy/sell execution ✅ Built-in profit protection and cooldown filters ✅ Real-time alerts (Telegram/Twitter ready) ✅ JSON-based state memory for continuity ✅ Minimal setup, maximum performance ✅ Excludes low-quality coins automatically (e.g., BTC/ETH filters optional) ✅ Plug-and-play friendly — run it locally or integrate it into your system. ✅ Clean, professional trade alerts with price and PnL details ✅ Recovers automatically from connection issues or downtime Whether you’re a pro or just getting started, this bot helps you stay ahead of the market—24/7, emotion-free with pure mathematics. This bot has been in development for the last 6 months. I, Chronos, the developer behind it, have been testing for a while for the best configuration for a trading bot. I believe I have something good going on here. The bot automatically posts all the trades via IFTTT and X integration to its X account. Everything is automated. So how can people rent it, and how will it bring value to the project? Soon, the bot can be rented out via a cloud server. A customer must buy 30 USD worth of Memecoin_MANNY token (CA:0x172ae9e9b46770a70f479404d76e2f6561507011ef77a247fe3f58e7a5840a0d::manny::MANNY). After buying it and depositing it into a special wallet, he will be granted access to the bot. . The bot runs only on the backend — users interact with it via an interface (web app, Telegram bot, or API). A web dashboard and Telegram bot interface will be created. This lets users Start/stop their bot session See trade logs or results. Connect their API keys securely. Get alerts and updates The idea of all this is to offer a service but also bring value to the project. More bots will be developed. This is only the beginning. Cheers Chronos #python #memecoin_manny #spot #trading #bitcoin #eth #Binance #bybit #memecoin #VALHALLA

Ex Machina

24,488 views • 1 year ago

CHINA JUST LEAKED THE FUTURE OF WEB APPS. Alibaba open-sourced PageAgent and 99% of SaaS founders are sleeping on this. It's a JavaScript AI agent that lives INSIDE your webpage. Users control your entire interface with natural language. ↳ No browser extensions needed, screenshots or multi-modal LLMs, headless browser setup, and also no backend rewrite required Just drop it in your HTML with ONE line of code. What took 20 clicks now takes one sentence. "Click login, fill in my credentials, submit the form" Done. This is not a demo, it is production-ready. ↳ Turn any SaaS into an AI copilot in minutes ↳ Smart form filling for ERP, CRM, admin systems ↳ Voice commands and accessibility built in ↳ Multi-page agent tasks via Chrome extension ↳ MCP server support for external control ↳ Bring your own LLM (Qwen, GPT, Claude, anything) Every founder building AI features just got a shortcut. Every developer manually building copilots just got replaced. The integration looks like this: That's it. Your app now has an AI agent.

CHINA JUST LEAKED THE FUTURE OF WEB APPS. Alibaba open-sourced PageAgent and 99% of SaaS founders are sleeping on this. It's a JavaScript AI agent that lives INSIDE your webpage. Users control your entire interface with natural language. ↳ No browser extensions needed, screenshots or multi-modal LLMs, headless browser setup, and also no backend rewrite required Just drop it in your HTML with ONE line of code. What took 20 clicks now takes one sentence. "Click login, fill in my credentials, submit the form" Done. This is not a demo, it is production-ready. ↳ Turn any SaaS into an AI copilot in minutes ↳ Smart form filling for ERP, CRM, admin systems ↳ Voice commands and accessibility built in ↳ Multi-page agent tasks via Chrome extension ↳ MCP server support for external control ↳ Bring your own LLM (Qwen, GPT, Claude, anything) Every founder building AI features just got a shortcut. Every developer manually building copilots just got replaced. The integration looks like this: That's it. Your app now has an AI agent.

Kanika

328,347 views • 15 days ago

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

The Visual Studio Code insiders version that just shipped and will ship in the next few days will come with an insane amount of new capabilities. A few highlights: - You can now run sub-agents in parallel. Yes, really. I even attached a video. - Major UX improvements for sub agents, especially visible in the chat window - A new search tool wrapped as a sub-agent that iteratively runs multiple search tools: semantic_search, file_search, grep_search Which connects nicely to the point above: multiple searches running in parallel, efficiently and fast - Anthropic’s Message API is now enabled by default - You can choose the model for the cloud agent (three available, all premium) - Extended thinking support when using the Claude cloud agent This is part of the broader multi-vendor cloud support under AgentsHQ I wrote about a few weeks ago - Tasks sent to the background agent (basically the CLI tool) now always run in isolation, each with its own git worktree - In a multi-repo workspace, assigning a task to a cloud agent prompts you to choose the target repo Same behavior when opening an empty workspace with no repo - Support for building an external index for files not supported by GitHub’s default indexing - UI/UX improvements for starting new sessions and switching between local / background / cloud agents - Skills are now first-class citizens, just like prompt files, with better UX indicating when a skill is loaded - Improved API for dynamic contribution of prompt files New V2 includes skills as part of the model. Curious to see the extensions that will leverage this - Finally, initial support for showing context usage percentage per session - Skills are enabled by default - Resizable chat window and session view. Small thing, but it was driving me crazy 😁 - A new integrated browser meant to replace the old simple browser Maybe the beginning of real browser use? - Better UI/UX for token streaming in chat - Ability to index external files not supported by GitHub There’s a lot more. Some of it hasn’t fully landed yet, but everything that has is already in Insiders. The next stable release should drop in early February. As usual, I’m just shocked by the volume of features this team ships every month. After the holiday slowdown, this one is shaping up to be a wild release.

Oren Melamed

29,555 views • 6 months ago

Most people see a Mac Mini as a home computer. He saw a $300 invoice waiting to happen. A guy in Shenzhen figured out that every early-stage startup, every founder, every small business owner needs the same thing, someone to tell them what their competitors are doing and where the gaps are. Nobody wants to pay $2,000 for a research firm. Nobody wants to wait a week. He set up Hermes on a laptop. Local model. No API costs. First report took 15 minutes. He charged $300 and delivered same day. Then he bought another machine. Then another. Now there are 65 Mac Minis on metal shelves in his apartment. Each one runs its own agent. Each agent has its own skills folder that grows every time it completes a task. Month one: $3,200. Month three: $9,600. The tool: Hermes Agent. Free on GitHub. The model: Qwen 3.6 27B. Also free. Total monthly cost: $2 in electricity. The hardware paid for itself in week two. The shelves haven't changed. He just keeps adding machines.

Most people see a Mac Mini as a home computer. He saw a $300 invoice waiting to happen. A guy in Shenzhen figured out that every early-stage startup, every founder, every small business owner needs the same thing, someone to tell them what their competitors are doing and where the gaps are. Nobody wants to pay $2,000 for a research firm. Nobody wants to wait a week. He set up Hermes on a laptop. Local model. No API costs. First report took 15 minutes. He charged $300 and delivered same day. Then he bought another machine. Then another. Now there are 65 Mac Minis on metal shelves in his apartment. Each one runs its own agent. Each agent has its own skills folder that grows every time it completes a task. Month one: $3,200. Month three: $9,600. The tool: Hermes Agent. Free on GitHub. The model: Qwen 3.6 27B. Also free. Total monthly cost: $2 in electricity. The hardware paid for itself in week two. The shelves haven't changed. He just keeps adding machines.

Superior

28,895 views • 1 month ago

SEVEN RTX 3090S IN A WATER TANK FOR AI SERVER it is a private AI server with the power bill moved into your room. not a clean Mac mini. not a quiet box under a monitor. loose vertical GPUs sit inside a transparent tank. bubbles rise through distilled water. ALLIED CONTROL is printed on the side. it looks closer to a lab accident than a normal workstation. but the logic is obvious: seven RTX 3090s = seven 24GB cards. that is the used-market shortcut for people who want local inference without paying cloud tax on every run. put Ollama, llama.cpp, vLLM, Open WebUI, Tailscale, Qwen, DeepSeek, or Llama on top. now the box can handle client files, code agents, scraping jobs, evals, transcription, and boring overnight work. not because it beats frontier cloud models. because it changes the bill shape. no rate limit. no per-token anxiety. no sensitive client context leaving the building. no monthly stack quietly turning into rent. the ugly part is physical. seven 3090s can pull serious power, dump serious heat, and punish lazy cooling. distilled water is the weird visual, not a setup tip. real immersion rigs live or die on coolant chemistry, insulation, pumps, maintenance, and whether the room can handle the heat. local AI PCs are becoming less like gaming builds and more like small private data centers. the early question is not: can it run ChatGPT? it is: what work is repetitive, private, expensive in the cloud, and worth owning in hardware?

SEVEN RTX 3090S IN A WATER TANK FOR AI SERVER it is a private AI server with the power bill moved into your room. not a clean Mac mini. not a quiet box under a monitor. loose vertical GPUs sit inside a transparent tank. bubbles rise through distilled water. ALLIED CONTROL is printed on the side. it looks closer to a lab accident than a normal workstation. but the logic is obvious: seven RTX 3090s = seven 24GB cards. that is the used-market shortcut for people who want local inference without paying cloud tax on every run. put Ollama, llama.cpp, vLLM, Open WebUI, Tailscale, Qwen, DeepSeek, or Llama on top. now the box can handle client files, code agents, scraping jobs, evals, transcription, and boring overnight work. not because it beats frontier cloud models. because it changes the bill shape. no rate limit. no per-token anxiety. no sensitive client context leaving the building. no monthly stack quietly turning into rent. the ugly part is physical. seven 3090s can pull serious power, dump serious heat, and punish lazy cooling. distilled water is the weird visual, not a setup tip. real immersion rigs live or die on coolant chemistry, insulation, pumps, maintenance, and whether the room can handle the heat. local AI PCs are becoming less like gaming builds and more like small private data centers. the early question is not: can it run ChatGPT? it is: what work is repetitive, private, expensive in the cloud, and worth owning in hardware?

kocer

570,850 views • 2 days ago

LayerAI Launches XRP AI Bot: A Simpler Way to Transact on the XRP Ledger 🌐 Users can now perform essential actions such as checking balances, sending tokens, or executing swaps through natural language commands, without relying on traditional interfaces or dApps. It works like ChatGPT, but instead of generating text, it executes XRP transactions on your behalf. Example commands: “Convert 150 XRP to EUR” “Send 75 XRP to address [wallet address]” “Swap 50 XRP for USDT” To get started: 1. Connect your XAMAN wallet (one-time setup) 2. Start a conversation with the XRP AI Bot 3. Review, confirm, and sign the transaction The XRP AI Bot is now available to all users. Start here:

LayerAI Launches XRP AI Bot: A Simpler Way to Transact on the XRP Ledger 🌐 Users can now perform essential actions such as checking balances, sending tokens, or executing swaps through natural language commands, without relying on traditional interfaces or dApps. It works like ChatGPT, but instead of generating text, it executes XRP transactions on your behalf. Example commands: “Convert 150 XRP to EUR” “Send 75 XRP to address [wallet address]” “Swap 50 XRP for USDT” To get started: 1. Connect your XAMAN wallet (one-time setup) 2. Start a conversation with the XRP AI Bot 3. Review, confirm, and sign the transaction The XRP AI Bot is now available to all users. Start here:

LayerAI | AI2Earn

123,799 views • 1 year ago

I stack Hermes agents with OpenClaw for financial research, and the results should be illegal. I track every politician, insider trader, and I know EXACTLY what moves they're making. If you can't beat them, join them. The exact playbook for printing money from insider trading (copy me): Requirements: • OpenClaw setup • Hermes Agent setup Step 1. Define your research thesis Before you send any prompts to either tool, you'll need to clarify exactly what you're trying to research. This could be: a specific industry, asset class, market sector, and so on. Examples: • Tracking smart money buys in the semiconductor industry • Tracking smart money buys in crypto • Tracking a specific politician and where they're bidding (like Nancy Pelosi) Step 2. Deploy Hermes agents to track the smart money (in parallel) Hermes is your data layer. Spin up 5 agents at the same time, each with one job: Agent 1: Track every politician's disclosed trades from the last 30 days (House and Senate stock disclosures) Agent 2: Pull insider transactions (Form 4 filings, CEO/CFO buys and sells) Agent 3: Scrape X sentiment from top 50 accounts on the topic Agent 4: Pull on-chain data (whale wallets, TVL, exchange flows) *if applicable* Agent 5: Monitor news, regulatory filings, and announcements from the last 30 days Each agent runs independently. You're not waiting for one to finish before the next starts. Step 3. Consolidate the output Once your Hermes agents finish, dump every output into a single document. (don't filter or summarize) - you want OpenClaw to see the raw data. Step 4. Feed it all into OpenClaw Open OpenClaw and paste the consolidated research file with this prompt: "Act as an elite macro analyst. Below is raw data gathered from multiple sources on [thesis], including politician disclosures and insider transactions. Synthesize the findings, identify the strongest signals and contradictions, flag any unusual smart-money activity, and give me a clear directional view with conviction levels. Flag any data gaps that need follow-up." OpenClaw will go deep, run its own reasoning chain, and produce a synthesized report. Done. Now you're literally tapping into the financial data they don't want you to see (it's all public - you just had to find it). Make sure to save this playbook so you don't lose it!

I stack Hermes agents with OpenClaw for financial research, and the results should be illegal. I track every politician, insider trader, and I know EXACTLY what moves they're making. If you can't beat them, join them. The exact playbook for printing money from insider trading (copy me): Requirements: • OpenClaw setup • Hermes Agent setup Step 1. Define your research thesis Before you send any prompts to either tool, you'll need to clarify exactly what you're trying to research. This could be: a specific industry, asset class, market sector, and so on. Examples: • Tracking smart money buys in the semiconductor industry • Tracking smart money buys in crypto • Tracking a specific politician and where they're bidding (like Nancy Pelosi) Step 2. Deploy Hermes agents to track the smart money (in parallel) Hermes is your data layer. Spin up 5 agents at the same time, each with one job: Agent 1: Track every politician's disclosed trades from the last 30 days (House and Senate stock disclosures) Agent 2: Pull insider transactions (Form 4 filings, CEO/CFO buys and sells) Agent 3: Scrape X sentiment from top 50 accounts on the topic Agent 4: Pull on-chain data (whale wallets, TVL, exchange flows) if applicable Agent 5: Monitor news, regulatory filings, and announcements from the last 30 days Each agent runs independently. You're not waiting for one to finish before the next starts. Step 3. Consolidate the output Once your Hermes agents finish, dump every output into a single document. (don't filter or summarize) - you want OpenClaw to see the raw data. Step 4. Feed it all into OpenClaw Open OpenClaw and paste the consolidated research file with this prompt: "Act as an elite macro analyst. Below is raw data gathered from multiple sources on [thesis], including politician disclosures and insider transactions. Synthesize the findings, identify the strongest signals and contradictions, flag any unusual smart-money activity, and give me a clear directional view with conviction levels. Flag any data gaps that need follow-up." OpenClaw will go deep, run its own reasoning chain, and produce a synthesized report. Done. Now you're literally tapping into the financial data they don't want you to see (it's all public - you just had to find it). Make sure to save this playbook so you don't lose it!

Miles Deutscher

19,709 views • 2 months ago

Visa just gave your AI a debit card. A real, spendable Visa card created by an AI chatbot in under 10 seconds. No human types in a card number or visits a checkout page. The machine handles it all. A tool called AgentCard just went live on Claude Desktop Anthropic’s AI assistant. You say create a card and the AI generates a one-time virtual Visa, preloaded with whatever amount you set. Then it spends it, anywhere Visa is accepted on your behalf. Visa, Mastercard, Google, Stripe, OpenAI, and Anthropic have all been building toward this moment for over a year. Visa calls it the trusted agent protocol, Mastercard calls it agent pay. Google published an open standard for agent payments and the infrastructure is already live. Santander and Mastercard just completed Europe’s first real AI‑agent payment in a live banking environment Now the part no one wants to talk about. Your AI agent can be manipulated and prompt injection a known, unsolved vulnerability can trick an agent into buying things you never asked for. The agent holds the card, makes the call and the agent can be fooled. Who is liable when an AI makes a bad purchase? You? Anthropic? Visa? The merchant? No one has answered this yet, regulators haven’t caught up, and no court has tested it.

Visa just gave your AI a debit card. A real, spendable Visa card created by an AI chatbot in under 10 seconds. No human types in a card number or visits a checkout page. The machine handles it all. A tool called AgentCard just went live on Claude Desktop Anthropic’s AI assistant. You say create a card and the AI generates a one-time virtual Visa, preloaded with whatever amount you set. Then it spends it, anywhere Visa is accepted on your behalf. Visa, Mastercard, Google, Stripe, OpenAI, and Anthropic have all been building toward this moment for over a year. Visa calls it the trusted agent protocol, Mastercard calls it agent pay. Google published an open standard for agent payments and the infrastructure is already live. Santander and Mastercard just completed Europe’s first real AI‑agent payment in a live banking environment Now the part no one wants to talk about. Your AI agent can be manipulated and prompt injection a known, unsolved vulnerability can trick an agent into buying things you never asked for. The agent holds the card, makes the call and the agent can be fooled. Who is liable when an AI makes a bad purchase? You? Anthropic? Visa? The merchant? No one has answered this yet, regulators haven’t caught up, and no court has tested it.

Milk Road AI

70,591 views • 4 months ago

This broke my mental model of game dev 💀 2.5 hours → fully playable ‘Worms’ clone. Built with Hermes agent by Nous Research Here’s what made that speed possible: Hermes used ‘Persistent Shell’ mode, which ensured it didn't forget its current folder or active tools. This allowed it to work smoothly, without the distraction of constantly having to recall where it left off last time. To optimize the workflow, the agent moved beyond linear execution and parallelized the workload. It spawned isolated subagents while executing multiple independent tool calls via ThreadPoolExecutor. Like, one subagent wrote Python RPC scripts for the projectile physics while another utilized vision tools for character sprites. When the complex terrain logic required debugging, the agent used filesystem checkpoints and the /rollback command to instantly return to a stable state. To fix UI bugs, it attached to a live Chrome instance via CDP (/browser connect), fixing rendering issues in real-time. The agent’s built-in learning loop was active from the very beginning. By the time the game was finished, this continuous process allowed the agent to autonomously convert the physics logic into a custom skill. This logic is now a permanent plugin file in the agent's plugin architecture, making the physics engine a native capability that the agent can reuse for future projects. Follow War_v3_FINALE.exe for updates!

This broke my mental model of game dev 💀 2.5 hours → fully playable ‘Worms’ clone. Built with Hermes agent by Nous Research Here’s what made that speed possible: Hermes used ‘Persistent Shell’ mode, which ensured it didn't forget its current folder or active tools. This allowed it to work smoothly, without the distraction of constantly having to recall where it left off last time. To optimize the workflow, the agent moved beyond linear execution and parallelized the workload. It spawned isolated subagents while executing multiple independent tool calls via ThreadPoolExecutor. Like, one subagent wrote Python RPC scripts for the projectile physics while another utilized vision tools for character sprites. When the complex terrain logic required debugging, the agent used filesystem checkpoints and the /rollback command to instantly return to a stable state. To fix UI bugs, it attached to a live Chrome instance via CDP (/browser connect), fixing rendering issues in real-time. The agent’s built-in learning loop was active from the very beginning. By the time the game was finished, this continuous process allowed the agent to autonomously convert the physics logic into a custom skill. This logic is now a permanent plugin file in the agent's plugin architecture, making the physics engine a native capability that the agent can reuse for future projects. Follow War_v3_FINALE.exe for updates!

Javier

37,874 views • 3 months ago

Slideshow clipping has to be the chillest business model you can really be making $5k - $15k+ a month running 10 TikTok accounts and have complete location freedom + make more than you would working a job you can literally just go to content rewards, pick a saas or brand to promote, for example skin care buy 5 aged TT accounts to start with connect US proxy / sim find videos in the niche the product is in for example skin care steal the hook of the video and content inside it and turn it into a slideshow for example: “skin care tips for broke girls” generate the images with NBP by finding a Pinterest image and getting the JSON from Gemini or ChatGPT promote the product as another “glow up” tip Post 1 a day from the start and as the accounts get more warm boost it to 2-3 + scale to more accounts If you can’t make your first $5k doing this then there is no hope

Pounds

15,415 views • 5 months ago

i spent $26,600 on cloud GPU rentals over 14 months before i found a NVIDIA DGX Spark at $2,999 (founder's edition) or $3,999 (shipping price) it paid for itself in 6 weeks i run 200B parameter models locally now and my old cloud provider keeps sending me loyalty discount emails the math on that $26,600 is embarrassing to type out loud $1,900/month for 14 months, H100 instances on a specialist cloud provider, because anything bigger than a 70B model simply would not fit anywhere else i paid the invoices like they were a utility bill and told myself it was just the cost of doing serious AI work it took me over a year to find out it wasn't 14 months, broken down: → months 1-4: $1,400-1,600/month - felt like manageable infrastructure overhead → months 5-9: crept to $1,900-2,100 as i started running DeepSeek-class experiments, costs tracking directly with model size → months 10-12: one agent loop ran for 36 hours against a 130B model while i slept, that month hit $2,400 → month 13: ran the cumulative total for the first time, saw $23,800, felt physically sick → month 14: another $2,800 month while i waited for the hardware to ship the box is the NVIDIA DGX Spark - roughly the footprint of a large mac mini, powered by a GB10 Grace Blackwell chip with 128GB of unified LPDDR5X memory that unified memory is the whole thing an RTX 4090 has 24GB of VRAM, which means a 70B model in full BF16 precision physically does not fit, you're quantizing down or you're renting cloud, those are your options this box loads a 200B parameter model quantized and serves it through vLLM over localhost, same API interface the cloud endpoint used the migration took one line of code - i changed the base URL from the provider's endpoint to 127.0.0.1:8000 and everything just worked electricity to run continuous 200B inference locally comes out to about $12/month the payback arithmetic is almost too clean: $2,999 hardware cost against $1,900/month saved, the box paid for itself before i'd owned it two months what i didn't account for was how completely the cost model changes your behavior when there's no hourly meter running, you greenlight experiments you'd never approve on cloud - agent loops that churn for hours, running 10,000 documents through a reasoning pass at 3am, speculative fine-tuning jobs you'd normally skip because the cost felt unjustifiable i ran more experiments in the first 30 days after the box arrived than in the four months before it the loyalty discount email landed about 8 weeks after i cancelled the cloud subscription 15% off my next three months, valued customer, we'd love to have you back i didn't reply the box was already running

i spent $26,600 on cloud GPU rentals over 14 months before i found a NVIDIA DGX Spark at $2,999 (founder's edition) or $3,999 (shipping price) it paid for itself in 6 weeks i run 200B parameter models locally now and my old cloud provider keeps sending me loyalty discount emails the math on that $26,600 is embarrassing to type out loud $1,900/month for 14 months, H100 instances on a specialist cloud provider, because anything bigger than a 70B model simply would not fit anywhere else i paid the invoices like they were a utility bill and told myself it was just the cost of doing serious AI work it took me over a year to find out it wasn't 14 months, broken down: → months 1-4: $1,400-1,600/month - felt like manageable infrastructure overhead → months 5-9: crept to $1,900-2,100 as i started running DeepSeek-class experiments, costs tracking directly with model size → months 10-12: one agent loop ran for 36 hours against a 130B model while i slept, that month hit $2,400 → month 13: ran the cumulative total for the first time, saw $23,800, felt physically sick → month 14: another $2,800 month while i waited for the hardware to ship the box is the NVIDIA DGX Spark - roughly the footprint of a large mac mini, powered by a GB10 Grace Blackwell chip with 128GB of unified LPDDR5X memory that unified memory is the whole thing an RTX 4090 has 24GB of VRAM, which means a 70B model in full BF16 precision physically does not fit, you're quantizing down or you're renting cloud, those are your options this box loads a 200B parameter model quantized and serves it through vLLM over localhost, same API interface the cloud endpoint used the migration took one line of code - i changed the base URL from the provider's endpoint to 127.0.0.1:8000 and everything just worked electricity to run continuous 200B inference locally comes out to about $12/month the payback arithmetic is almost too clean: $2,999 hardware cost against $1,900/month saved, the box paid for itself before i'd owned it two months what i didn't account for was how completely the cost model changes your behavior when there's no hourly meter running, you greenlight experiments you'd never approve on cloud - agent loops that churn for hours, running 10,000 documents through a reasoning pass at 3am, speculative fine-tuning jobs you'd normally skip because the cost felt unjustifiable i ran more experiments in the first 30 days after the box arrived than in the four months before it the loyalty discount email landed about 8 weeks after i cancelled the cloud subscription 15% off my next three months, valued customer, we'd love to have you back i didn't reply the box was already running

Argona

22,099 views • 1 month ago