Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| hermes_installation_on_windows_11 [29 June 2026 / 15:36:58] – kadek | hermes_installation_on_windows_11 [09 July 2026 / 18:44:46] (current) – kadek | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Hermes Installation on Windows 11 ===== | ===== Hermes Installation on Windows 11 ===== | ||
| - | We will install | + | This guide walks you through installing |
| - | Create | + | === #1 Create |
| + | |||
| + | * Open Telegram. | ||
| + | * Search | ||
| + | * Send: | ||
| + | |||
| + | /newbot | ||
| + | |||
| + | * Choose a bot name and username. | ||
| + | * Copy the bot token. You will use it later in the .env file. | ||
| + | |||
| + | === #2 Create the Hermes | ||
| + | |||
| + | Replace YourUsername with your Windows username: | ||
| mkdir C: | mkdir C: | ||
| - | Run the setup wizard: | + | === #3 Run the setup wizard |
| + | |||
| + | The setup wizard will create the initial configuration files inside your hermes-data directory: | ||
| docker run -it --rm -v C: | docker run -it --rm -v C: | ||
| - | Create | + | === #4 Create |
| - | docker network create hermes-net | + | Create a file named: |
| - | ocker network connect hermes-net hermes-agent | + | |
| - | Create or edit the docker-compose.yml | + | C: |
| - | services: | + | Paste the following: |
| - | hermes: | + | |
| - | image: nousresearch/ | + | |
| - | container_name: | + | |
| - | + | ||
| - | restart: unless-stopped | + | |
| - | + | ||
| - | volumes: | + | |
| - | - C: | + | |
| - | + | ||
| - | ports: | + | |
| - | - " | + | |
| - | - " | + | |
| - | + | ||
| - | stdin_open: true | + | |
| - | tty: true | + | |
| - | Create or edit the .env file, get the value from the specified service: | + | services: |
| + | hermes-cli: | ||
| + | image: nousresearch/ | ||
| + | container_name: | ||
| + | stdin_open: true | ||
| + | tty: true | ||
| + | volumes: | ||
| + | - C: | ||
| + | hermes-gateway: | ||
| + | image: nousresearch/ | ||
| + | container_name: | ||
| + | command: gateway run | ||
| + | restart: unless-stopped | ||
| + | volumes: | ||
| + | - C: | ||
| + | hermes-dashboard: | ||
| + | image: nousresearch/ | ||
| + | container_name: | ||
| + | command: dashboard --host 0.0.0.0 --port 9119 --no-open | ||
| + | restart: unless-stopped | ||
| + | ports: | ||
| + | - " | ||
| + | volumes: | ||
| + | - C: | ||
| + | |||
| + | === #5 Configure | ||
| + | |||
| + | Create a file named: | ||
| + | |||
| + | C: | ||
| + | |||
| + | Example of the values: | ||
| OPENROUTER_API_KEY=sk-or-v1-ABCDEFGabcdefg0123456789 | OPENROUTER_API_KEY=sk-or-v1-ABCDEFGabcdefg0123456789 | ||
| Line 41: | Line 71: | ||
| TELEGRAM_ALLOWED_USERS=123456789 | TELEGRAM_ALLOWED_USERS=123456789 | ||
| - | Start the docker: | + | Where: |
| - | cd hermes-data | + | |
| + | - OPENROUTER_API_KEY is obtained from OpenRouter. | ||
| + | - TELEGRAM_BOT_TOKEN is obtained from BotFather. | ||
| + | - TELEGRAM_ALLOWED_USERS is your Telegram numeric User ID. | ||
| + | |||
| + | === #6 Start Hermes === | ||
| + | |||
| + | cd C: | ||
| docker compose up -d | docker compose up -d | ||
| - | To connect | + | Wait 10–20 seconds for Hermes to initialize. |
| + | |||
| + | === #7 Verify Hermes === | ||
| + | |||
| + | View the logs for Gateway & Dashboard: | ||
| + | |||
| + | docker logs hermes-gateway --tail 10 | ||
| + | docker logs hermes-dashboard --tail 10 | ||
| + | |||
| + | === #8 Pair Telegram === | ||
| + | |||
| + | Open your Telegram bot and send: | ||
| + | |||
| + | /sethome | ||
| + | |||
| + | Hermes may ask you to complete the initial pairing. Once complete, your private chat becomes the default Home channel. | ||
| + | |||
| + | === #9 Open the Hermes CLI (Optional) === | ||
| + | |||
| + | To access the Hermes | ||
| + | |||
| + | docker exec -it hermes hermes | ||
| + | |||
| + | This connects to the running Hermes instance without stopping the Telegram | ||
| + | |||
| + | ---- | ||
| + | |||
| + | === Daily Startup === | ||
| + | |||
| + | After Windows starts: | ||
| + | |||
| + | - Start Docker Desktop. | ||
| + | - Wait until Docker Desktop reports Engine running. | ||
| + | - Open PowerShell, and run these commands: | ||
| + | |||
| + | cd C: | ||
| + | docker compose up -d | ||
| + | |||
| + | A successful startup should display messages similar to: | ||
| + | |||
| + | PS C: | ||
| + | [+] up 4/4 | ||
| + | ✔ Network hermes-data_default Created | ||
| + | ✔ Container hermes-gateway | ||
| + | ✔ Container hermes-cli | ||
| + | ✔ Container hermes-dashboard | ||
| + | |||
| + | Hermes, the Dashboard, and the Telegram Gateway will start automatically. | ||
| + | Access the dashboard via this URL: http:// | ||
| + | |||
| + | === Daily Shutdown === | ||
| + | |||
| + | You may simply shut down Windows. | ||
| + | Docker will gracefully stop the Hermes container. | ||
| + | |||
| + | Alternatively: | ||
| + | |||
| + | docker compose down | ||
| + | |||
| + | === Updating Hermes === | ||
| + | |||
| + | To update Hermes to the latest version: | ||
| + | |||
| + | docker compose pull | ||
| + | |||
| + | === Backup === | ||
| - | * In Telegram, search @BotFather (the one with the verified tick) | + | Back up the following directory periodically: |
| - | * Send this command: /newbot | + | |
| - | * Pick a name | + | |
| - | * Copy the token, we will add the token to our configuration. | + | |
| + | C: | ||
| + | This folder contains your configuration, | ||
