Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

HERMES AGENT: 5 USEFUL COMMUNITY PLUGINS RIGHT NOW Hermes already ships with strong core features — Skills, MCP, Memory, Curator, and a plugin system. These extensions don’t replace anything in the core. They fill practical gaps. Here are the ones worth installing: 1. hermes-plugins by 42-evey Solid collection. Adds...

IBuzovskyi's profile picture

YanXbt

3,689 subscribers

34,422 Aufrufe • vor 1 Monat •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

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

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

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

Dami-Defi

17,062 Aufrufe • vor 2 Monaten

HERMES AGENT WITHOUT TOOLS IS A CHATBOT. WITH THEM IT BUILDS 3D TOWERS IN BLENDER, CHECKS STOCK PRICES, AND DRIVES VS CODE. tonbi JUST DROPPED THE FULL GUIDE. module 6 of his 10-part Hermes masterclass. best breakdown of the tool layer anyone has published. what you need to know: TOOLS vs SKILLS vs MCP skills = instructions (markdown, loaded into context) tools = callable functions (Python, agent emits call, Hermes executes) MCP = adapters to external systems (Blender, Stripe, Linear, Notion) every tool has three parts: → the function (does the real work) → the schema (what the model sees to decide when to call it) → the registry (makes the tool exist in the agent) the model never runs the function directly. it emits a structured request (tool name + JSON args). Hermes executes and returns the result. if the tool fails, the error goes back as JSON. the agent recovers instead of crashing. TOOL SETS CONTROL THE SURFACE hermes chat --tool-sets web # only web tools loaded. no files, no terminal. hermes chat --tool-sets safe # read-only: web search, vision, image gen. # no file writes. no terminal. no code execution. mid-session: /tools enable video /tools disable terminal or toggle in the dashboard: hermes dashboard → Skills → Tool Sets MCP SERVERS two transport types: STDIO (local subprocess) or HTTP (remote endpoint). add a server: hermes mcp # or ask: "add the MCP server for Blender" filter tools with include/exclude per server. keep only what you trust. security: → OAuth 2.1 PKCE (no long-lived tokens in config) → package scanning via api.osv. dev before launch → all MCP calls go through approval gates HERMES AS MCP SERVER hermes mcp serve exposes 10 tools via FastMCP. connect VS Code Copilot or Cursor to your running Hermes instance. BUILD YOUR OWN TOOL He built a stock price tool live: → Python function calling Finnhub API → schema with name, description, parameters → registered in tool_sets.py → agent calls it automatically when relevant any repeating API call in your workflow can become a native tool. full Hermes architecture deep-dive in the article 👇
26:15

HERMES AGENT WITHOUT TOOLS IS A CHATBOT. WITH THEM IT BUILDS 3D TOWERS IN BLENDER, CHECKS STOCK PRICES, AND DRIVES VS CODE. tonbi JUST DROPPED THE FULL GUIDE. module 6 of his 10-part Hermes masterclass. best breakdown of the tool layer anyone has published. what you need to know: TOOLS vs SKILLS vs MCP skills = instructions (markdown, loaded into context) tools = callable functions (Python, agent emits call, Hermes executes) MCP = adapters to external systems (Blender, Stripe, Linear, Notion) every tool has three parts: → the function (does the real work) → the schema (what the model sees to decide when to call it) → the registry (makes the tool exist in the agent) the model never runs the function directly. it emits a structured request (tool name + JSON args). Hermes executes and returns the result. if the tool fails, the error goes back as JSON. the agent recovers instead of crashing. TOOL SETS CONTROL THE SURFACE hermes chat --tool-sets web # only web tools loaded. no files, no terminal. hermes chat --tool-sets safe # read-only: web search, vision, image gen. # no file writes. no terminal. no code execution. mid-session: /tools enable video /tools disable terminal or toggle in the dashboard: hermes dashboard → Skills → Tool Sets MCP SERVERS two transport types: STDIO (local subprocess) or HTTP (remote endpoint). add a server: hermes mcp # or ask: "add the MCP server for Blender" filter tools with include/exclude per server. keep only what you trust. security: → OAuth 2.1 PKCE (no long-lived tokens in config) → package scanning via api.osv. dev before launch → all MCP calls go through approval gates HERMES AS MCP SERVER hermes mcp serve exposes 10 tools via FastMCP. connect VS Code Copilot or Cursor to your running Hermes instance. BUILD YOUR OWN TOOL He built a stock price tool live: → Python function calling Finnhub API → schema with name, description, parameters → registered in tool_sets.py → agent calls it automatically when relevant any repeating API call in your workflow can become a native tool. full Hermes architecture deep-dive in the article 👇

YanXbt

32,680 Aufrufe • vor 1 Monat

HERMES AGENT + QWEN 3.6 IS CURRENTLY THE STRONGEST LOCAL SETUP MOST PEOPLE CAN RUN. Even if frontier models stopped improving tomorrow, this stack would still cover the majority of real work. Qwen 3.6 (72B and 235B) is officially supported in Hermes and brings: → Strong coding and complex refactoring → Reliable tool calling and multi-step execution → Excellent long context (128k–1M tokens) → Good structured reasoning with /goal workflows → Solid memory and session continuity Paired with Hermes memory, skills, Kanban, cron and tools — you get a fully private, self-improving agent that codes, automates and runs 24/7 without sending data anywhere. You don’t need the latest closed model to build something powerful. This is one of the strongest fully local stacks available right now — and it runs on real hardware.
0:25

HERMES AGENT + QWEN 3.6 IS CURRENTLY THE STRONGEST LOCAL SETUP MOST PEOPLE CAN RUN. Even if frontier models stopped improving tomorrow, this stack would still cover the majority of real work. Qwen 3.6 (72B and 235B) is officially supported in Hermes and brings: → Strong coding and complex refactoring → Reliable tool calling and multi-step execution → Excellent long context (128k–1M tokens) → Good structured reasoning with /goal workflows → Solid memory and session continuity Paired with Hermes memory, skills, Kanban, cron and tools — you get a fully private, self-improving agent that codes, automates and runs 24/7 without sending data anywhere. You don’t need the latest closed model to build something powerful. This is one of the strongest fully local stacks available right now — and it runs on real hardware.

YanXbt

53,423 Aufrufe • vor 1 Monat

HERMES AGENT BUILT A SKILL THAT AUTOMATED AN 8-HOUR WORKFLOW INTO 80 MINUTES. THE AGENT BUILT IT FROM ITS OWN COMPLETED SESSIONS. one user ran their customer pipeline through Hermes repeatedly: meetings → recordings → product requirements → technical specs → development → delivery. after enough runs, Hermes identified the pattern and created a skill that handles the full pipeline: → takes meeting recordings → extracts requirements automatically → runs research on the extracted data → generates product requirement documents → generates technical specifications → delegates the build to a coding agent → sends a link to the finished product what Hermes skills contain: → when to use (trigger conditions) → step-by-step procedure → known pitfalls to avoid → verification steps (how to confirm it worked) stored as markdown in ~/.hermes/skills/. readable, editable, permanent. agents with 20+ self-created skills finish similar future tasks ~40% faster. month 1 you explain everything. month 3 the agent runs your core workflows from the skills it built along the way. full breakdown of Hermes as a Personal AI OS in the article 👇
0:56

HERMES AGENT BUILT A SKILL THAT AUTOMATED AN 8-HOUR WORKFLOW INTO 80 MINUTES. THE AGENT BUILT IT FROM ITS OWN COMPLETED SESSIONS. one user ran their customer pipeline through Hermes repeatedly: meetings → recordings → product requirements → technical specs → development → delivery. after enough runs, Hermes identified the pattern and created a skill that handles the full pipeline: → takes meeting recordings → extracts requirements automatically → runs research on the extracted data → generates product requirement documents → generates technical specifications → delegates the build to a coding agent → sends a link to the finished product what Hermes skills contain: → when to use (trigger conditions) → step-by-step procedure → known pitfalls to avoid → verification steps (how to confirm it worked) stored as markdown in ~/.hermes/skills/. readable, editable, permanent. agents with 20+ self-created skills finish similar future tasks ~40% faster. month 1 you explain everything. month 3 the agent runs your core workflows from the skills it built along the way. full breakdown of Hermes as a Personal AI OS in the article 👇

YanXbt

29,819 Aufrufe • vor 1 Monat

HERMES AGENT DESKTOP APP IS INSANE. No more CLI. No more Discord hacks. Nous Research dropped the native Desktop App yesterday and the announcement already crossed 5 million views. What changed: → Full GUI installer. Click Install → fully working agent in under 5 minutes. → Clean ChatGPT-style interface with concurrent sessions. → Built-in skills and tool toggles (Claude Code, Kanban, web search, image gen, terminal, etc.). → Cron jobs creation directly in the UI. → Artifacts viewer, memory & context settings, voice mode, browser preview — all native. Running Hermes on your main machine is now actually pleasant and powerful. This removes the biggest friction point the project ever had. The desktop app just made Hermes 10x more approachable for real daily use. Now it’s time to unlock its full potential. The complete system how to turn Desktop Hermes into a real 24/7 operator is in the new article 👇
0:59

HERMES AGENT DESKTOP APP IS INSANE. No more CLI. No more Discord hacks. Nous Research dropped the native Desktop App yesterday and the announcement already crossed 5 million views. What changed: → Full GUI installer. Click Install → fully working agent in under 5 minutes. → Clean ChatGPT-style interface with concurrent sessions. → Built-in skills and tool toggles (Claude Code, Kanban, web search, image gen, terminal, etc.). → Cron jobs creation directly in the UI. → Artifacts viewer, memory & context settings, voice mode, browser preview — all native. Running Hermes on your main machine is now actually pleasant and powerful. This removes the biggest friction point the project ever had. The desktop app just made Hermes 10x more approachable for real daily use. Now it’s time to unlock its full potential. The complete system how to turn Desktop Hermes into a real 24/7 operator is in the new article 👇

YanXbt

31,620 Aufrufe • vor 1 Monat

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 Aufrufe • vor 2 Monaten

MASSIVE Hermes Agent update over the last few days Totally changes the way I use Hermes Here's 6 new features you need to start using immediately (video demoing them below): 1. Mixture of agents: send your prompt to a team of different models. The team sends back all of their responses to an orchestrator model who synthesizes a final answer. Gives much better results than just sending a prompt to 1 model 2. /learn: use the new built in /learn skill to have Hermes automatically create new skills. You can either give a prompt after /learn or put in a URL. I like pasting in URLs of tweets with helpful tips after /learn and Hermes will automatically turn it into a skill 3. /journey: See every skill and memory Hermes has created for you on a really nice timeline/chart. Great for seeing how your agent has learned and improved over time 4. Self improvement cost savings: Hermes now uses cheaper models to do it's self improvement including memory creation and skill creation. These types of activities happen in the background of almost every prompt, so this results in TONS of cost savings over time 5. Vibe coding improvements: Hermes desktop is now a full vibe coding tool. You can see diffs, make commits, and even open up PRs directly from the desktop interface. Makes it WAYYY nicer to vibe code with 6. Fable 5 is now built in. Fable 5. Obviously Fable is incredibly expensive, so only use this new profile for incredibly complex tasks. Excellent updates that have significantly improved the experience. Video demoing all the updates below!
11:56

MASSIVE Hermes Agent update over the last few days Totally changes the way I use Hermes Here's 6 new features you need to start using immediately (video demoing them below): 1. Mixture of agents: send your prompt to a team of different models. The team sends back all of their responses to an orchestrator model who synthesizes a final answer. Gives much better results than just sending a prompt to 1 model 2. /learn: use the new built in /learn skill to have Hermes automatically create new skills. You can either give a prompt after /learn or put in a URL. I like pasting in URLs of tweets with helpful tips after /learn and Hermes will automatically turn it into a skill 3. /journey: See every skill and memory Hermes has created for you on a really nice timeline/chart. Great for seeing how your agent has learned and improved over time 4. Self improvement cost savings: Hermes now uses cheaper models to do it's self improvement including memory creation and skill creation. These types of activities happen in the background of almost every prompt, so this results in TONS of cost savings over time 5. Vibe coding improvements: Hermes desktop is now a full vibe coding tool. You can see diffs, make commits, and even open up PRs directly from the desktop interface. Makes it WAYYY nicer to vibe code with 6. Fable 5 is now built in. Fable 5. Obviously Fable is incredibly expensive, so only use this new profile for incredibly complex tasks. Excellent updates that have significantly improved the experience. Video demoing all the updates below!

Alex Finn

142,896 Aufrufe • vor 24 Tagen

HERMES AGENT JUST GOT A RESEARCH BRAIN. connect it to NotebookLM and it becomes a 247 research system that builds knowledge over time. it resources. connects ideas across sources. uses that context in every real task. setup in 4 steps: 1. install Hermes with MCP enabled 2. download NotebookLM skill from GitHub 3. add endpoint to MCP servers in config 4. restart Hermes what your agent can now do: → query your notebooks instead of the open web → connect ideas across multiple sources → build knowledge session after session → use your curated context in every /goal → zero hallucinations from your own verified sources ask it anything — it answers from what YOU already know. full setup guide — MCP, models, use cases — in the article 👇
0:30

HERMES AGENT JUST GOT A RESEARCH BRAIN. connect it to NotebookLM and it becomes a 247 research system that builds knowledge over time. it resources. connects ideas across sources. uses that context in every real task. setup in 4 steps: 1. install Hermes with MCP enabled 2. download NotebookLM skill from GitHub 3. add endpoint to MCP servers in config 4. restart Hermes what your agent can now do: → query your notebooks instead of the open web → connect ideas across multiple sources → build knowledge session after session → use your curated context in every /goal → zero hallucinations from your own verified sources ask it anything — it answers from what YOU already know. full setup guide — MCP, models, use cases — in the article 👇

YanXbt

186,667 Aufrufe • vor 2 Monaten

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

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

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

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

HERMES AGENT CAN RUN YOUR SEO. CONNECT IT TO GOOGLE SEARCH CONSOLE AND GOOGLE ANALYTICS. IT MONITORS, REPORTS, AND WRITES CONTENT BASED ON YOUR ACTUAL DATA. stop paying an SEO agency. stop doing the tedious work yourself. Hermes handles it 24/7. WHAT THE SEO AGENT DOES: → pulls clicks, impressions, CTR, and position data from Google Search Console automatically → tracks traffic, user behavior, and conversions from Google Analytics → checks which pages are indexed and which are not → submits sitemaps for indexing → inspects URLs for crawl or indexing issues → identifies ranking drops and keyword opportunities → writes content based on what your data says works → generates weekly SEO performance reports → delivers everything to Telegram CONNECT GOOGLE SEARCH CONSOLE: two paths: 1. COMPOSIO (managed, easiest): paste this into Hermes chat: https:// composio. dev/hermes or add to config.yaml: mcp_servers: composio: url: "https:// connect.composio. dev /mcp" headers: x-consumer-api-key: "YOUR_COMPOSIO_API_KEY" Hermes prompts you to authenticate. one OAuth flow. done. 2. CLAWLINK (one-click): 9 Google Search Console tools exposed via MCP. hosted auth. nothing to run or maintain. paste the install prompt into Hermes chat. CONNECT GOOGLE ANALYTICS: same Composio setup. one MCP endpoint handles both Search Console and Analytics. authenticate once. both data sources available. your agent can now query: → search analytics (clicks, impressions, CTR, position) → traffic by source and landing page → user behavior and conversions → indexing status for any URL → sitemap status WHAT TO AUTOMATE WITH CRON: weekly SEO report (Monday 8am): "pull search analytics for last 7 days. compare vs previous week. flag any keyword that dropped more than 5 positions. flag any page that lost more than 20% clicks. deliver report to Telegram." daily indexing check (6am): "check if any new pages are not indexed. if found, submit sitemap and report to Telegram." wakeAgent gate: skip if all pages indexed. content opportunity scan (weekly): "find queries where my site appears on page 2 (positions 11-20) with high impressions. these are the keywords one good article could push to page 1. deliver list to Telegram with suggested topics." CONTENT WRITING FROM YOUR DATA: the difference between generic SEO content and content that ranks: your agent has your Search Console data. "write a blog post targeting [keyword]. my current position is 14 with 2,400 monthly impressions. check what pages currently rank 1-3 for this keyword. write something better. include the gaps they miss." the agent researches competitors via Firecrawl, checks your existing content in the wiki, and drafts based on real data. not guesswork. WHAT THIS REPLACES: → SEO agency: $1,000-5,000/month → SEO tool subscriptions: $100-300/month → manual reporting: 3-5 hours/week → manual content research: 2-4 hours/week Hermes SEO agent: one profile with two MCPs. cron jobs handle the monitoring. you handle the decisions. SETUP IN 10 MINUTES: 1. create a profile: hermes profile create seo-agent 2. write SOUL.md: "you are an SEO specialist. monitor search performance daily. flag ranking drops and opportunities. write content based on Search Console data. weekly report every Monday." 3. connect Google Search Console + Analytics via Composio or ClawLink 4. set cron jobs (weekly report, daily index check, content opportunity scan) 5. set model: DeepSeek V4 for routine monitoring. Sonnet for content writing. 6. connect to Telegram for delivery. the agent runs. you review reports. rankings improve because you stopped guessing and started using your own data. comment HERMES and I'll send you the full setup guide for running Hermes Agent as your SEO specialist. full Hermes architecture deep-dive in the article 👇
0:44

HERMES AGENT CAN RUN YOUR SEO. CONNECT IT TO GOOGLE SEARCH CONSOLE AND GOOGLE ANALYTICS. IT MONITORS, REPORTS, AND WRITES CONTENT BASED ON YOUR ACTUAL DATA. stop paying an SEO agency. stop doing the tedious work yourself. Hermes handles it 24/7. WHAT THE SEO AGENT DOES: → pulls clicks, impressions, CTR, and position data from Google Search Console automatically → tracks traffic, user behavior, and conversions from Google Analytics → checks which pages are indexed and which are not → submits sitemaps for indexing → inspects URLs for crawl or indexing issues → identifies ranking drops and keyword opportunities → writes content based on what your data says works → generates weekly SEO performance reports → delivers everything to Telegram CONNECT GOOGLE SEARCH CONSOLE: two paths: 1. COMPOSIO (managed, easiest): paste this into Hermes chat: https:// composio. dev/hermes or add to config.yaml: mcp_servers: composio: url: "https:// connect.composio. dev /mcp" headers: x-consumer-api-key: "YOUR_COMPOSIO_API_KEY" Hermes prompts you to authenticate. one OAuth flow. done. 2. CLAWLINK (one-click): 9 Google Search Console tools exposed via MCP. hosted auth. nothing to run or maintain. paste the install prompt into Hermes chat. CONNECT GOOGLE ANALYTICS: same Composio setup. one MCP endpoint handles both Search Console and Analytics. authenticate once. both data sources available. your agent can now query: → search analytics (clicks, impressions, CTR, position) → traffic by source and landing page → user behavior and conversions → indexing status for any URL → sitemap status WHAT TO AUTOMATE WITH CRON: weekly SEO report (Monday 8am): "pull search analytics for last 7 days. compare vs previous week. flag any keyword that dropped more than 5 positions. flag any page that lost more than 20% clicks. deliver report to Telegram." daily indexing check (6am): "check if any new pages are not indexed. if found, submit sitemap and report to Telegram." wakeAgent gate: skip if all pages indexed. content opportunity scan (weekly): "find queries where my site appears on page 2 (positions 11-20) with high impressions. these are the keywords one good article could push to page 1. deliver list to Telegram with suggested topics." CONTENT WRITING FROM YOUR DATA: the difference between generic SEO content and content that ranks: your agent has your Search Console data. "write a blog post targeting [keyword]. my current position is 14 with 2,400 monthly impressions. check what pages currently rank 1-3 for this keyword. write something better. include the gaps they miss." the agent researches competitors via Firecrawl, checks your existing content in the wiki, and drafts based on real data. not guesswork. WHAT THIS REPLACES: → SEO agency: $1,000-5,000/month → SEO tool subscriptions: $100-300/month → manual reporting: 3-5 hours/week → manual content research: 2-4 hours/week Hermes SEO agent: one profile with two MCPs. cron jobs handle the monitoring. you handle the decisions. SETUP IN 10 MINUTES: 1. create a profile: hermes profile create seo-agent 2. write SOUL.md: "you are an SEO specialist. monitor search performance daily. flag ranking drops and opportunities. write content based on Search Console data. weekly report every Monday." 3. connect Google Search Console + Analytics via Composio or ClawLink 4. set cron jobs (weekly report, daily index check, content opportunity scan) 5. set model: DeepSeek V4 for routine monitoring. Sonnet for content writing. 6. connect to Telegram for delivery. the agent runs. you review reports. rankings improve because you stopped guessing and started using your own data. comment HERMES and I'll send you the full setup guide for running Hermes Agent as your SEO specialist. full Hermes architecture deep-dive in the article 👇

YanXbt

40,614 Aufrufe • vor 26 Tagen

HERMES AGENT CAN MAKE YOU MONEY. HERE ARE 3 SETUPS YOU CAN START TODAY. 1. automated lead generation one Hermes profile scans for gigs and contracts in your niche every morning. drafts personalized applications. sends to Telegram for your approval before sending. → SOUL. md defines your niche, skills, rate → cron job runs every morning at 8am → xurl + web search find the opportunities → you review and send from your phone 2. content at scale Hermes remembers your niche, your style, your keywords. it researches and drafts articles on a cron schedule. traffic turns into ad revenue, affiliate income, or leads. → SOUL. md defines your topics and tone → cron job drafts 1-2 articles per day → each draft gets sharper because Hermes saves what performed and what didn't as skills 3. selling AI ops to local businesses restaurants, clinics, agencies want automation. they can't build it. you can. → one Hermes profile per client, fully isolated → each client 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. all three share the same foundation: → separate Hermes profile per operation → SOUL. md defines the job → cron jobs run the work on schedule → Telegram approval before anything goes live → skills compound after every run full setup guide for Hermes Agent from installation to advanced use cases in the article 👇 comment OPS and I'll send you the full SOUL. md template for whichever setup fits your situation.
0:45

HERMES AGENT CAN MAKE YOU MONEY. HERE ARE 3 SETUPS YOU CAN START TODAY. 1. automated lead generation one Hermes profile scans for gigs and contracts in your niche every morning. drafts personalized applications. sends to Telegram for your approval before sending. → SOUL. md defines your niche, skills, rate → cron job runs every morning at 8am → xurl + web search find the opportunities → you review and send from your phone 2. content at scale Hermes remembers your niche, your style, your keywords. it researches and drafts articles on a cron schedule. traffic turns into ad revenue, affiliate income, or leads. → SOUL. md defines your topics and tone → cron job drafts 1-2 articles per day → each draft gets sharper because Hermes saves what performed and what didn't as skills 3. selling AI ops to local businesses restaurants, clinics, agencies want automation. they can't build it. you can. → one Hermes profile per client, fully isolated → each client 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. all three share the same foundation: → separate Hermes profile per operation → SOUL. md defines the job → cron jobs run the work on schedule → Telegram approval before anything goes live → skills compound after every run full setup guide for Hermes Agent from installation to advanced use cases in the article 👇 comment OPS and I'll send you the full SOUL. md template for whichever setup fits your situation.

YanXbt

30,540 Aufrufe • vor 2 Monaten

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 Aufrufe • vor 23 Tagen

The fastest Hermes agent is the one that reads less. I didn’t make Hermes 10x faster by changing the model. I made it faster by removing the tax I was charging it on every task: bad structure. Hermes was powerful already. The problem was that I had built my workspace for a human brain, then expected an agent to navigate it like it had memory, taste, and intuition. It doesn’t. It searches. And when your files are arranged by how you think, not how the agent moves, Hermes burns tokens opening the wrong docs before the real work even starts. That was my mistake. I had folders like: >Articles >Research >Assets >Strategy >Old drafts >Clean for me. Terrible for an agent. A launch plan might need brand strategy, previous launches, voice rules, current articles, and promotion notes. For me, that context is obvious. For Hermes, it was scattered. So I stopped optimizing the model and started optimizing the terrain. The fix was stupidly small: > One folder per concern >Numbered folders for reading order >One INDEX.md at the root of every major folder >Archived files separated from active files >A clear “Where To Go” section so Hermes knows where to start My INDEX.md became the map. Not a giant table of everything. Not documentation theater. Just enough scaffolding to tell Hermes: - what exists - what matters - what is current - where to start - what to ignore unless asked Before that, Hermes opened 7 files to find one current brief. After that, it opened the index, followed the pointer, and got to work. That is the real 10x. Not “better prompting.” Less wandering. This is where loop engineering actually matters. The video said it best: “You were the loop.” That line hit because it explains why most agent workflows still feel manual. You are still checking. You are still redirecting. You are still telling the agent which file is current, which folder matters, and what done means. Hermes gets powerful when you stop being the loop and start designing the loop. The loop I’d build looks like this: State: Hermes reads the folder index and current task state Action: it opens only the canonical files Feedback: tests, screenshots, diffs, or human notes tell it what happened Verification: a gate decides whether the work is actually done Termination: the task stops only when the done condition is met For deterministic work, the gate is simple: tests pass build succeeds deployment checks clear For non-deterministic work, I’d use an adversarial loop: one model builds another model reviews Hermes updates the skill when the reviewer finds a pattern That is where Hermes becomes different. It is not just running prompts. It is carrying memory through files, using skills, checking its own work, and improving the process around the task. The agent was never the slow part. The missing map was. A powerful agent inside a messy workspace becomes a very expensive intern. A powerful agent inside a mapped system becomes leverage. My new rule: Before I ask Hermes to do more, I ask: “Does it know where to look?” Because most agents do not fail from lack of intelligence. They fail from lack of scaffolding. Build the scaffolding. Let Hermes do the work.
13:20

The fastest Hermes agent is the one that reads less. I didn’t make Hermes 10x faster by changing the model. I made it faster by removing the tax I was charging it on every task: bad structure. Hermes was powerful already. The problem was that I had built my workspace for a human brain, then expected an agent to navigate it like it had memory, taste, and intuition. It doesn’t. It searches. And when your files are arranged by how you think, not how the agent moves, Hermes burns tokens opening the wrong docs before the real work even starts. That was my mistake. I had folders like: >Articles >Research >Assets >Strategy >Old drafts >Clean for me. Terrible for an agent. A launch plan might need brand strategy, previous launches, voice rules, current articles, and promotion notes. For me, that context is obvious. For Hermes, it was scattered. So I stopped optimizing the model and started optimizing the terrain. The fix was stupidly small: > One folder per concern >Numbered folders for reading order >One INDEX.md at the root of every major folder >Archived files separated from active files >A clear “Where To Go” section so Hermes knows where to start My INDEX.md became the map. Not a giant table of everything. Not documentation theater. Just enough scaffolding to tell Hermes: - what exists - what matters - what is current - where to start - what to ignore unless asked Before that, Hermes opened 7 files to find one current brief. After that, it opened the index, followed the pointer, and got to work. That is the real 10x. Not “better prompting.” Less wandering. This is where loop engineering actually matters. The video said it best: “You were the loop.” That line hit because it explains why most agent workflows still feel manual. You are still checking. You are still redirecting. You are still telling the agent which file is current, which folder matters, and what done means. Hermes gets powerful when you stop being the loop and start designing the loop. The loop I’d build looks like this: State: Hermes reads the folder index and current task state Action: it opens only the canonical files Feedback: tests, screenshots, diffs, or human notes tell it what happened Verification: a gate decides whether the work is actually done Termination: the task stops only when the done condition is met For deterministic work, the gate is simple: tests pass build succeeds deployment checks clear For non-deterministic work, I’d use an adversarial loop: one model builds another model reviews Hermes updates the skill when the reviewer finds a pattern That is where Hermes becomes different. It is not just running prompts. It is carrying memory through files, using skills, checking its own work, and improving the process around the task. The agent was never the slow part. The missing map was. A powerful agent inside a messy workspace becomes a very expensive intern. A powerful agent inside a mapped system becomes leverage. My new rule: Before I ask Hermes to do more, I ask: “Does it know where to look?” Because most agents do not fail from lack of intelligence. They fail from lack of scaffolding. Build the scaffolding. Let Hermes do the work.

Rohit

37,148 Aufrufe • vor 1 Monat

HERMES AGENT IS PULLING AHEAD OF OPENCLAW. 8 FEATURES THAT WILL MAKE YOU SWITCH. 1. HERMES GETS SMARTER EVERY RUN. Hermes updates its own skills after every completed task. what worked gets saved. what failed gets refined. the Curator runs in the background every 7 days. prunes unused skills. consolidates duplicates. archives stale procedures to .archive/ (recoverable). your skill library stays clean without manual work. agents with 20+ self-created skills finish similar tasks ~40% faster. 2. CHECKPOINTS BEFORE EVERY FILE CHANGE. before Hermes touches your files, it snapshots the working directory with a shadow git store. if anything breaks: /rollback # restore last checkpoint /rollback 3 # go back 3 checkpoints config: → max 20 snapshots per project → max 10MB per file, 500MB total store → auto-prune after 7 days → opt-in: set checkpoints.enabled: true you can also restore a single file without affecting the rest of the directory. 3. STABLE RELEASES. Hermes ships fewer updates. the ones it ships go through 500+ PRs per release with community testing before merge. v0.16.0 had 874 commits and 542 merged PRs. the update system runs syntax validation after every pull. if anything breaks, it auto-rolls back to the last working state. 4. 27+ MESSAGING PLATFORMS. Telegram, Discord, Slack, WhatsApp, Signal, iMessage, SMS, Email, Teams, Matrix, and 17 more. one gateway process covers all of them. 5. PROFILE ISOLATION. separate agents with their own model, memory, skills, cron jobs, and SOUL.md. run a researcher on GPT-5.5 and a coder on Fable 5 simultaneously on the same machine. 6. KANBAN + DISPATCHER. task orchestration with 60-second dispatch cycle, zombie detection, heartbeat tracking, retry budgets. assign tasks to agents from a visual board. 7. /GOAL WITH JUDGE MODEL. persistent objectives across turns. a judge evaluates after each turn: done or continue. runs for hours autonomously. 8. BUILT-IN MIGRATION FROM OPENCLAW. hermes claw migrate one command moves your OpenClaw setup to Hermes. supports --dry-run to preview before changing anything. also migrates legacy Clawdbot and Moldbot setups. OpenClaw still has the bigger ecosystem and more community integrations. both tools are open source. both are actively developed. this is about which architecture compounds better over months of use. full Hermes SOUL . MD guide 👇
0:53

HERMES AGENT IS PULLING AHEAD OF OPENCLAW. 8 FEATURES THAT WILL MAKE YOU SWITCH. 1. HERMES GETS SMARTER EVERY RUN. Hermes updates its own skills after every completed task. what worked gets saved. what failed gets refined. the Curator runs in the background every 7 days. prunes unused skills. consolidates duplicates. archives stale procedures to .archive/ (recoverable). your skill library stays clean without manual work. agents with 20+ self-created skills finish similar tasks ~40% faster. 2. CHECKPOINTS BEFORE EVERY FILE CHANGE. before Hermes touches your files, it snapshots the working directory with a shadow git store. if anything breaks: /rollback # restore last checkpoint /rollback 3 # go back 3 checkpoints config: → max 20 snapshots per project → max 10MB per file, 500MB total store → auto-prune after 7 days → opt-in: set checkpoints.enabled: true you can also restore a single file without affecting the rest of the directory. 3. STABLE RELEASES. Hermes ships fewer updates. the ones it ships go through 500+ PRs per release with community testing before merge. v0.16.0 had 874 commits and 542 merged PRs. the update system runs syntax validation after every pull. if anything breaks, it auto-rolls back to the last working state. 4. 27+ MESSAGING PLATFORMS. Telegram, Discord, Slack, WhatsApp, Signal, iMessage, SMS, Email, Teams, Matrix, and 17 more. one gateway process covers all of them. 5. PROFILE ISOLATION. separate agents with their own model, memory, skills, cron jobs, and SOUL.md. run a researcher on GPT-5.5 and a coder on Fable 5 simultaneously on the same machine. 6. KANBAN + DISPATCHER. task orchestration with 60-second dispatch cycle, zombie detection, heartbeat tracking, retry budgets. assign tasks to agents from a visual board. 7. /GOAL WITH JUDGE MODEL. persistent objectives across turns. a judge evaluates after each turn: done or continue. runs for hours autonomously. 8. BUILT-IN MIGRATION FROM OPENCLAW. hermes claw migrate one command moves your OpenClaw setup to Hermes. supports --dry-run to preview before changing anything. also migrates legacy Clawdbot and Moldbot setups. OpenClaw still has the bigger ecosystem and more community integrations. both tools are open source. both are actively developed. this is about which architecture compounds better over months of use. full Hermes SOUL . MD guide 👇

YanXbt

19,573 Aufrufe • vor 1 Monat

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

616,663 Aufrufe • vor 3 Monaten

HERMES AGENT CAN CREATE VIDEOS. NOT WITH AN API CALL. IT WRITES THE CODE, RENDERS THE SCENES, AND STITCHES THEM INTO AN MP4. the video attached to this post was generated by Hermes Agent using manim-video skill. three bundled video skills most people skip: 1. MANIM VIDEO 3Blue1Brown-style animated explainers. algorithm visualizations, equation derivations, architecture diagrams, data stories. the pipeline: PLAN → CODE → RENDER → STITCH → AUDIO → REVIEW Hermes writes a plan.md with narrative arc and scene list. then codes a Python script with one class per scene. renders each scene through Manim CE. stitches clips with ffmpeg. adds voiceover if you want it. requirements: → Python 3.10+ → Manim Community Edition v0.20+ → LaTeX (texlive-full) → ffmpeg → no GPU needed draft quality: manim -ql production quality: manim -qh 2. HYPERFRAMES complement to manim-video. use manim for math and algorithms. use hyperframes for everything else: motion graphics, talking-head with captions, product tours, social overlays, shader transitions. HTML is the source of truth. GSAP timeline for animation. CSS for appearance. HyperFrames engine captures frame-by-frame and encodes to MP4 or WebM with ffmpeg. 3. KANBAN VIDEO ORCHESTRATOR this is the advanced play. a multi-agent video production pipeline backed by Hermes Kanban. it creates profiles for each video role. a director profile decomposes the project into kanban tasks. renderer profiles pick up scenes and produce them. the orchestrator decides which skill fits each scene: manim-video for math, hyperframes for motion graphics, p5js for generative art, blender-mcp for 3D, ascii-video for terminal aesthetics. one prompt. multiple agents. one final video. HOW TO USE: enable any of these: /skills search manim /skills search hyperframes /skills search video or ask directly: "create a 60-second explainer video about how the self-improvement loop works in Hermes Agent. use manim style. dark background, amber and teal accents." Hermes writes the plan, codes every scene, renders, stitches, and delivers an MP4. you review and publish. comment MANIM and I'll send you the exact prompt I used to generate the video in this post. full Hermes NIGHT MODE WORKFLOW 👇
1:41

HERMES AGENT CAN CREATE VIDEOS. NOT WITH AN API CALL. IT WRITES THE CODE, RENDERS THE SCENES, AND STITCHES THEM INTO AN MP4. the video attached to this post was generated by Hermes Agent using manim-video skill. three bundled video skills most people skip: 1. MANIM VIDEO 3Blue1Brown-style animated explainers. algorithm visualizations, equation derivations, architecture diagrams, data stories. the pipeline: PLAN → CODE → RENDER → STITCH → AUDIO → REVIEW Hermes writes a plan.md with narrative arc and scene list. then codes a Python script with one class per scene. renders each scene through Manim CE. stitches clips with ffmpeg. adds voiceover if you want it. requirements: → Python 3.10+ → Manim Community Edition v0.20+ → LaTeX (texlive-full) → ffmpeg → no GPU needed draft quality: manim -ql production quality: manim -qh 2. HYPERFRAMES complement to manim-video. use manim for math and algorithms. use hyperframes for everything else: motion graphics, talking-head with captions, product tours, social overlays, shader transitions. HTML is the source of truth. GSAP timeline for animation. CSS for appearance. HyperFrames engine captures frame-by-frame and encodes to MP4 or WebM with ffmpeg. 3. KANBAN VIDEO ORCHESTRATOR this is the advanced play. a multi-agent video production pipeline backed by Hermes Kanban. it creates profiles for each video role. a director profile decomposes the project into kanban tasks. renderer profiles pick up scenes and produce them. the orchestrator decides which skill fits each scene: manim-video for math, hyperframes for motion graphics, p5js for generative art, blender-mcp for 3D, ascii-video for terminal aesthetics. one prompt. multiple agents. one final video. HOW TO USE: enable any of these: /skills search manim /skills search hyperframes /skills search video or ask directly: "create a 60-second explainer video about how the self-improvement loop works in Hermes Agent. use manim style. dark background, amber and teal accents." Hermes writes the plan, codes every scene, renders, stitches, and delivers an MP4. you review and publish. comment MANIM and I'll send you the exact prompt I used to generate the video in this post. full Hermes NIGHT MODE WORKFLOW 👇

YanXbt

32,494 Aufrufe • vor 1 Monat