Hermes Hearth update: every new feature step by step
This guide goes with the video "Hermes Just Got A HUGE Update". It has every step from the video, with the commands and prompts ready to copy.
28 steps · 6 parts · copy-paste ready
// Contents
Part 01 / 06 — Every Hermes in one Desktop app
Part 02 / 06 — Bots and group chats
Part 03 / 06 — Who answers in a group
Part 04 / 06 — One gateway: move a chat to Telegram
Part 05 / 06 — /rewind
Part 06 / 06 — The Desktop app in a browser tab (Webapp)
- 18Turn the Webapp on
- 19Restart the gateway
- 20Option A (without Tailscale): open a tunnel
- 21Option A: get your link
- 22Option B (with Tailscale): put Tailscale on your server (once)
- 23Option B: sign in to Tailscale
- 24Option B: give the Webapp a private address (once)
- 25Option B: tell Hermes that address (once)
- 26Option B: restart the gateway
- 27Option B: get your link (every time)
- 28Sign out every browser tab
Prerequisites
- ▸Hermes v0.23.0 or newer on every server you connect
- ▸Hermes Desktop on your Mac or Windows PC
All 28 steps are . Or skip the setup:
Membership
Build beyond this tutorial
- 3 paid tutorials of your choice today
- Every new tutorial, the day it drops
- One-line auto-installers for what you unlock
- Private members Telegram
- Priority inbox, reply within 24h
$10/month. $20 covers your first 2 months.
Become a memberGet all 28 steps by email
No card needed.
Want them as a single Markdown file? We'll email you a 6 digit code to confirm.
Every Hermes in one Desktop app
You add each Hermes once. Then you switch between them from one menu. Where you add them: Settings → Gateways → Saved connections → + Add connection. Local is the Hermes on this computer, Hermes Cloud is Hermes in Nous' cloud, Remote gateway is a Hermes with a web address and a login (Hostinger, or Tailscale), and SSH is any VPS you log in to with root@IP. Give every connection a clear name, like Hostinger or Contabo. That name is what you see when you switch.
Check your Hermes version
Your server
hermes --versionYou need v0.23.0 or newer.
Too old? Update it
Your server
hermes updateTell me which Hermes version this server runs. If it is older than 0.23.0, update
Hermes and tell me the new version.hermes --version shows v0.23.0 or newer.A Hermes on Hostinger (Remote gateway)
Hostinger, then Hermes Desktop
In Hostinger, open your VPS → click Open App. A new tab opens with your Hermes.
Copy the address from https:// up to the first / after the domain. Leave the / out. Example: https://hermes-abc123.hstgr.cloud
Then in Desktop: Settings → Gateways → Saved connections → + Add connection → Remote gateway, and fill in:
- Name: anything you like, for example Hostinger
- Gateway URL: the address you copied, e.g.
https://hermes-abc123.hstgr.cloud - Authentication: Sign in
Click Sign In. A second Sign In button appears. Click the lower one. Type the Hermes username and password from your Hostinger setup. The username is often hermes.
Click Save connection, then Test. Save stays grey until the Name field has text.
Check: you see "Hostinger reachable".A Hermes on your Tailscale network (Remote gateway)
Your dashboard, then Hermes Desktop
Your computer and the server must be on the same Tailscale account.
Accordo Pro or NEXORA: open your dashboard → Integrations → Hermes Desktop. It shows the address, the username and the password.
Add it the same way as step 3, with that address:
- Name: for example Accordo Pro
- Gateway URL: the address from the card, e.g.
https://myserver.tail1234.ts.net:8445
Any VPS over SSH: check if you already have a key
Your own computer
Desktop logs in to your server with a key, not a password. You make the key once and copy it to your server once.
These steps run on your own computer. Mac: open Terminal. Windows: open PowerShell.
ls ~/.sshdir $env:USERPROFILE\.sshDo you see id_ed25519.pub? Then you already have a key. Skip to step 7.
Make a key
Your own computer
ssh-keygen -t ed25519Press Enter at every question.
Does it ask Overwrite (y/n)?? Type n. You already have a key, and overwriting it locks you out of your servers.
Copy the key to your server
Your own computer
ssh-copy-id root@YOUR-SERVER-IPtype $env:USERPROFILE\.ssh\id_ed25519.pub | ssh root@YOUR-SERVER-IP "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys"Type your server password. This is the last time you need it.
Does it ask Are you sure you want to continue connecting?? Type yes.
Check: log in without a password
Your own computer
ssh root@YOUR-SERVER-IPYou are logged in, and nobody asked for a password. Type exit to leave.
Add the server in Desktop (SSH)
Hermes Desktop
Settings → Gateways → Saved connections → + Add connection → SSH, and fill in:
- Name: for example Contabo
- SSH host:
root@YOUR-SERVER-IP - Hermes path: leave it on auto-detect
Click Save connection, then Test.
Check: you see "Contabo reachable".Switch between your setups: at the bottom of the Sessions list, click the device name, then pick a setup.Check: the sessions and bots of that setup load.Bots and group chats
The Bots tab lists every agent from every setup, grouped by setup. Click one to talk to it.
Keep Hermes running on that server (SSH servers only, once)
Your server
First switch to the setup whose bots you want. A group lives on one setup. Use the switcher at the bottom of the Sessions list. If you skip this, Desktop says the group will live on that other setup.
A group needs Hermes running on the server all the time, not only while Desktop is open. Hostinger and Tailscale setups already run all the time. Skip this step for those.
On the server:
hermes gateway install --system --run-as-user rootsudo hermes gateway install --systemInstall the Hermes gateway on this server as a system service that starts at boot.
Don't restart or stop it yourself. Tell me the command if it needs me to run it.Check the gateway
Your server
hermes gateway listMake the group
Hermes Desktop
Bots tab → + → New Group Chat → pick 2 to 6 bots → Create Group. Rename it with the pencil icon.
Then send a message like Hi everyone.
Who answers in a group
Give the group a purpose, then decide who answers a message that names nobody.
Open the group settings and pick who answers
Hermes Desktop
Click the group's name at the top of the chat (not the arrow next to it). The Group chat settings panel opens.
Fill in Purpose and Shared notes (optional). Every bot in the group reads them. Example purpose: Plan and ship my client websites.
Under Who answers a message that names nobody, pick one:
- Everyone answers: every bot replies
- Lead: (a bot): the lead answers and hands work to the other bots
- Pick who answers automatically: Hermes picks the best bot for each message
Click Save.
Check: with "Pick who answers automatically" on, ask a coding question. Your developer bot answers.Tip: @name and @everyone always go straight to those bots.
One gateway: move a chat to Telegram
Hermes now runs one gateway per machine. Desktop, the terminal and Telegram all use that one gateway. So a chat can move from your desk to your phone and back.
Connect Telegram to this Hermes (once)
Your Hermes chat
Skip this if your bot already answers you in Telegram. Otherwise paste this into your Hermes chat:
Connect Telegram to this Hermes. Walk me through making a bot with BotFather, then
save the bot token and my Telegram user ID. Don't restart the gateway yourself.
Tell me the command if it needs one.Tell Hermes where handoffs go (once)
Telegram
Open your bot in Telegram and send:
/sethomeHand off the chat
Hermes Desktop
In a Desktop chat, type:
/handoff telegramWait until the agent finishes its answer first.
Check: Desktop says the session was handed off to Telegram. Your bot sends "Continuing here in Telegram".Keep talking on your phone. Example: "I'm on my way to Sarah now. Give me the three most important questions only." The agent still knows everything from the Desktop chat.Back at your desk: open the chat under Telegram in the Desktop sessions list and carry on.Use the Desktop app for /handoff. In the terminal chat, Hermes 0.23.1 says it isn't available yet.
/rewind
Go back to an earlier message when a chat goes the wrong way. The wrong turns leave the chat, so they stop confusing your agent.
Open the list and pick a message
Your chat
In the chat, type:
/rewindOr press Esc twice on an empty message box.
Choose the message to go back to and press Enter. It comes back in the message box. Edit it and send. Everything after that message is removed from the chat.
Want to keep the original chat? In the terminal chat, press F instead of Enter. Hermes makes a copy of the chat from that point, and the original stays as it was.
Check: the chat now ends at the message you picked.The Desktop app in a browser tab (Webapp)
The full Desktop app in any browser, with nothing to install on that computer. Turn it on first (steps 18 and 19), then pick Option A without Tailscale or Option B with Tailscale.
Turn the Webapp on
Your server
hermes config set webapp.enabled trueTurn on the Hermes Webapp on this server (webapp.enabled true). Don't restart the
gateway yourself. When you're done, tell me to run: hermes gateway restartThen run step 19.
Restart the gateway
Your server
hermes gateway restartOption A (without Tailscale): open a tunnel
Your own computer
Using Tailscale? Skip to step 22.
ssh -L 9120:127.0.0.1:9120 root@YOUR-SERVER-IPThis logs you in to the server. Keep this window open.
Option A: get your link
In that same window
hermes webapp --no-openThe first time, it builds the app. That takes a few minutes.
Check: it prints a link. Open it in your browser within 60 seconds. You see the Desktop app in a tab.Option B (with Tailscale): put Tailscale on your server (once)
Your server
curl -fsSL https://tailscale.com/install.sh | shSet up the Hermes Webapp for my Tailscale network. Install Tailscale on this server
and give me the sign-in link. Serve http://127.0.0.1:9120 with tailscale serve on
https port 8443, then set webapp.public_url to that address. Don't restart the
gateway yourself. When you're done, tell me to run: hermes gateway restartInstead of steps 22 to 26.
Option B: sign in to Tailscale
Your server
sudo tailscale upOpen the link it prints and sign in.
Option B: give the Webapp a private address (once)
Your server
sudo tailscale serve --bg --https=8443 http://127.0.0.1:9120It prints your address. Example: https://myserver.tail1234.ts.net:8443
Does it ask you to turn on HTTPS? Open the link it gives you and click Enable.
Option B: tell Hermes that address (once)
Your server
hermes config set webapp.public_url https://myserver.tail1234.ts.net:8443Option B: restart the gateway
Your server
hermes gateway restartOption B: get your link (every time)
Your server
hermes webapp --no-openSign out every browser tab
Your server
hermes webapp --sign-outStay safe
Never open ports 9119 or 9120 to the internet. A signed-in tab can run commands on your server.
Never share the key file without .pub (your private key). The .pub file is safe to copy.
The 60-second Webapp link works once. Don't paste it into chats.
Common problems and fixes
Save connection stays grey: the Name field is empty. Type a name.
Remote gateway Test fails: the address has a / at the end or no https://. Copy it again as in step 3.
hermes: command not found: your terminal opened before the install. Log out and back in.
It still asks for a password after copying the key: your key has another name than id_ed25519. Go back to step 5.
Connection reset by peer: your server blocks you for a few minutes after failed logins. Wait 10 minutes, then try once.
Desktop Test can't find Hermes over SSH: put /root/.local/bin/hermes in Hermes path. Not logged in as root? Use /home/YOUR-USER/.local/bin/hermes.
"can't host a bot for a group chat on another computer yet": Hermes on that server stops when Desktop closes. Run step 10, then click Retry.
Desktop says the group will live on another setup: you picked bots from a setup you haven't switched to. Switch to it first (step 10).
/handoff says there is no home channel: send /sethome to your bot in Telegram (step 15).
"/handoff is not available on the shared gateway yet": you typed it in the terminal chat. Use the Desktop app.
"The gateway started before the Webapp was turned on": run hermes gateway restart, then hermes webapp --no-open again.
"channel 3: open failed: connect failed: Connection refused": the tunnel works, but nothing runs on that port yet. Run hermes webapp --no-open.
"REMOTE HOST IDENTIFICATION HAS CHANGED": your server was reinstalled. Run ssh-keygen -R YOUR-SERVER-IP, then connect again.
What the parts of the commands mean
ssh-keygen -t ed25519: make a key pair, a private key and a .pub key.
ssh-copy-id: copy your .pub key to the server's list of allowed keys.
~/.ssh: the folder where your computer keeps its keys.
gateway install --system: run Hermes as a service that starts with the server.
/sethome: make this Telegram chat the place where handoffs land.
-L 9120:127.0.0.1:9120: your computer's port 9120 leads to the server's port 9120.
127.0.0.1: "this machine only". Nothing outside can reach it.
--no-open: print the link instead of opening a browser on the server.
tailscale serve --bg: share a page inside your Tailscale network only, in the background.
--https=8443: the port of the private HTTPS address.
// What you set up
Every Hermes you run in one Desktop app (Hostinger, Tailscale, any VPS over SSH). Group chats with your bots. A lead bot, or Hermes picks who answers. A chat that moves from Desktop to Telegram with /handoff. /rewind for a chat that went the wrong way. The Desktop app in a browser tab.
Stuck on a step? Drop a comment on the video, or book a session and we'll walk through it together.
Usage & License
Use the prompts and downloadable templates on this page in your own personal and commercial projects. What's not allowed: reselling, repackaging, redistributing, or republishing this material — on YouTube, Gumroad, paid courses, newsletters, or anywhere else. Send people to komputermechanic.com instead. Violations get reported and taken down.