Hermes BibleUnofficial Docs
← All docs Docs / Using Hermes

Windows (WSL2) Guide

Hermes Agent now supports both native Windows and WSL2. This page covers the WSL2 path; for the native PowerShell install see the dedicated Windows (Native) Gui

Using Hermes
Section
Using Hermes
Source
hermesbible.com/docs/user-guide/windows-wsl-quickstart

Hermes Agent now supports both native Windows and WSL2. This page covers the WSL2 path; for the native PowerShell install see the dedicated Windows (Native) Gui

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Why WSL2 (vs. native Windows)
  2. Install WSL2
  3. Distro choice
  4. Enable systemd (recommended)
  5. Install Hermes inside WSL
  6. Filesystem: crossing the Windows ↔ WSL2 boundary
  7. The two directions
  8. Where to put Hermes and your projects
  9. Getting files back and forth
  10. Line endings, BOMs, and git
  11. "Clone inside WSL or on /mnt/c?"
  12. Networking: WSL ↔ Windows
  13. Case 1 — Hermes in WSL talks to a service on Windows
  14. Case 2 — Something on Windows (or your LAN) talks to Hermes in WSL

Section map

Why WSL2 (vs. native Windows)

Maps why wsl2 (vs. native windows) to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Install WSL2

Maps install wsl2 to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Distro choice

Maps distro choice to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Enable systemd (recommended)

Maps enable systemd (recommended) to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Install Hermes inside WSL

Maps install hermes inside wsl to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Filesystem: crossing the Windows ↔ WSL2 boundary

Maps filesystem: crossing the windows ↔ wsl2 boundary to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

The two directions

Maps the two directions to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Where to put Hermes and your projects

Maps where to put hermes and your projects to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Why WSL2 (vs. native Windows), Install WSL2, Distro choice, Enable systemd (recommended), Install Hermes inside WSL. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: windows, supports, native, wsl2., covers. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitUsing Hermes documentation

Use when you need orientation for windows (wsl2) guide before applying exact upstream commands.

Verify firstWhy WSL2 (vs. native Windows)

Open the source anchor for Why WSL2 (vs. native Windows) and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
  2. Start with the source section for Why WSL2 (vs. native Windows); do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Install WSL2 if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Hermes Agent now supports both native Windows
  • WSL2. This page covers the WSL2 path
  • for the native PowerShell install see the dedicated Windows (Native) Gui

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page