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 can now /learn from anything: feed it directories of any source material (code, API docs, manuals, PDFs, configs) and it distills a verifiable reusable skill

Nous Research

250,140 subscribers

1,315,623 views • 1 month ago •via X (Twitter)

Education News & Politics Science & Technology

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Addicted to Nous Research Hermes Agent's /learn. You can feed it any design and turn it into a reusable skill that makes Hermes design exactly how you want. /learn [URL or image] - extracts design tokens, layout structure, interaction states, component patterns, and a 10-point checklist Next time you want that exact style, just ask Hermes to use the skill it created. Example below 👇

Addicted to Nous Research Hermes Agent's /learn. You can feed it any design and turn it into a reusable skill that makes Hermes design exactly how you want. /learn [URL or image] - extracts design tokens, layout structure, interaction states, component patterns, and a 10-point checklist Next time you want that exact style, just ask Hermes to use the skill it created. Example below 👇

Mia

76,206 views • 1 month ago

Your favorite AI coding agents can now learn any skill from the web. We're shipping HyperSkill today. It auto-generates SKILL. md files from live docs, so your agents can master new frameworks, APIs, tools, and patterns, instantly. Open-source repo here ↓

Your favorite AI coding agents can now learn any skill from the web. We're shipping HyperSkill today. It auto-generates SKILL. md files from live docs, so your agents can master new frameworks, APIs, tools, and patterns, instantly. Open-source repo here ↓

Hyperbrowser

51,248 views • 6 months ago

Today I'm launching Interpreter. It's a desktop agent that can fill PDFs, edit your Excel and Word docs, and learn new skills. Runs offline, works with any model, and it's free.

Today I'm launching Interpreter. It's a desktop agent that can fill PDFs, edit your Excel and Word docs, and learn new skills. Runs offline, works with any model, and it's free.

killian

367,985 views • 5 months ago

I built a Claude Code skill that allows it to generate a deep research report over any collection of complex docs (PDFs, Word, Pptx)….and generate word-level citations and bounding boxes directly back to the source! 📝 Check out “/research-docs”. 1. It parses out text and bounding boxes from every doc with liteparse, in seconds. 2. It then generates a full HTML report of the outputs that let you see word-level citations in each page. Raw Claude obviously has deep research capabilities, but it lacks an audit trail back to the source. This skill gives you a researched report that can be audited by others. Check it out: LiteParse:

I built a Claude Code skill that allows it to generate a deep research report over any collection of complex docs (PDFs, Word, Pptx)….and generate word-level citations and bounding boxes directly back to the source! 📝 Check out “/research-docs”. 1. It parses out text and bounding boxes from every doc with liteparse, in seconds. 2. It then generates a full HTML report of the outputs that let you see word-level citations in each page. Raw Claude obviously has deep research capabilities, but it lacks an audit trail back to the source. This skill gives you a researched report that can be audited by others. Check it out: LiteParse:

Jerry Liu

77,259 views • 4 months ago

🧠 Want to give your coding agent new capabilities? Use Agent Skills in Visual Studio Code! Agent skills let you package instructions and resources into reusable capabilities for your agent. Skills can be loaded on demand and called directly from chat using slash commands like /skill-name. Learn more:

🧠 Want to give your coding agent new capabilities? Use Agent Skills in Visual Studio Code! Agent skills let you package instructions and resources into reusable capabilities for your agent. Skills can be loaded on demand and called directly from chat using slash commands like /skill-name. Learn more:

Visual Studio Code

55,133 views • 5 months ago

I made a short video demonstrating how to use /learn in Hermes Agent to take a bunch of different sources, as well as your own preferences expressed to Hermes, and create a reusable skill. It's never been easier to teach your Hermes exactly how to work for you!

I made a short video demonstrating how to use /learn in Hermes Agent to take a bunch of different sources, as well as your own preferences expressed to Hermes, and create a reusable skill. It's never been easier to teach your Hermes exactly how to work for you!

tonbi

74,451 views • 1 month ago

Hermes Agent by Nous Research natively integrates with Give Hermes any URL and find a skill for it in our catalog, or create your own. Watch it find the NASA picture of the day for me.

Hermes Agent by Nous Research natively integrates with Give Hermes any URL and find a skill for it in our catalog, or create your own. Watch it find the NASA picture of the day for me.

Kyle Jeong

91,766 views • 2 months ago

This shouldn’t be possible… I built a reusable API for YouTube in under 5 minutes just by showing the agent once. My colleague needed all video links from a creator → the agent reverse-engineered the flow and produced a permanent API endpoint. Now we can hit it forever.

This shouldn’t be possible… I built a reusable API for YouTube in under 5 minutes just by showing the agent once. My colleague needed all video links from a creator → the agent reverse-engineered the flow and produced a permanent API endpoint. Now we can hit it forever.

Magnus Müller

46,405 views • 8 months ago

Today we're launching It gives any AI agent ready-to-use security context for thousands of open source projects, built from each project's commit history of security fixes and its disclosed CVEs. Useful whether your agent is writing code or reviewing it for bugs. Free, no auth, over MCP and API.

Today we're launching It gives any AI agent ready-to-use security context for thousands of open source projects, built from each project's commit history of security fixes and its disclosed CVEs. Useful whether your agent is writing code or reviewing it for bugs. Free, no auth, over MCP and API.

ProjectDiscovery

41,023 views • 1 month ago

AI Agents can now connect to 100,000+ APIs instantly. Postman's AI Agent builder can turn any API into an MCP server in seconds without writing a single line of Code. You can use it in Claude, Cursor, Windsurf and other AI tools.

AI Agents can now connect to 100,000+ APIs instantly. Postman's AI Agent builder can turn any API into an MCP server in seconds without writing a single line of Code. You can use it in Claude, Cursor, Windsurf and other AI tools.

Shubham Saboo

79,818 views • 1 year ago

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.

Here is a demo of the most comprehensive research agent for your code docs, powered by Nozomio Labs. It turns your indexed repos and docs into a dynamic tree that the agent can access on the fly, using SOTA tools to reduce code hallucinations. Now using the latest Anthropic model, Claude Opus 4.5.

Arlan

28,405 views • 8 months ago

Today we’re launching Prava Pay- Cards for your AI agent. Coffee, sneakers or subscriptions - your AI agent can now buy anything online by itself, all within the limits you set for it. Works with OpenClaw, Hermes, Claude Code out of the box.

Today we’re launching Prava Pay- Cards for your AI agent. Coffee, sneakers or subscriptions - your AI agent can now buy anything online by itself, all within the limits you set for it. Works with OpenClaw, Hermes, Claude Code out of the box.

Sushant

61,897 views • 2 months ago

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👇

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 views • 1 month ago

You can now connect Hermes Agent directly to your browser as a side panel. It's called Hermes Browser Extension. It reads your active tab and sends the context straight into a live Hermes session. > Summarize, explain, or extract action items from any page > Connects to a local gateway, Hermes Cloud, or a self-hosted server > Works with Chrome, Edge, Brave, and other Chromium browsers > Full Hermes runtime: tools, skills, sessions, and memory included 100% Free. Open Source.

You can now connect Hermes Agent directly to your browser as a side panel. It's called Hermes Browser Extension. It reads your active tab and sends the context straight into a live Hermes session. > Summarize, explain, or extract action items from any page > Connects to a local gateway, Hermes Cloud, or a self-hosted server > Works with Chrome, Edge, Brave, and other Chromium browsers > Full Hermes runtime: tools, skills, sessions, and memory included 100% Free. Open Source.

Simplifying AI

43,450 views • 1 month ago

HERMES AGENT CAN NOW RUN COMPLETELY FREE WITH GEMMA 4 + OLLAMA. No API bills, no limits, and a 256k context window running straight from your own machine.

HERMES AGENT CAN NOW RUN COMPLETELY FREE WITH GEMMA 4 + OLLAMA. No API bills, no limits, and a 256k context window running straight from your own machine.

0xMarioNawfal

120,992 views • 4 months ago

If an agent can automate Salesforce reliably… it can automate anything. It's the final boss of browser agents - nested iframes, dynamic components… pure chaos. So I stopped fighting the UI. It feels like pure magic. Record the workflow once → the agent reverse-engineers the API → you get a clean, reusable API. Agents won’t use UIs. They’ll use tools they create themselves. Comment a site like “salesforce?” and I’ll send you the agent.

If an agent can automate Salesforce reliably… it can automate anything. It's the final boss of browser agents - nested iframes, dynamic components… pure chaos. So I stopped fighting the UI. It feels like pure magic. Record the workflow once → the agent reverse-engineers the API → you get a clean, reusable API. Agents won’t use UIs. They’ll use tools they create themselves. Comment a site like “salesforce?” and I’ll send you the agent.

Magnus Müller

24,902 views • 8 months ago

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

Sarah Chieng

26,679 views • 4 months ago

My Hermes agent can now create LIVE datasets on the fly. Just added a real-time data layer to Hermes using the open-source TinyFish BigSet. First it builds the dataset. Then it finds the signal. This is WHAT agent-native research looks like in 2026.

My Hermes agent can now create LIVE datasets on the fly. Just added a real-time data layer to Hermes using the open-source TinyFish BigSet. First it builds the dataset. Then it finds the signal. This is WHAT agent-native research looks like in 2026.

Shubham Saboo

22,042 views • 2 months ago

A living map of everything your Hermes agent has learned; every memory & skill Press play to watch it unfold, Nous Research Copy yours into a code, paste a friend's to explore theirs

A living map of everything your Hermes agent has learned; every memory & skill Press play to watch it unfold, Nous Research Copy yours into a code, paste a friend's to explore theirs

Brooklyn!

59,578 views • 1 month ago

You need to try Hermes RIGHT NOW. OpenClaw was the breakthrough. Hermes feels like the evolution. Here’s why AI power users are quietly switching: • Hermes learns from you over time • It creates its own reusable skills • Memory stays curated instead of bloated • Agents improve every 10 turns automatically • It actually feels stable on day 30 The wildest part: Hermes agents build workflows from your behavior. One user asked their agent to configure Twingate once. The agent: → learned the process → created a reusable skill → stored it for future tasks → improved its own workflow automatically That’s not prompt engineering anymore. That’s agent evolution. Meanwhile most people are still babysitting broken OpenClaw setups and manually importing marketplace skills. Hermes took a different path: Less clutter. Less tweaking. More autonomy. And it’s working. It already flipped OpenClaw in OpenRouter token usage and became one of the fastest-growing AI repos on GitHub. The bigger shift: We’re entering the era where the model matters less than the harness around it. GPT-5.5, Grok, Qwen: They’re already powerful enough. The real edge now is: • memory systems • self-improvement loops • skill creation • agent orchestration Hermes understands that. Most people still think AI agents are glorified chatbots. The people using Hermes are building AI teammates.

You need to try Hermes RIGHT NOW. OpenClaw was the breakthrough. Hermes feels like the evolution. Here’s why AI power users are quietly switching: • Hermes learns from you over time • It creates its own reusable skills • Memory stays curated instead of bloated • Agents improve every 10 turns automatically • It actually feels stable on day 30 The wildest part: Hermes agents build workflows from your behavior. One user asked their agent to configure Twingate once. The agent: → learned the process → created a reusable skill → stored it for future tasks → improved its own workflow automatically That’s not prompt engineering anymore. That’s agent evolution. Meanwhile most people are still babysitting broken OpenClaw setups and manually importing marketplace skills. Hermes took a different path: Less clutter. Less tweaking. More autonomy. And it’s working. It already flipped OpenClaw in OpenRouter token usage and became one of the fastest-growing AI repos on GitHub. The bigger shift: We’re entering the era where the model matters less than the harness around it. GPT-5.5, Grok, Qwen: They’re already powerful enough. The real edge now is: • memory systems • self-improvement loops • skill creation • agent orchestration Hermes understands that. Most people still think AI agents are glorified chatbots. The people using Hermes are building AI teammates.

Dami-Defi

17,062 views • 2 months ago