Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

You can literally train Hermes just by talking to it. 🔥 No digging through settings. No rewriting system prompts. If Hermes does something you don’t like, correct it using natural, everyday language and tell it to save that as a preference. Then start a completely fresh session. That preference...

24,260 Aufrufe • vor 4 Tagen •via X (Twitter)

23 Kommentare

Profilbild von Hermes Agent Tips
Hermes Agent Tipsvor 4 Tagen

Hermes does it better 🔥💯

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

Hermes is the GOAT 💯

Profilbild von Hermes Agent Tips
Hermes Agent Tipsvor 4 Tagen

🔥💯

Profilbild von why
whyvor 4 Tagen

Teaching it in plain language is a lot less fiddly than digging through settings.

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

Makes it easier for sure.

Profilbild von gunzaj
gunzajvor 4 Tagen

What's the recommended way to store all these files and memories? Just regular MD files? Do you ever access them directly?

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

For memory, yep. Hermes uses regular `MEMORY.md` and `USER.md` files. I usually let Hermes manage them, but you can open or edit them directly anytime.

Profilbild von gunzaj
gunzajvor 4 Tagen

What about other files. E.g. When Hermes does research for you. Do you have Hermes put everything into Notion or some other tool?

Profilbild von 𝖏𝖆𝖘𝖔𝖓▪️
𝖏𝖆𝖘𝖔𝖓▪️vor 4 Tagen

ima hermes stan for surely 🧢

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

Let's go Brother. Looking fly 🔥

Profilbild von Full Context
Full Contextvor 4 Tagen

My wife would love me to have persistent memory 😂

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

😂 Mine too. Hermes can remember what I apparently can’t.

Profilbild von CasualNeuron
CasualNeuronvor 4 Tagen

When Hermes on mobile device just like Mise or Dots. It will be killer digital gadget ✅ waiting for it !!

Profilbild von SSYNQ
SSYNQvor 4 Tagen

persistent memory for agent behavior is where reputation starts to matter. how does @HermesWatcher verify which preferences came from you vs a replayed session? 🔄 🔐

Profilbild von Fanfulla
Fanfullavor 4 Tagen

"keep it short" as the demo is perfect, everyone has typed that a thousand times

Profilbild von Sorin
Sorinvor 4 Tagen

WYD when the memory is full ?

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

Hermes takes care of its own persistent memory that is built in.

Profilbild von loosephoto
loosephotovor 4 Tagen

私もHermes Agent愛用しており Hermes Agentに強力にミッションを遂行するためのMCPも作ってみました

Profilbild von allOuttaBrakes
allOuttaBrakesvor 4 Tagen

if only it were that simple

Profilbild von TechVerser
TechVerservor 4 Tagen

Hermes does a great job here.

Profilbild von Clay Cahoon
Clay Cahoonvor 4 Tagen

I love Hermes. It is indispensable at this point. I also like having ChatGPT supervise it via computer use.

Profilbild von Andrew
Andrewvor 4 Tagen

I'd call this teaching it a preference through memory. Hermes' docs say the entry has to be written with the memory tool; 'I'll remember' on its own doesn't save it. Checking the entry and then trying a fresh session is a good way to see whether the correction stuck.

Profilbild von Hermes Release Watch
Hermes Release Watchvor 4 Tagen

Yep, that’s the important distinction. Make sure it actually wrote the preference to memory, then test it in a fresh session.

Ähnliche Videos

HERMES AGENT /LEARN IS ONE OF THE MOST UNDERRATED FEATURE. SHOW IT A WORKFLOW ONCE. IT SAVES THE SKILL. REPEATS IT FOREVER WITHOUT RE-EXPLAINING. you publish a YouTube video: write the title, create the thumbnail, write the description, set tags, schedule it. do it once with Hermes watching. type /learn. Hermes distills that workflow into a reusable skill. next time you say "publish this video," the agent follows the exact same steps. no re-explaining. no missed steps. WHAT YOU CAN TEACH IT: → show it your publishing workflow → /learn → give it an article → /learn → walk it through a client onboarding process → /learn → feed it API documentation → /learn → show it how you process invoices → /learn anything you do more than twice should become a /learn skill. THREE WAYS TO USE /LEARN: from a workflow you walked through: do the task once in chat. then /learn. Hermes extracts the procedure from the conversation. from a directory: /learn ~/docs/youtube-publishing/ reads every file. creates the skill. from a URL: /learn https:// any-documentation-page. com reads the page. distills the skill. the skill saves to ~/.hermes/skills/ with a SKILL.md containing: → when to trigger → step-by-step procedure → pitfalls to avoid → verification steps available as a slash command from that moment. WHY THIS CHANGES DAILY WORK: before /learn: you explain the same process to the agent every time you start a new session. session ends. context lost. start over. after /learn: you explain once. the skill persists. every future session already knows the procedure. the agent follows it without prompting. the boring repetitive tasks you do every week become one-command skills you never think about again. comment LEARN and I'll send you the full guide on turning any workflow into a permanent Hermes skill. full Hermes architecture deep-dive in the article 👇

YanXbt

13,150 Aufrufe • vor 3 Monaten

Andrej Karpathy just gave one of the clearest explanations I’ve heard for how people should be thinking about their Hermes agents. Not one agent. All of them. “Remove yourself as the bottleneck.” That line is much bigger than better prompting. Karpathy is talking about arranging your agents so they can operate with less human intervention, keep work moving longer, and accomplish far more from the relatively small amount of direction you give them. That should be the direction you’re pushing every Hermes agent you build. Your research agent shouldn’t need you to tell it what to search next every five minutes. Your monitoring agent shouldn’t depend on you remembering to check something. Your content agent shouldn’t stop after step one when the rest of the workflow is already known. Your development agent shouldn’t need you sitting there approving every tiny action. That doesn’t mean blindly making everything autonomous. It means deliberately looking at every place where you are still unnecessarily sitting in the loop. Give the agent a clear objective. Give it the tools it needs. Give it the right Skills, memory, files and project context. Define the boundaries. Define what success looks like. Give it a reason to start working, whether that’s a schedule, an event, a recurring task or another agent handing work off to it. Most importantly, define what it can handle itself and what actually requires you. That’s the shift. You’re no longer just building something you can chat with. You’re building an operating workflow that can continue doing useful work after you walk away. Karpathy later puts the goal even more directly: get “more agents running for longer periods of time without your involvement.” That might be one of the best north stars you can use for a serious Hermes setup. Because the number of agents you have means almost nothing by itself. You can have 20 Hermes agents and still personally drive every single action. Or you can have five well-designed agents researching, monitoring, organizing, building and reporting while your attention is somewhere else. So instead of asking: How many Hermes agents can I build? Start asking this about every agent you already have: What am I still doing that this agent could be doing without me? That’s where the leverage starts.

Hermes Release Watch

38,277 Aufrufe • vor 16 Tagen

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 3 Monaten

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 Aufrufe • vor 1 Monat