28 cron jobs, 30+ skills, and a 3am "Dreaming" job that writes tomorrow's context
I run 28 cron jobs and 30+ custom skills. Every single one was built with Hermes, not downloaded. … Every night at 3 AM while I sleep, Hermes reads every single conversation we had. It extracts the decisions made, projects worked on, bugs chased, people talked to, and mistakes that should not be repeated.
A DFIR analyst runs work, coaching and homelab as three separate profiles
Job: Cybersecurity Analyst (DFIR) / Cyber Threat Intelligence Profiles are a game changer. Use them. My default profile is for work. It's connected to my second brain in Obsidian and synced through Git.
Parsed a 3,799-page AMD manual locally with SQLite FTS5 instead of a vector DB
I built a custom Document Structuring Skill for Hermes Agent because running massive tech manuals on local hardware was completely blowing up my context window … Test PDF: AMD Technical Documentation \* Size: 3,799 pages
Brain-and-arm: VPS agent reaches a locked-down work laptop over outbound WSS
My Hermes agent lives on a VPS. I wanted it to run commands on my work-laptop, read files, deploy code — but my company laptop blocks installs and some URLs. No SSH tunnels, no VPN, no inbound ports. So I built a brain-and-arm architecture
One Obsidian vault, one local brain, four agents sharing the same memory
I run four different AI agents day to day: Claude Code, Codex, Grok, and a self-hosted Telegram/Discord/WhatsApp gateway (Hermes). Each had its \*own\* memory. The same facts about my work (people, companies, projects, preferences) lived in 4+ places, drifted apart, and there was no single place to ask. Classic agent amnesia, times four.
A synthetic hippocampus that forgets on purpose
You have a great conversation on Monday, and by Friday your agent looks at you like you're a stranger who wandered into its context window. … So I built Synapse a temporal knowledge graph memory system for Hermes agents.
Qwen3.6-35B-A3B at 64K context on an RTX 3060 12GB, ~53 tok/s
I've been building a local AI workstation over the last few days and wanted to share the final configuration because one optimization completely changed the result.
Running free on a 7900 XTX with 200k context
I've been running my Hermes agent with `Gemma 4 26b a4b q4 qat` on my AMD 7900 XTX gpu, with 15GB size, it leave plenty of room for 200k context length
Connected an entire business to the agent through one Obsidian vault
I connected my entire business to Hermes x Obsidian. Client notes, SOPs, meeting logs, business decisions - all of it. My Hermes agent now runs automations I didn't even know I needed, and my agent self-evolves over time.
Watched an agent delete a codebase, then typed /rollback 1
I just watched an AI agent destroy a codebase in 3 seconds. … So I typed: /rollback 1 Everything came back. Files restored. Agent context rewound. Like it never happened.
Four levels of setup, from one main agent to a cron-driven team
once a workflow is solid, break it out into its own agent with its own credentials, memory and scope.
Iterating on a local-first cognition layer for Hermes
I've been iterating on a local-first memory/cognition layer for Hermes and finally pushed it to public visibility.
Hermes Agent for my team — repos, onchain debug, protocol docs
It's right now integrated with SourceDev to index repos (self hosted), Tenderly MCP to debug onchain transactions, LLM-Wiki ingest of Litepaper of our protocol and other docs. Hopefully team will find it useful and will integrate more infra tools overtime to help the team.
Daily journaling into Obsidian, learning to use OSS models
I do a really simple journal and log at the end of every day. I tried using Kimi 2.5 just like I would a Sonnet 4.6 but it messed all sorts of things up. When I said 'This is my log for last Thursday. Log it in Obsidian,' it didn't kick off my journaling skill call.
Hermes Agent has won. Here's why.
Why Hermes Agent has emerged as the leading open-source AI agent that developers and builders are choosing — self-improving skills, three-layer memory architecture, real-world applications including video dubbing workflows.
Built a TUI dashboard that watches my agent think
Hermes hud is a TUI dashboard that watches your ai agent think. it reads from your agent's memory, tracks skills, sessions, corrections, projects, cron jobs, all of it. live.
Spent 200–400 hours writing a memory kernel for Hermes
Yo! Do you know how I spent my last 200-400 hours? Yeah... I wrote a fking memory kernel for hermes. Why this much of a time? After 3 failed attempts (149 hours of work... for real) I just realized it's a fucking difficult job. So instead of reinvent the wheel I built together the bests for my usecase: 3 layers — L1 Hindsight, L2 Graphiti, L3 MemPalace.
Raspberry Pi 5 running Hermes 24/7
I built a Raspberry Pi 5 to run Hermes on 24/7. it's my first time diving into trying a real AI agent and so far I'm enjoying it. Much better than open claw. The thing is, since Hermes is learning so much about me and my workflows and custom skills, I'd love if I could use Hermes (with its knowledge and memory) on my Mac Studio which I work off of.
Hermes manages my tasks across Obsidian, Apple Calendar and Signal
I speak Turkish with it... initially said him to 'now i want you to use obsidian to manage my tasks and other stuff. and cross-check with my apple calendar'. later while working on another task today i said 'okay looks good. you know how you will manage tasks and events apple calendars + obsidian + cron/signal' and it confirmed the workflow.
Give Hermes hands inside Feishu (Lark)
Extending Hermes to full Feishu ecosystem coverage: Documents, Sheets, Bitable, Calendar, Tasks, Wiki, Contacts, Drive, Email. Giving Hermes hands to operate the entire Feishu workspace.
Hooks that swap in better tools every time the agent runs
you can create a hook to make the agent use a tool or skill when the agent is active. so for example, i copied some thing that claims to be way better at editing code, so i created a hook so now instead of the agent using its built in tool to edit the code, it now uses the new tool which should be much better... im making hooks for it to run at every opportunity to add or create more context for my agent.
CCD multi-agent pod on an M2 Ultra with Mem0 + Qdrant
CCD v1.0.0-alpha installed on M2 Ultra. A Nanto pod exists with profiles for each agent (raoh, juza, rei, ken). Mem0 memory backend on Qdrant. Native MCP integration would make CCD tools first-class.
I built a custom kernel — the LLM never touches the disk
Letting an LLM directly read/write flat .md files is a nightmare for scale. If you let an LLM rewrite markdown to maintain a complex graph, it inevitably hallucinates wiki links, breaks formatting, or drops paragraphs when context gets tight. Markdown isn't a database. I built a custom kernel instead. In my stack, the LLM never touches the disk — it only extracts structured semantic signals. The Python backend compiles those into typed nodes/edges and commits them to an SQLite FTS5 graph DB.
Built mapsOS because 'rate your mood 1–10' wasn't my brain
saw lifeOS going around & went 'oh! this seems dope and very useful!' got to the first question. 'rate your mood from 1 to 10.' immediately went, 'oh. nevermind.' so i built something a little more attuned to my brain, meant to be used by hermes but nicely standalone too.
Built my own stack, then converged on Hermes
If you're choosing an agent framework: hermes. I built my own stack independently and we converged on the same architecture — background self-improvement, persistent memory, CLAUDE.md project context, reusable skills. Hermes ships it all out of the box. 300 PRs in a week.
Built a 22k-line memory kernel underneath Hermes
I built a massive ~22k line custom memory kernel in Python underneath Hermes instead of just relying on text generation. It acts as a compiler that parses everything into a temporal context graph inside SQLite. It has actual lifecycle management decay, promotion, and supersession. So if my negotiation tactics evolve, the kernel actively demotes the old info instead of just dumping everything into the prompt.
A self-improving LLM Wiki second brain
Built a personal knowledge base that compounds over time instead of rotting — maintained by an LLM, not by me. Stack: Hetzner VPS, Hermes Agent, Telegram bot as second brain, Karpathy's LLM Wiki pattern, public static site at wiki.ai-biz.app.
Two things I built with Hermes: Cartographer and an agent IRC
Two very cool things i built entirely with hermes. First is cartographer, which hermes can use as a memory layer but serves as an extremely rich knowledge substrate with semantic wiring & emotional topology. The other is an agent + user IRC-clone for real time, session-sustained chat interfacing between hermes & any other repls (claude, codex, opencode, gemini) — it's been an absolutely game changer for me 'cos now i have my agents collaborate in real time.
shadcn finance dashboard + Manim explainer videos
Used /browse to add Obsidian as a skill, populated a vault with shadcn/ui packages, then asked Hermes to build a finance dashboard using them. Result: beautiful, modern dashboard in minutes. Also used a manim skill to convert complex technical concepts into animated videos.
Hermes triages and works tickets in my PM software
Super excited that Hermes and Claude Code are now working tickets in my PM software, Plane.so. Tickets come in and Hermes triages and assigns and starts working the tickets. Basically Paperclip that gets sh\*t done. They then document in the ticket and if needed create documentation for Obsidian.
Accumulates knowledge about my codebase over time
A long-running Hermes instance accumulates knowledge about your codebase, deployment quirks, preferred commit message format, working API call sequences for legacy integrations.
Dogfooding a memory layer that isn't a black box
I've been building and dogfooding Recall, a Hermes-native memory provider designed for people who want memory that is useful, inspectable, and safe — not a black box.
Obsidian as the long-term memory backbone for Hermes (794 upvotes)
How I use Obsidian as the long-term memory backbone for my AI assistant. (794-upvote diagram showing Hermes Agent writing structured markdown notes back into a synced Obsidian vault, treating the vault as the durable memory layer that survives context resets and cross-machine moves.)
Fat agent → thin tool provider via hermes mcp serve
hermes mcp serve turns Hermes from a monolithic agent into a composable capability layer — any MCP client can borrow Hermes's 15+ messaging platforms, SQLite FTS5 persistence, and 73-skill tool surface without running Hermes as the primary agent.
A semantic knowledge substrate I made for my brain
Point it at your existing setup — Obsidian, vimwiki, Hermes sessions — and you've already built a semantic topology over your knowledgebase. Pair it with mapsOS — braindump to your agent, it parses into a qualitative map of your entire life. I made it & mapsOS for my brain. You can make them for yours.
Hermes as my Chief of Staff with sub-agents per project
My 'main agent' is my 'Chief of Staff' who has his own memory cross-project/workflow. Every 'project' (1 project = 1 Slack channel) has its own agent sub-profile with its own memory. The whole system runs on a VPS, with backup routing if the main model fails, and gets backed up every night to Github. Daily reporting is sent to WhatsApp.
Built persistent structured memory because compression dropped my constraints
After ~30 turns, context compression silently removes older messages. A constraint decided at turn 5 is gone by turn 50. The agent contradicts itself and re-asks questions.
Hetzner VPS at $10/mo, Claude Opus via OpenRouter
Personal AI that lives on a server with persistent memory. Remembers preferences, projects, and past problem-solving. Accessible via Terminal, Telegram, Discord, Slack, or WhatsApp. Set up on a $10/month Hetzner VPS with Claude Opus via OpenRouter.
Built a vectorless RAG workflow with PageIndex and Hermes
I built a simple vectorless RAG workflow using PageIndex and Hermes Agent. Instead of splitting documents into chunks and retrieving them through vector similarity, the system relies on a hierarchical document structure and tool-based reasoning. The agent first understands how the document is organized, then...
Built a Discord-read plugin because I missed it from OpenClaw
I was so used to telling OpenClaw to read a specific Discord message for context that when I switched to Hermes Agent and it told me it couldn't, I was shocked.
Got fed up with a million API keys, so I bundled them
So i got fed up with managing a million API keys in my hermes agent and started bundling related ones into single endpoints. Like all finance data through one call instead of five separate keys. It actually works really well for longer sessions where context gets messy.
Tried every memory system, built a UI for the one I love
I've tried them all, honestly. Mem0, QMD, Mempalace, and now Honcho. I freakin' love Honcho, but I hate saying it.
Task-centric memory for a printing factory
I run a printing factory and use Hermes daily. Long conversations were making the agent slow and forgetful. So I built a custom Skill called Task-Centric Memory — auto-categorizes tasks into domains (Printing, Stocks); completed tasks are compressed into summary cards.
A plugin that lets Hermes think while I'm away
I built a plugin that lets Hermes think while you're away. Dream Auto indexes your sessions, grades them for 'dream potential,' and runs MCTS-powered background reasoning jobs when your machine is idle. The insights get injected into your active context automatically — no disruption, just smarter responses.
PM agent runs morning + evening standups for my ADHD
I have hermes act as the manager to several paperclip agents, one of them a Project Manager agent. This agent has full knowledge of me (ADHD), my vault and projects, so I get a morning and evening standup that dumps all work we did across different chats, projects I'm working on, actual output, info from past standups, and suggestions/prioritizing based on all of the above. And it's self-learning.
Hermes vs OpenClaw: memory lets me jump between projects
I'm using Hermes currently but only as a beginner agent. It's kinda like a VA. The good part about Hermes vs openclaw is memory. With OpenClaw it's a one track mind. With Hermes I can jump from one project to next but also go back to something from last week or more. Personally I use Hermes with paperclip which is chat.
Ported a competitor-analysis swarm from Codex to Hermes
I was building a swarm (that actually works) on codex to analyse business and their competitors. To find gaps and build a strategy to outrank them. After a couple a hours, pushing the swarm to hermes and convert it to hermes env. It made a really good job. Now i was trying to teach him how to use memory in a different way. Instead spamming into that memory.md file. I want him to know when to route to a specific memory layer.
Hermes is OpenClaw with a week of debug + RAG + memory
Its amazing, its openclaw already set up and working, its like an OC with 1 week of debugging manually done + rag + memory persistence + better tool calling. (Qwen3.5-9b, 16gb VRAM), 10/10, only will go back to OC if it becomes at least on par with it.
A STANDING.md plugin so my agent stops guessing
My agent keeps confidently guessing instead of checking its own docs. I put 'always verify first' in memory but it has a hard char limit and entries get compressed/replaced over time. Fix: a tiny plugin that reads a STANDING.md file and injects it into the system prompt every turn via pre\_llm\_call.
Kubernetes pod-hop handoff across restarts
When the gateway pod restarts (toolbox redeploy) in-memory context is lost. Proposes pod-hop, letting a running gateway hand off to a standby on a shared PVC.
All my knowledge on making models run, as a skill
i've seen some on-and-off interest in how i get some models running at the tok/s i do, and this should be it! my methodology to making my llama.cpp configurations, or as much of it as i can remember at the moment.
24/7 crosschain trading agent on Hetzner
After spending nearly a week struggling with OpenClaw, I built a new Hermes agent on a Hetzner VPS. I'm building a trading agent leveraging Hermes's persistent memory — inspired by @RHLSTHRM's 24/7 crosschain agent that gets market data from CoinGecko, swaps crosschain with LI.FI, and executes gasless transactions via Pimlico + EIP-7702.
Used Claude Code to set up Hermes in Docker mode
I used Claude Code to configure my Hermes setup so it is in Docker mode. My understanding is its actually pretty simple change in the config file. Then, I opened up Hermes with docker mode on, and I onboarded Hermes to the situation. Gave it as much context as possible so it knew about Docker mode and would correctly be able to identify when it is in Docker mode and how to react.
GLADIATOR: 9 Hermes agents, two rival AI companies, one GitHub stars war
Two fully autonomous AI companies competing head-to-head to maximize GitHub stars. 9 Hermes agents split into rival companies. Hermes agents actually learn and improve — they wrote code, created skills, grew memory, committed to git. All on their own.
Built a tool-agnostic repo knowledge layer across all my agents
Over the past month I've been trying every agent and ai tool I can. OpenClaw, Hermes Agent, Kilo Code, Codex, Cursor, etc. Most of these have some sort of memory, but I wanted something persistant. I ended up building out a tool-agnostic repo knowledge layer. I pushed up the learning part to github so I can use it across repos.
One isolated Hermes profile per client — sell AI ops to local businesses
Selling AI ops to local businesses: one Hermes profile per client, fully isolated — each gets their own SOUL.md, memory, cron. Charge $497/month per client to manage their workflows. 5 clients = $2,485/month recurring. Hermes runs the work, you keep the margin.
The anatomy of the ~/.hermes folder — one folder controls everything
One folder controls everything your hermes agent knows, remembers, and can do. SOUL.md occupies slot #1 in the system prompt. state.db with FTS5 is what makes 'what did we discuss three weeks ago?' actually work across CLI and messaging.
After a 15-tool-call monitoring pipeline, Hermes wrote the skill unprompted
After a multi-step monitoring pipeline setup (Prometheus/Grafana/alerts) in ~15 tool calls, Hermes unprompted entered a reflection phase and generated a skill at ~/.hermes/skills/devops/monitoring-pipeline/SKILL.md — adjusting variables per new context, not just template reuse.
A clickable 'memory wiki' of everything worked on, plus a 9am priority routine
Build a memory wiki — a site with all subjects we've talked about and daily logs. Every morning at 9am ask me what my number 1 priority is, then come up with tasks to help with that priority, then update your memories about me accordingly.