Loading video...

Video Failed to Load

Go Home

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...

IBuzovskyi's profile picture

YanXbt

4,401 subscribers

29,045 views • 11 days ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵
0:34

You probably don’t use just one AI agent anymore. Maybe Codex for coding. Claude Code for research. Cursor for quick edits. Hermes for the rest. Each one is great at something different. But every time you switch, you have to start over — re-explaining your project, preferences, and the way you like to work. Your agents know how to help you. They just don’t share a memory of you. memU just shipped an update that fixes this. One personal memory, shared across every agent and device you use. What Codex learned last night, Claude Code can remember this morning. 🧵

Hasan

22,362 views • 1 month 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👇
20:54

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

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.
0:34

most agent memory is one file that grows forever and gets re-read every single turn. it overflows the context, overwrites old facts, loses the thread. that's why your agent feels sharp on day one and lost by week three. Sibyl Memory replaces the pile with a structure: → leaner context, lower token cost. a bloated agent file and flat memory get re-read in full every message. Sibyl Memory keeps a light hot layer and retrieves the rest on demand, so each turn carries only the tokens that matter. → relations are first-class. people link to projects, projects to deals, deals to the decisions behind them. ask about one partner and the agent surfaces the whole connected web around them. that relational context is what lets it help run a company. → one source of truth per fact, person, and project. no duplicates, no silent overwrites. works with hermes, claude code, and codex. beta open.

SIBYL

83,832 views • 3 months ago

I gave my local AI agents persistent memory without sending a single byte to a cloud API. It’s called Hindsight. Instead of your agent forgetting everything the moment a session ends, it extracts facts, builds a knowledge graph, and recalls exactly what matters, next time you ask. → Three core operations: retain (store a fact), recall (search memories), reflect (reason across everything it knows), not just a vector database bolted onto a chatbot → Runs fully local when paired with Ollama, no API keys, no cloud costs, and no user data transiting through a third-party provider → Ships as an MCP server out of the box, so Claude, Cursor, or any MCP-compatible client gets persistent memory in one Docker command → Builds “mental models,” living summaries that auto-update as memories accumulate, instead of you re-reading a growing pile of raw logs → Per-user memory isolation lets you run one instance for multiple people or agents without their memories bleeding into each other → Reports top results on the LongMemEval long-term memory benchmark, per the project’s own published numbers Every AI agent today is stateless by default, it knows nothing about yesterday’s conversation unless you re-paste it. Hindsight’s answer: real structured memory, running on your own hardware if you want it there. MIT License. Built by
1:12

I gave my local AI agents persistent memory without sending a single byte to a cloud API. It’s called Hindsight. Instead of your agent forgetting everything the moment a session ends, it extracts facts, builds a knowledge graph, and recalls exactly what matters, next time you ask. → Three core operations: retain (store a fact), recall (search memories), reflect (reason across everything it knows), not just a vector database bolted onto a chatbot → Runs fully local when paired with Ollama, no API keys, no cloud costs, and no user data transiting through a third-party provider → Ships as an MCP server out of the box, so Claude, Cursor, or any MCP-compatible client gets persistent memory in one Docker command → Builds “mental models,” living summaries that auto-update as memories accumulate, instead of you re-reading a growing pile of raw logs → Per-user memory isolation lets you run one instance for multiple people or agents without their memories bleeding into each other → Reports top results on the LongMemEval long-term memory benchmark, per the project’s own published numbers Every AI agent today is stateless by default, it knows nothing about yesterday’s conversation unless you re-paste it. Hindsight’s answer: real structured memory, running on your own hardware if you want it there. MIT License. Built by

Harman

11,032 views • 1 month ago

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access
2:15

i merged all my AI agents into one brain Claude Code, Codex, Gemini: one team, one memory, zero re-briefing result: 8+ hours a week back, and every agent already knows my projects, my clients and how i think here's the setup with Jarvix: 1. dump your context once: projects, clients, writing style, how you make decisions.. it builds your personal model from your actual AI interactions 2. switch agents mid-task with zero re-briefing: Claude Code builds, Codex reviews, Gemini researches, all reading the same context 3. it carries what YOU choose across sessions.. never start a chat from zero again 4. when it's time to act, it pulls the right agents together as one team instead of five separate assistants the unlock isn't another agent. it's that your context finally travels agents without shared memory are five interns on their first day, forever. agents with it are a team that's worked with you for years not more agents. one shared context that's the right bet P.S. thanks to the Jarvix team for the early access

Ronin

15,071 views • 17 days ago

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇
14:28

HERMES AGENT SHIPS WITH A BUNDLED SKILL FOR ANDREJ KARPATHY'S LLM WIKI PATTERN. A SELF-IMPROVING KNOWLEDGE BASE THAT GROWS EVERY TIME YOU FEED IT. mentioned this briefly in the overnight workflow article. here is the full breakdown. what it is: a self-improving knowledge base built as interlinked markdown files. unlike RAG (which rediscovers knowledge from scratch every query), the wiki compiles knowledge once and keeps it current. cross-references stay linked. contradictions get flagged automatically. synthesis reflects everything ingested so far. why this matters for Hermes memory: Hermes built-in memory knows YOU. it remembers your conversations, your preferences, your business context across sessions. but it doesn't know your inbox. or your meeting transcripts. or that article you saved last week. or the expert framework you want it to learn. the LLM Wiki solves that. THE DIVISION OF LABOR human curates sources and directs analysis. agent summarizes, cross-references, files, and maintains consistency. you drop in articles, transcripts, notes. Hermes indexes them, links related concepts, flags contradictions, updates affected pages. your knowledge base grows itself. SETUP IS ONE COMMAND the skill ships with Hermes. enable it. set WIKI_PATH in ~/.hermes/.env: WIKI_PATH=/Users/you/wiki defaults to ~/wiki if unset. then drop anything into it: "index this article into my wiki: [paste URL or text]" Hermes reads it, builds a source page, updates related entries, flags contradictions. THE OBSIDIAN ANGLE set OBSIDIAN_VAULT_PATH to the same directory. now your wiki is visible in Obsidian's graph view. nodes, links, backlinks. all built by Hermes. for headless servers: install obsidian-headless. syncs vaults without a GUI. agent writes from the server, you read on your laptop. THE COMPOUND EFFECT Hermes knows you. the wiki knows your world. combine them and the agent answers questions using BOTH contexts at once. month 1: you explain things twice. month 3: the agent references the wiki on its own. answers get sharper because the knowledge base got sharper. AUTOMATIONS THAT FEED THE WIKI set cron jobs to ingest automatically: "every day at 9am, check Granola for new meetings. add any new transcripts to my wiki under meeting notes." "every morning, scan my Gmail starred items. add anything worth keeping to the wiki." "every week, check arXiv for new papers in [your niche]. summarize and file." your wiki grows while you sleep. Hermes never forgets what gets indexed. THE LIMITATION TO KNOW unlike Hermes memory (which is conversational and lives across sessions), the wiki is a separate knowledge layer. Hermes won't pull from the wiki automatically unless you reference it or save it as a skill. best setup: build an LLM Wiki personality that tells Hermes to consult the wiki when answering strategy questions or domain-specific queries. full HERMES AGENT OVERNIGHT WORKFLOW👇

YanXbt

30,804 views • 2 months ago

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓
3:29

If you use Cursor for coding, Claude Code for debugging, and local agents for automation, you almost certainly have a context problem. Every tool acts like an isolated employee. One assistant forgets what the other just learned. The biggest bottleneck in multi-agent workflows right now isn’t reasoning. It’s collective amnesia, combined with zero communication between agents. Memmy just launched a smart fix for this: a local, cross-agent memory layer. Instead of re-pasting your context everywhere, Memmy gives your stack a shared memory hub: → accumulate knowledge once, then use it across Cursor, Codex, and OpenClaw → automatically scan and import your existing agent history, so you don’t have to start from zero → keep your memory local, while model usage depends on your chosen provider or BYOK setup And it isn’t just a memory plugin. It’s a complete personal AI runtime with both MCP and a CLI. Memmy officially launched on Product Hunt, and the team is giving early users experiencing context fragmentation a free trial with 2M GPT tokens. Check it out and support the team with an upvote: → Best part? It’s also open-source for devs who want to build their own agents 🔥 Repo in 🧵↓

Charly Wargnier

203,456 views • 1 month ago

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇
0:20

HERMES AGENT IS NOW IN THE CLOUD. NO VPS. NO TERMINAL. NO SETUP. PICK A MODEL. PICK A SERVER SIZE. AGENT IS LIVE IN 60 SECONDS. Nous Portal just launched hosted Hermes Agent. two clicks. one minute. done. Nous Research WHAT THIS MEANS: before today: install Hermes on a VPS or your laptop. configure providers. set up gateway. manage updates. run hermes setup. edit config.yaml. great for power users. friction for everyone else. now: go to pick a model. pick a server size. your agent is live and reachable in 60 seconds. no terminal. no SSH. no Docker. same Hermes. same features. same tools. someone else handles the infrastructure. FOR TEAMS: this is where it gets interesting. spin up agents for everyone at your org. each team member gets their own Hermes instance. granular access controls per user. unified billing through Nous Portal. your team gets Hermes on day one. no DevOps needed. no VPS per person. one admin dashboard. one bill. WHAT'S INCLUDED: → 300+ models via Nous Portal (Claude, GPT, Gemini, DeepSeek, Grok, MiniMax, and more) → Tool Gateway (web search, image generation, TTS, browser automation) → all messaging platforms (Telegram, Discord, Slack, WhatsApp, Signal) → full feature set (profiles, cron, kanban, skills, memory, sub-agents, MoA, /goal, /learn, /journey) → automatic updates ONE PORTAL. FOUR TIERS: Free: $0/month. pay-as-you-go credits from $10. Plus: $20/month. $22 in monthly usage credit. Super: $100/month. $110 in monthly credit. Ultra: $200/month. $220 in monthly credit. highest rate limits. every paid tier includes Tool Gateway. one OAuth. one subscription. no extra API keys. SELF-HOSTED IS NOT GOING ANYWHERE: Hermes is MIT licensed. open source. free forever. you can still run it on your laptop, VPS, or GPU cluster. nothing changes for self-hosted users. the cloud version is for people who want the agent running without managing the machine. pick your path: → self-hosted: full control. you manage everything. → cloud: zero ops. Nous manages infrastructure. → hybrid: self-host your main agent, cloud for team members. HOW TO START: cloud: self-hosted: hermes setup --portal both connect to the same Nous Portal. same models. same tools. same billing. learn how to replace your entire team with 8 hermes agents 👇

YanXbt

45,446 views • 1 month ago

how to set up hermes agent step by step. built-in memory, 40+ tools, works on your phone, and what to think of hermes vs openclaw: 1. hermes is a personal AI agent that runs in your terminal. think of it like open claw but with built-in memory, 40+ tools out of the box, and 90% cheaper token costs. you install it with one command. 2. the 3 problems with open claw that hermes solves: no memory (you keep repeating yourself), constant gateway restarts, and zero visibility into what you're spending on tokens. 3. hermes remembers everything. every completed task gets saved to memory. it searches through past logs to find solutions. over time it literally gets smarter at your specific workflows. 4. connect it to open router. you see exact costs per model per task. free models rotate weekly. one founder went from $130 every five days on open claw to $10 on hermes. same output. 5. it comes preloaded with skills. apple notes, imessage, find my, browser, web search, image generation, cron jobs. no hunting for plugins. 6. connect it to obsidian so it reads your entire vault. connect it to gstack for your dev environment. create custom skills for your specific workflows. 7. the biggest money saver: have it write code once for recurring tasks. then it runs without burning tokens every time. stop paying an LLM to do the same scrape or report daily. 8. run it on android via telegram. name your agents. talk to them like coworkers. in this episode imran shows you how to set this up. 9. you can run it bare metal, in docker, or serverless on modal. pick your risk level. i begged imran to come on The Startup Ideas Podcast (SIP) 🧃 and walk through the full installation live. he made it impossibly clear. if you've heard of Hermes Agent and want the clearest explanation of how to get set up like a pro let me know what you want me to cover on the next ep this is the best personal agent setup video on the internet right now. watch
37:00

how to set up hermes agent step by step. built-in memory, 40+ tools, works on your phone, and what to think of hermes vs openclaw: 1. hermes is a personal AI agent that runs in your terminal. think of it like open claw but with built-in memory, 40+ tools out of the box, and 90% cheaper token costs. you install it with one command. 2. the 3 problems with open claw that hermes solves: no memory (you keep repeating yourself), constant gateway restarts, and zero visibility into what you're spending on tokens. 3. hermes remembers everything. every completed task gets saved to memory. it searches through past logs to find solutions. over time it literally gets smarter at your specific workflows. 4. connect it to open router. you see exact costs per model per task. free models rotate weekly. one founder went from $130 every five days on open claw to $10 on hermes. same output. 5. it comes preloaded with skills. apple notes, imessage, find my, browser, web search, image generation, cron jobs. no hunting for plugins. 6. connect it to obsidian so it reads your entire vault. connect it to gstack for your dev environment. create custom skills for your specific workflows. 7. the biggest money saver: have it write code once for recurring tasks. then it runs without burning tokens every time. stop paying an LLM to do the same scrape or report daily. 8. run it on android via telegram. name your agents. talk to them like coworkers. in this episode imran shows you how to set this up. 9. you can run it bare metal, in docker, or serverless on modal. pick your risk level. i begged imran to come on The Startup Ideas Podcast (SIP) 🧃 and walk through the full installation live. he made it impossibly clear. if you've heard of Hermes Agent and want the clearest explanation of how to get set up like a pro let me know what you want me to cover on the next ep this is the best personal agent setup video on the internet right now. watch

GREG ISENBERG

622,600 views • 4 months ago

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👇
0:56

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 views • 2 months ago

Clude is now available as a custom connector on Anthropic Claude. Giving it persistent memory across every conversation. It remembers your projects, your preferences, and the decisions you make, so you never start from zero again. Use Clude across Chat / Co-Work and Claude Code. Add it in 30 seconds, no API key: 1. In Claude: Customize, Add custom connector URL: Enter your email. That's it. Recap for people unfamiliar: Clude deviates from the traditional vector database that many others bolt onto Claude. We are a cognitive memory system modeled on how human memory works. Think traditional memory systems: Calculator > It computes. Fullstop. Excel > Dynamic, formula run, able to share and manipulate Clude scored 86% on LongMemEval, one of the toughest long-term memory benchmarks. This means less hallucinations to traditional platforms. It scores memories by relevance, recency, and importance, links them into a knowledge graph, and consolidates them over time. Tell Claude something, open a new chat, and watch it remember.
0:39

Clude is now available as a custom connector on Anthropic Claude. Giving it persistent memory across every conversation. It remembers your projects, your preferences, and the decisions you make, so you never start from zero again. Use Clude across Chat / Co-Work and Claude Code. Add it in 30 seconds, no API key: 1. In Claude: Customize, Add custom connector URL: Enter your email. That's it. Recap for people unfamiliar: Clude deviates from the traditional vector database that many others bolt onto Claude. We are a cognitive memory system modeled on how human memory works. Think traditional memory systems: Calculator > It computes. Fullstop. Excel > Dynamic, formula run, able to share and manipulate Clude scored 86% on LongMemEval, one of the toughest long-term memory benchmarks. This means less hallucinations to traditional platforms. It scores memories by relevance, recency, and importance, links them into a knowledge graph, and consolidates them over time. Tell Claude something, open a new chat, and watch it remember.

seb

20,554 views • 2 months ago

HERMES AGENT WITHOUT THESE 3 FILES IS A CHATBOT. WITH THEM IT KNOWS WHO IT IS, WHO YOU ARE, AND WHAT IT LEARNED. SOUL.md — who the agent is. first thing in the system prompt. defines personality, voice, values, how it operates, what it can and can't do. structure yours like this: → identity (name, role, relationship to you) → values (what matters, what principles guide decisions) → voice (how it communicates, tone, style) → operations (autonomy level, ground rules) → restrictions (what it never does) → failure protocol (how to operate when things break) lives in ~/.hermes/SOUL.md. auto-seeded on first install. edit anytime. scanned for prompt injection on every load. keep it concise. SOUL.md injects into every turn. a 200-line soul burns tokens on every message. aim for 50-80 lines. one paragraph per section. MEMORY.md — what the agent remembers. persistent facts, insights, preferences. survives across sessions and restarts. capped at ~800 tokens by default: memory: memory_char_limit: 2200 the agent writes to this automatically as it learns about your work. USER.md — who you are. your profile, preferences, context. capped at ~500 tokens by default: memory: user_char_limit: 1375 injected every turn so the agent always knows who it's working for. bonus: AGENTS.md — project-specific instructions. drop one in any project folder. subdirectory AGENTS.md files load lazily during tool calls, not at startup. keeps your system prompt light. prompt stack order on every turn: SOUL.md → tool guidance → MEMORY.md + USER.md → skills index → AGENTS.md → platform hints skills come preloaded. 60+ built-in tools. the agent creates more skills from completed work. you focus on these 3 files. each profile gets its own copy: ~/.hermes/SOUL.md (default profile) ~/.hermes/profiles/researcher/SOUL.md ~/.hermes/profiles/ops/SOUL.md different agent, different soul, different memory, same machine. full breakdown of Hermes as a Personal AI OS in the article 👇
0:54

HERMES AGENT WITHOUT THESE 3 FILES IS A CHATBOT. WITH THEM IT KNOWS WHO IT IS, WHO YOU ARE, AND WHAT IT LEARNED. SOUL.md — who the agent is. first thing in the system prompt. defines personality, voice, values, how it operates, what it can and can't do. structure yours like this: → identity (name, role, relationship to you) → values (what matters, what principles guide decisions) → voice (how it communicates, tone, style) → operations (autonomy level, ground rules) → restrictions (what it never does) → failure protocol (how to operate when things break) lives in ~/.hermes/SOUL.md. auto-seeded on first install. edit anytime. scanned for prompt injection on every load. keep it concise. SOUL.md injects into every turn. a 200-line soul burns tokens on every message. aim for 50-80 lines. one paragraph per section. MEMORY.md — what the agent remembers. persistent facts, insights, preferences. survives across sessions and restarts. capped at ~800 tokens by default: memory: memory_char_limit: 2200 the agent writes to this automatically as it learns about your work. USER.md — who you are. your profile, preferences, context. capped at ~500 tokens by default: memory: user_char_limit: 1375 injected every turn so the agent always knows who it's working for. bonus: AGENTS.md — project-specific instructions. drop one in any project folder. subdirectory AGENTS.md files load lazily during tool calls, not at startup. keeps your system prompt light. prompt stack order on every turn: SOUL.md → tool guidance → MEMORY.md + USER.md → skills index → AGENTS.md → platform hints skills come preloaded. 60+ built-in tools. the agent creates more skills from completed work. you focus on these 3 files. each profile gets its own copy: ~/.hermes/SOUL.md (default profile) ~/.hermes/profiles/researcher/SOUL.md ~/.hermes/profiles/ops/SOUL.md different agent, different soul, different memory, same machine. full breakdown of Hermes as a Personal AI OS in the article 👇

YanXbt

28,924 views • 2 months ago

HERMES AGENT HAS 5 SYSTEMS RUNNING UNDER THE HOOD. UNDERSTAND THEM AND YOU USE THE AGENT 10X BETTER. In this video Alejandro AO 🤗 explained: 1. THE AGENT LOOP every message triggers the same cycle: → you send a message → Hermes builds context (SOUL.md + memory.md + user.md + skills + tools + message history) → sends everything to the LLM → LLM decides: call a tool or respond → if tool call: execute, return result, loop back → if response: deliver to you → after response: memory update (agent checks if anything is worth remembering, writes to memory.md or user.md) this loop is why Hermes gets better over time. the memory update after every response means the agent learns from every conversation. 2. CONTEXT ASSEMBLY what the LLM sees on every turn: → SOUL.md (your agent's personality and rules) → memory.md (facts the agent learned over time) → user.md (facts about you, auto-updated) → AGENTS.md and .hermes.md (project context files) → skill descriptions (loaded on demand) → tool schemas (available actions) → message history (current conversation) if SOUL.md is empty, Hermes falls back to a default system prompt. write your own SOUL.md and the agent becomes yours, not generic. CONTEXT COMPRESSION: conversations hit context limits. Hermes handles this at two checkpoints: preflight: before each turn. if conversation exceeds 50% of context window, compression fires. older messages get summarized. last 20 messages stay intact (protect_last_n). gateway auto-compression: between turns. fires at 85%. more aggressive. prevents API errors before the agent even starts processing your message. after compression, a new session lineage ID is generated. the agent can trace back to the original conversation through SQLite. three things break prompt cache: switching models mid-session, changing memory files, or changing context files. 3. THE GATEWAY the system that keeps Hermes reachable on 27+ messaging platforms. an async loop runs continuously. listens for incoming messages from Telegram, Discord, Slack, WhatsApp, email, SMS, and every other adapter. when a message arrives: → gateway identifies which session it belongs to → queries SQLite for the full message history (session ID = platform prefix + chat ID) → builds the context from scratch → sends everything into the agent loop → delivers the response back to the platform the gateway also runs the session manager. when you send a message while the agent is busy: → default: queued for next turn → /steer: injected without interrupting → /interrupt: stops current work without the gateway, Hermes is a CLI tool. with the gateway, Hermes is an always-on agent you reach from your phone. 4. MEMORY (THREE LAYERS) LAYER 1 — MARKDOWN FILES SOUL.md (identity), memory.md (learned facts), user.md (facts about you). injected into context after the system prompt. updated by the agent after every response. LAYER 2 — SQLITE full transcripts of every session stored locally. FTS5 full-text search across all past conversations. session lineage tracking across compressions. the agent can recall what you discussed weeks ago using /recall or session search. LAYER 3 — EXTERNAL PROVIDERS (optional) 8 supported providers: Mem0, SuperMemory, Honcho, Zep, and more. each works differently (semantic search, LLM extraction, similarity matching). queried after the first message in each session. the agent processes your topic first, then checks external memory for related context from past conversations. not enabled by default. enable for significantly better long-term recall. 5. CRON ENGINE a loop inside the gateway ticks every 60 seconds. each tick checks ~/.hermes/cron/jobs.json for scheduled tasks. if a job is due: → fresh session (no chat history, no memory pollution) → execute the prompt with assigned tools → store the run output as markdown in ~/.hermes/cron/output/[job-id]/ → deliver result to your home messaging platform cron does NOT use the send_message tool. delivery happens at the system level, not the agent level. a cron session cannot create more cron jobs. prevents runaway loops. WHY THIS MATTERS: the agent loop teaches it. the context assembly focuses it. the gateway reaches it. the memory remembers it. the cron engine automates it. five systems. one agent. understanding how they connect changes how you configure every level. full 15 levels breakdown in the article 👇
40:28

HERMES AGENT HAS 5 SYSTEMS RUNNING UNDER THE HOOD. UNDERSTAND THEM AND YOU USE THE AGENT 10X BETTER. In this video Alejandro AO 🤗 explained: 1. THE AGENT LOOP every message triggers the same cycle: → you send a message → Hermes builds context (SOUL.md + memory.md + user.md + skills + tools + message history) → sends everything to the LLM → LLM decides: call a tool or respond → if tool call: execute, return result, loop back → if response: deliver to you → after response: memory update (agent checks if anything is worth remembering, writes to memory.md or user.md) this loop is why Hermes gets better over time. the memory update after every response means the agent learns from every conversation. 2. CONTEXT ASSEMBLY what the LLM sees on every turn: → SOUL.md (your agent's personality and rules) → memory.md (facts the agent learned over time) → user.md (facts about you, auto-updated) → AGENTS.md and .hermes.md (project context files) → skill descriptions (loaded on demand) → tool schemas (available actions) → message history (current conversation) if SOUL.md is empty, Hermes falls back to a default system prompt. write your own SOUL.md and the agent becomes yours, not generic. CONTEXT COMPRESSION: conversations hit context limits. Hermes handles this at two checkpoints: preflight: before each turn. if conversation exceeds 50% of context window, compression fires. older messages get summarized. last 20 messages stay intact (protect_last_n). gateway auto-compression: between turns. fires at 85%. more aggressive. prevents API errors before the agent even starts processing your message. after compression, a new session lineage ID is generated. the agent can trace back to the original conversation through SQLite. three things break prompt cache: switching models mid-session, changing memory files, or changing context files. 3. THE GATEWAY the system that keeps Hermes reachable on 27+ messaging platforms. an async loop runs continuously. listens for incoming messages from Telegram, Discord, Slack, WhatsApp, email, SMS, and every other adapter. when a message arrives: → gateway identifies which session it belongs to → queries SQLite for the full message history (session ID = platform prefix + chat ID) → builds the context from scratch → sends everything into the agent loop → delivers the response back to the platform the gateway also runs the session manager. when you send a message while the agent is busy: → default: queued for next turn → /steer: injected without interrupting → /interrupt: stops current work without the gateway, Hermes is a CLI tool. with the gateway, Hermes is an always-on agent you reach from your phone. 4. MEMORY (THREE LAYERS) LAYER 1 — MARKDOWN FILES SOUL.md (identity), memory.md (learned facts), user.md (facts about you). injected into context after the system prompt. updated by the agent after every response. LAYER 2 — SQLITE full transcripts of every session stored locally. FTS5 full-text search across all past conversations. session lineage tracking across compressions. the agent can recall what you discussed weeks ago using /recall or session search. LAYER 3 — EXTERNAL PROVIDERS (optional) 8 supported providers: Mem0, SuperMemory, Honcho, Zep, and more. each works differently (semantic search, LLM extraction, similarity matching). queried after the first message in each session. the agent processes your topic first, then checks external memory for related context from past conversations. not enabled by default. enable for significantly better long-term recall. 5. CRON ENGINE a loop inside the gateway ticks every 60 seconds. each tick checks ~/.hermes/cron/jobs.json for scheduled tasks. if a job is due: → fresh session (no chat history, no memory pollution) → execute the prompt with assigned tools → store the run output as markdown in ~/.hermes/cron/output/[job-id]/ → deliver result to your home messaging platform cron does NOT use the send_message tool. delivery happens at the system level, not the agent level. a cron session cannot create more cron jobs. prevents runaway loops. WHY THIS MATTERS: the agent loop teaches it. the context assembly focuses it. the gateway reaches it. the memory remembers it. the cron engine automates it. five systems. one agent. understanding how they connect changes how you configure every level. full 15 levels breakdown in the article 👇

YanXbt

51,860 views • 2 months ago

MOST AI AGENTS RESET TO ZERO EVERY TIME YOU OPEN A NEW SESSION. Hermes Agent was built to do the opposite. Every task compounds. Every workflow becomes reusable. Every session teaches the next one. That is the core thesis behind Hermes, and it completely changes how AI agents work. Unlike most AI agents built by software tool companies, Hermes was created by the researchers training the Hermes model family itself. Meaning: The same system used internally to generate training data is now open source and available to everyone. One install gives you access to: Claude. GPT. Grok. Local models via Ollama. Telegram, Discord, Slack, iMessage integrations. Custom skills. Persistent memory. CLI control. But the real unlock is the compounding loop: You give Hermes a task. It records every tool call, decision, and result. Then it converts successful workflows into reusable skills automatically. A Hermes setup running for 3 months becomes fundamentally smarter than a fresh install. That’s the big idea. One of the coolest parts: You literally watch the agent evolve in real time from a blank install into a personalized AI operator. Instead of watching Netflix today, spend 28 mins with this. Follow Dami-Defi for more AI systems, agent workflows, and infrastructure alpha.
0:48

MOST AI AGENTS RESET TO ZERO EVERY TIME YOU OPEN A NEW SESSION. Hermes Agent was built to do the opposite. Every task compounds. Every workflow becomes reusable. Every session teaches the next one. That is the core thesis behind Hermes, and it completely changes how AI agents work. Unlike most AI agents built by software tool companies, Hermes was created by the researchers training the Hermes model family itself. Meaning: The same system used internally to generate training data is now open source and available to everyone. One install gives you access to: Claude. GPT. Grok. Local models via Ollama. Telegram, Discord, Slack, iMessage integrations. Custom skills. Persistent memory. CLI control. But the real unlock is the compounding loop: You give Hermes a task. It records every tool call, decision, and result. Then it converts successful workflows into reusable skills automatically. A Hermes setup running for 3 months becomes fundamentally smarter than a fresh install. That’s the big idea. One of the coolest parts: You literally watch the agent evolve in real time from a blank install into a personalized AI operator. Instead of watching Netflix today, spend 28 mins with this. Follow Dami-Defi for more AI systems, agent workflows, and infrastructure alpha.

Dami-Defi

11,668 views • 3 months ago

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!
28:01

One of my favorite upgrades to Claude Cowork right now: Projects Here's the problem it solves: By default, every new thread starts blank Claude has no memory of what you were working on, what other threads figured out, or what your instructions were So you'd re-explain yourself at the start of every session Or your agents would overlap, contradict each other, or miss context that another thread already had If you've been following my Cowork setup guides, you've already solved part of this — local files and a CLAUDE.md get you most of the way there Projects takes it the rest of the way Shared memory across every thread in the project Permanent instructions that apply everywhere — set once, always on Scheduled tasks that prep your work before you open the app One project HQ to launch every agent from The day-one prompt I paste into every new project: "I just created this project. Read every file in the folder. Then summarize what you know about this workspace — what's here, what I probably use it for, and what instructions you'll follow. If anything is unclear, ask me some questions." Run that once and Claude builds its own understanding of your project workspace from scratch Full video with my live build, including my 4 tips for getting Projects right, and where projects still lack. Send to someone whose ready to Do More with AI, or bookmark to implement this weekend!

JJ Englert

29,809 views • 4 months ago

I just built my second brain with Hermes Agent. It remembers people, companies, projects, and decisions. It pulls from meeting notes, docs, anything I feed it, and cites the source every time. It's this repo called Gbrain, open-sourced by Y Combinator president Garry Tan. install it by pasting this into Hermes: "Install Gbrain following the instructions at Set up the embedding provider, then run gbrain init and gbrain doctor to verify." Add the MCP server so Hermes can call it directly: "Add the Gbrain MCP server and reload." The graph builds itself. Pattern matching on the people and companies already in your notes. 31 points more precise than plain vector search, by their own benchmark. The data from the video is made up so I could show you how it works. Hermes' memory remembers our conversations. Gbrain remembers my world. Open source. Runs local, no server, no Docker.
0:31

I just built my second brain with Hermes Agent. It remembers people, companies, projects, and decisions. It pulls from meeting notes, docs, anything I feed it, and cites the source every time. It's this repo called Gbrain, open-sourced by Y Combinator president Garry Tan. install it by pasting this into Hermes: "Install Gbrain following the instructions at Set up the embedding provider, then run gbrain init and gbrain doctor to verify." Add the MCP server so Hermes can call it directly: "Add the Gbrain MCP server and reload." The graph builds itself. Pattern matching on the people and companies already in your notes. 31 points more precise than plain vector search, by their own benchmark. The data from the video is made up so I could show you how it works. Hermes' memory remembers our conversations. Gbrain remembers my world. Open source. Runs local, no server, no Docker.

Alvaro Cintas

16,800 views • 1 month ago

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 views • 1 month ago

WTF, THIS CHINESE FOUNDER RUNS HIS $10,000+ STARTUP'S ENTIRE WORKFLOW THROUGH HERMES AGENT ON FOUR MACHINES SIMULTANEOUSLY A studio founder just broke down why Hermes is different from every other AI tool right now: → Long-term memory. Most LLMs forget everything after the chat ends. Hermes remembers your work habits and gets sharper the more you use it. → Real execution, not suggestions. This is the core difference from Claude. Claude tells you what to do – you still do it. Hermes takes the instruction and finishes the task itself. → Scheduled tasks that just work. No complicated setup. Set the plan once, it runs on its own. This is what actual "hands-off" looks like. He's not running this on one machine. He's got FOUR laptops running Hermes simultaneously – each one handling a different part of his workflow at the same time. This is what it looks like when one person operates like a full team. He's dropping a full workflow build tutorial next – built for founders and operators trying to lighten their workload. Bookmark this, you'll want to come back to it later.
0:51

WTF, THIS CHINESE FOUNDER RUNS HIS $10,000+ STARTUP'S ENTIRE WORKFLOW THROUGH HERMES AGENT ON FOUR MACHINES SIMULTANEOUSLY A studio founder just broke down why Hermes is different from every other AI tool right now: → Long-term memory. Most LLMs forget everything after the chat ends. Hermes remembers your work habits and gets sharper the more you use it. → Real execution, not suggestions. This is the core difference from Claude. Claude tells you what to do – you still do it. Hermes takes the instruction and finishes the task itself. → Scheduled tasks that just work. No complicated setup. Set the plan once, it runs on its own. This is what actual "hands-off" looks like. He's not running this on one machine. He's got FOUR laptops running Hermes simultaneously – each one handling a different part of his workflow at the same time. This is what it looks like when one person operates like a full team. He's dropping a full workflow build tutorial next – built for founders and operators trying to lighten their workload. Bookmark this, you'll want to come back to it later.

SCOTTY BEAM

11,654 views • 1 month ago

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.
1:18

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,540 views • 2 months ago

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.
1:34

🚀 Global Launch: Jarvix, Your Context OS is now live! Meet the next generation of personalized AI built around your context, your taste, and your way of thinking. #JarvixOS transforms how you work with AI by understanding your patterns, carrying your context across agents, and helping you move from ideas to action. Step into a new era of AI collaboration: • Discover your AI-native archetype • Build your personal AI model from your evolving AI interactions • Never start from zero - your context moves with you across sessions • Coordinate Codex, Claude Code, Gemini, Hermes, OpenClaw, and more as one connected AI team. • Turn insights into your next move, with you always in control Instead of adapting yourself to every agent, Jarvix carries the context you choose, helps you understand what it reveals, and brings the right agents together when you decide to act. Your AI tools shouldn’t work like separate assistants. They should work like one team. That’s the future of AI: Not more agents. One shared context. One Jarvix.

Jarvix

1,687,755 views • 17 days ago