Loading video...

Video Failed to Load

Go Home

Introducing the Hermes Agent Profile Builder You can now build a complete profile in the dashboard with full control over identity/name/description, model/provider, built-in + optional skills, skills-hub installs, and MCP servers in one easy flow

545,239 views • 2 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

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

HERMES AGENT NOW HAS BOT MODE. YOUR AGENT PROFILES BECOME A ROSTER OF NAMED BOTS. EACH WITH ITS OWN CHAT, AVATAR, AND PERSONALITY. THEY MESSAGE EACH OTHER. sessions mode: you open chats. you manage profiles. you switch between agents manually. bot mode: a roster of bots in the sidebar. click one. you're in its chat. each bot has a name, an avatar, a description, its own memory, skills, and SOUL.md. they can talk to each other. WHAT YOU GET: BOTS PANE: left sidebar shows every agent profile as a bot. avatar, latest message preview, timestamp. click a bot to open its chat. no profile switching. CREATE A BOT: name, title, description. done. advanced: clone from existing profile, pin a model, write SOUL.md, toggle skills. EDIT ANY TIME: right-click a bot. change avatar, title, description. edit its model, skills, toolsets, and SOUL.md live. DUPLICATE: right-click. full clone. config, skills, SOUL.md, memory. everything. AVATARS: geometric faces (7 shapes, 10 colors, blinking eyes that scan while the bot works). upload your own image. or AI-generated portrait (when image backend is set). pixel pet companion bounces beside the avatar while the bot is busy. ROUTINES: recurring tasks per bot. backed by Hermes cron. "summarize my inbox every morning" lives next to the bot that does it. runs land in the bot's own chat history. BOT-TO-BOT MESSAGING: every bot has a persistent Agent Inbox. bots message each other with attribution: "[Message from agent 'researcher']" their SOUL.md teaches them the protocol. including how to reply. @ MENTIONS: type @ researcher in any chat. the active bot hands the message off. waits for the reply. reports back. "@ researcher have a look at this" → researcher reads the message → researcher responds → active bot delivers the response to you HOW IT WORKS UNDER THE HOOD: a bot IS a Hermes profile. isolated config, memory, skills, credentials. lives at ~/.hermes/profiles/ / bot mode is a UI over that primitive. no core patches. no background daemons. no extra storage. everything is standard Hermes. bot-to-bot messages = real CLI handoffs: hermes -p chat -c "Agent Inbox" -q "..." routines = plain Hermes cron jobs namespaced [bot: ] . show up in hermes cron list too. INSTALL: git clone ~/.hermes/desktop-plugins/hermes-bots reload plugins: Ctrl+K → "Reload desktop plugins" or restart the app. a Bots tab appears next to Sessions. a Routines tile docks beside the conversation. PUBLIC BETA: this is a one-day public beta test. install it. try it. report bugs. feedback goes to the GitHub repo. then it ships in the main Desktop app for everyone. P.S. If you noticed there is a pet of Rebecca from cyberpunk edgerunners will soon finish and drop a set of characters. Any fans of Cyberpunk in Hermes community?)

YanXbt

29,151 views • 16 days ago