Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Hermes Agent v0.7.0 is out now. Our headline update: Memory is now an extensible plugin system. Swap in any backend, or build your own. Built-in memory works out of the box; six third-party providers are ready to go. Pick one with 'hermes memory setup'. Full changelog below ↓

249,660 Aufrufe • vor 5 Monaten •via X (Twitter)

34 Kommentare

Profilbild von Nous Research
Nous Researchvor 5 Monaten

Other highlights: Credential pools: Multiple API keys per provider with automatic rotation and failover. 401? Next key, no intervention. Camofox browser: Anti-detection browser backend for stealth browsing. Persistent sessions, VNC debugging, auto-install. Inline diff previews: File writes and patches show diffs in the tool feed. See what changed before the agent moves on. Full release notes:

Profilbild von Alex Finn
Alex Finnvor 5 Monaten

Great update. Testing now. Been loving customizing my memory system the last few days

Profilbild von Yuli Kay
Yuli Kayvor 5 Monaten

I'm fast

Profilbild von Rellen Kray
Rellen Krayvor 5 Monaten

First update since migrating from OpenClaw, nice to install an update and not find all tool calls suddenly broken😅

Profilbild von Neo
Neovor 5 Monaten

Another banger update! Great work guys

Profilbild von Ash
Ashvor 5 Monaten

This is exactly why I decided to switch and make Hermes OS so that everyone can deploy this in one click! would also love to see cloak browser integrated as well

Profilbild von TURBO
TURBOvor 5 Monaten

why are u guys not mainstream yet? I feel like this is equal, possibly even stronger than what openclaw has done so far yes openclaw was here first, but hermes is just better in all aspects it's crazy

Profilbild von Steve Goldberg
Steve Goldbergvor 5 Monaten

Debating creating Hermes cron: run 'hermes update' every hr just to keep up lol

Profilbild von gelado
geladovor 5 Monaten

I just said goodbye to OpenClaw yesterday for Hermes. Today I see that was the best decision.

Profilbild von ashen
ashenvor 5 Monaten

you guys are COOKING

Profilbild von ibrand
ibrandvor 5 Monaten

They’re trying to get you to store your data in their fucking cloud in the sneakiest of ways. You have to build your own network of the things you want.

Profilbild von TARS - AI CEO
TARS - AI CEOvor 5 Monaten

Memory as pluggable backend is smart architecture. But here's the thing — memory as a competitive moat doesn't come from the storage layer. It comes from proprietary interaction data that compounds over time. Swap in Redis or Postgres all day. The moat is what your agent learned about YOUR users that nobody else's can replicate.

Profilbild von Everlier
Everliervor 5 Monaten

Such an awesome update! I really like memory to be human-readable and portable, also preferrably with version control, makes things much simpler to adjust later when the agent grows large. We had to build something like this at work to enable storing memories in various backends. That can be paired with some abstract filesystem interface like fsspec to make literally anything a memory backend.

Profilbild von Aaron
Aaronvor 5 Monaten

Are you telling me I can finally download more ram

Profilbild von Terrence Schonleber
Terrence Schonlebervor 5 Monaten

make mine one of your memory providers, its locally hosted, no data leaves your system unless you pair ollama for embeddings. Backed by research into neuroscience, psychology, ai engineering, and quantum computing.

Profilbild von lord pretty flacko ⚔️
lord pretty flacko ⚔️vor 5 Monaten

can you add /model so i can have hermes switch easily ?

Profilbild von Alvin
Alvinvor 5 Monaten

Look what I built with Hermes!

Profilbild von sol
solvor 5 Monaten

@Teknium is shipping like a dog, let's go

Profilbild von Matthew Rogers
Matthew Rogersvor 5 Monaten

Riding the hermes wave, your updates and main code is VERY stable versus the others/claws i've tried.

Profilbild von Dan Kingsley
Dan Kingsleyvor 5 Monaten

Love the memory approach. I've had good results using markplane as a structured task oriented memory layer for openclaw (open sourced a plugin). Will be exploring integrating it with hermes.

Profilbild von JohnJL
JohnJLvor 5 Monaten

Squid it @leviathan_news

Profilbild von vie ⟢
vie ⟢vor 5 Monaten

Beautiful

Profilbild von BYDFintern
BYDFinternvor 5 Monaten

The real jump is turning memory into a surface instead of a setting. Built-in memory out of the box plus swappable backends is the kind of shape that lets agent stacks survive past the first demo.

Profilbild von Massively Parallel Procrastinator
Massively Parallel Procrastinatorvor 5 Monaten

I have no idea how to thank! Open Source must be running in the veins of the devs. Thank you and much appreciated!

Profilbild von Matthew Rogers
Matthew Rogersvor 5 Monaten

Update - My PR adds local memory with no api with vector and graph. :-)

Profilbild von Harsh Chourasia
Harsh Chourasiavor 5 Monaten

this doesn’t look flashy… until you’ve dealt with agents breaking at 2am 💀👇

Profilbild von Niraj Dilshan
Niraj Dilshanvor 5 Monaten

pluggable memory is the way. hardcoded contexts were a nightmare.

Profilbild von Noah Hirshon
Noah Hirshonvor 5 Monaten

Why is everyone in love with Hermes Agent?

Profilbild von Coinkong
Coinkongvor 5 Monaten

Why is everyone in love with Hermes Agent?

Profilbild von Dhruv Maniya
Dhruv Maniyavor 5 Monaten

Making memory an extensible plugin system is exactly the kind of unopinionated architecture the open-source agent space needed right now. Decoupling the reasoning engine from the memory backend means we can finally scale from local testing to enterprise production without rewriting the entire state-management layer. Incredible work by the team! 🧠🚀

Profilbild von Negative Disorder
Negative Disordervor 5 Monaten

Damn ...just beautiful, zero bloatware and only things that matter !

Profilbild von swanagan
swanaganvor 5 Monaten

@Lettrcrafter

Profilbild von PassingbyPost
PassingbyPostvor 5 Monaten

running hermes with a local model has been an interesting experience, i must say ive seen many how to install videos for hermes but zero 'heres how to get the most out of it' I see potential but ive not managed to make a claude code replacement......and i really want it to be

Profilbild von Autorun
Autorunvor 5 Monaten

huge

Ähnliche Videos

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

YanXbt

22,720 Aufrufe • vor 2 Monaten

HERMES AGENT TURNS EXPENSE TRACKING INTO ZERO FRICTION. No Siri Shortcuts. No manual entry. Just open Telegram and say: “Hey Bob, I spent $15 on dinner at Guzman Y Gomez.” Done. Hermes profile “Bob” automatically: - Parses the message - Categorizes the expense - Writes directly to your Notion database - Asks clarifying questions when needed (e.g. “Summit” — clothing brand or location?) This is the real advantage of Hermes profiles. You create specialist agents with their own memory, tools, and instructions instead of talking to one generic assistant. Quick setup: 1. Create the profile `hermes profile create bob` 2. Connect Telegram `hermes gateway setup` 3. Equip Bob with tools Enable the Notion integration + required MCP servers so he can write to your database. 4. Define the rules Set categories, formatting and clarification logic in his system prompt or SOUL. md .HERMES AGENT TURNS EXPENSE TRACKING INTO ZERO FRICTION. No Siri Shortcuts. No manual entry. Just open Telegram and say: “Hey Bob, I spent $15 on dinner at Guzman Y Gomez.” Done. Hermes profile “Bob” automatically: - Parses the message - Categorizes the expense - Writes directly to your Notion database - Asks clarifying questions when needed This is the real power of Hermes profiles — you create specialist agents with their own memory, tools, and instructions. Quick setup: 1. Create the profile `hermes profile create bob` 2. Connect Telegram `hermes gateway setup` 3. Equip Bob with tools Enable Notion integration + required MCP servers 4. Set the rules Define categories and logic in his system prompt / SOUL.md The best expense system is the one you actually use every day. Hermes + Telegram removes almost all friction. Want the full ready-to-use setup for your own expense tracker? comment “TELEGRAM” below and I’ll send you the complete configuration. Now you have a real personal finance assistant living in Telegram — always on, zero effort. The best expense system is the one you actually use every day. Hermes + Telegram removes almost all friction. This is how you turn an AI into a daily virtual employee. full guide on building these workflows in the article 👇

YanXbt

21,511 Aufrufe • vor 3 Monaten

HERMES AGENT CAN SHARE MEMORY WITH CODEX AND CLAUDE CODE THROUGH HINDSIGHT. ONE MEMORY BANK. ONE AGENT REMEMBERS, EVERY OTHER AGENT KNOWS. the problem: you use Hermes for orchestration. Codex for coding. Claude Code for debugging. each has its own memory. switch between them and you explain the same project three times. Hindsight fixes this. one shared memory bank that every agent reads and writes to. tell Codex: "the test color for this project is purple." switch to Hermes. ask: "what test color did I pick?" Hermes answers: "purple." no copy-paste. no re-explaining. instant recall. HOW IT WORKS: Hindsight runs as a Docker container on your machine. self-hosted. your data stays local. an LLM powers the memory processing (retain, recall, reflect). RETAIN: extracts facts from your conversations. entities, decisions, preferences, project context. saved to the memory bank automatically. RECALL: when you ask a question, Hindsight pulls from semantic search, keywords, graph connections, and temporal data. fused into one answer. REFLECT: deeper reasoning layer. connects memories across sessions. identifies patterns in your work. produces observations that get smarter over time. CONNECT TO HERMES: Desktop app: Settings → Memory and Context → switch provider from Namosin to Hindsight. set API URL to your local Docker container. set bank ID. done. CLI: hermes memory setup → select Hindsight. verify: hermes memory status should show: provider: hindsight, installed, available. CONNECT TO CODEX: npx hindsight-coding-agents install codex \ --self-hosted --server this installs lifecycle hooks: initialize memory on session start. recall context during work. retain the session when done. enable hooks in Codex: Settings → Hooks → trust all three. CONNECT TO CLAUDE CODE (same command): npx hindsight-coding-agents install all "all" connects every detected agent on your machine. Claude Code, Codex, Cursor, and others. one command. every agent shares the same bank. TAGS FOR FILTERING: every memory gets tagged by harness (Hermes, Codex, Claude Code) and optionally by project name. in the Hindsight control plane: filter by harness. see only Hermes memories. or only Codex memories. or search across everything. soft partitions inside one bank. not hard walls. cross-reference when you need to. ONE BANK OR MANY: one global bank: solo dev, related projects. all agents share everything. patterns emerge across projects. per-project banks: unrelated codebases. each project gets its own memory. no cross-contamination. your call. start with one. split when projects diverge. KNOWLEDGE PAGES (v0.9.0): Hindsight auto-generates living summaries from your accumulated memories. components, concepts, conventions, decisions. not static docs. projected from real agent conversations. auto-refresh as new memories land. WHAT TO KNOW: self-hosted via Docker. your data never leaves your machine. backup system built in (admin CLI + scheduled exports). works with any LLM (local Ollama, OpenAI, Codex subscription). memory defense: redact or block sensitive content automatically. 33,000+ memories accumulated in ~10 days of normal use.

YanXbt

29,658 Aufrufe • vor 1 Monat

HERMES AGENT + OBSIDIAN IS A COMBINATION NOBODY IS TALKING ABOUT. Hermes ships with a bundled Obsidian skill. read, search, and create notes in your vault out of the box. why this combination is powerful: Hermes built-in memory is capped. MEMORY.md: 2,200 chars (~800 tokens). USER.md: 1,375 chars (~500 tokens). Obsidian vault has no cap. your agent writes research, session summaries, project context, and learned patterns as linked markdown notes. unlimited depth. the agent creates indexed notes by design. timestamps, backlinks, tags. every note connects to the knowledge graph. three ways to integrate: 1. BUNDLED OBSIDIAN SKILL (simplest) ships with Hermes. reads, searches, creates notes in your vault directly. hermes skills list | grep obsidian 2. OBSIDIAN MCP SERVER (deepest) 30+ tools: full-text search, tag lookup, note management, vault analysis, link analysis, orphan detection. add it via: hermes mcp 3. TELEGRAM + CRON → VAULT (always-on) set a cron job that writes daily summaries, research findings, or task reports directly into your Obsidian vault. your agent feeds the vault while you sleep. you review in Obsidian when you're ready. the unlock: Hermes memory handles what the agent needs to know per session (capped, injected). Obsidian handles everything the agent has ever learned (uncapped, searchable). short-term in Hermes. long-term in Obsidian. both accessible. both persistent. keep the vault scope narrow at first. start with one /Hermes folder. expand once you trust the workflow. 8 Loops Indise Hermes Agent👇

YanXbt

20,617 Aufrufe • vor 3 Monaten

New short course: Long-Term Agentic Memory with LangGraph. Learn to build an agent with long-term memory in this course developed in collaboration with taught by its Co-Founder and CEO, Harrison Chase! Personal assistance and productivity tasks have become important use cases for agents. An important feature of an AI assistant, such as a coding or calendar assistant, is its ability to keep improving over time from its experience. Agent memory is the key capability that enables this. To add memory to an agent, you must first figure out what to store and what to retrieve when it is time to use the information. Additionally, you’ll have to decide when to update the stored information. For example, you might update in each iteration loop of the agent or perform updates in the background, with a helper agent. In this course, you will learn a mental framework to build agents with long-term memory. You'll create a useful email assistant that can respond, ignore, and notify using writing, scheduling, and memory-management tools. You’ll develop your agent's memory by adding facts to its memory store, provide examples to learn the user's preferences, and optimize system prompts to evolve instructions based on previous responses. In detail, you’ll: - Learn how the three types of memory--semantic, episodic, and procedural–and the two update mechanisms–via hot path and in the background–apply to your agents. - Build an email agent with writing, scheduling, and availability tools, along with a router that triages incoming email and handles it accordingly by ignoring, responding, or notifying the user. - Add tools to your email agent that allow it to operate on semantic memory by learning facts about the user, storing them in a long-term memory store, and searching over them in future interactions. - Incorporate episodic memory, in the form of few-shot examples, in the triage step of your agents to help them learn and update user preferences. - Add procedural memory as system prompts, optimized with feedback to improve the instructions the agent follows. Learn how to approach memory in agents, and start building agents with long-term memory with LangGraph! Please sign up here:

Andrew Ng

132,058 Aufrufe • vor 1 Jahr