Git Worktrees
Hermes Agent is often used on large, long‑lived repositories. When you want to: Run multiple agents in parallel on the same project, or Keep experimental refact
Hermes Agent is often used on large, long‑lived repositories. When you want to: Git worktrees are the safest way to give each agent its own checkout without duplicating the entire repository. This page shows how to combine worktrees with Hermes so each session has a clean, isolated working directory. …
What this page covers
- Why Use Worktrees with Hermes?
- Quick Start: Creating a Worktree
- Running Multiple Agents in Parallel
- Cleaning Up Worktrees Safely
- Best Practices
- Using hermes -w (Automatic Worktree Mode)
- Putting It All Together
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
More in Using Hermes
CLI Interface
Hermes Agent's CLI is a full terminal user interface (TUI) — not a web UI. It features multiline editing, slash command autocomplete, conversation history, inte
TUI
The TUI is the modern front end for Hermes — a terminal UI backed by the same Python runtime as the Classic CLI. Same agent, same sessions, same slash commands;
Configuration
All settings are stored in the directory for easy access. TIP — Easiest path to a working Run — one OAuth gets you a model provider and all four Tool Gateway to
Configuring Models
Configuring Models Hermes uses two kinds of model slots: Main model — what the agent thinks with. Every user message, every tool call loop, every streamed respo
Sessions
Hermes Agent automatically saves every conversation as a session. Sessions enable conversation resume, cross session search, and full conversation history manag
Profiles: Running Multiple Agents
Profiles: Running Multiple Agents Run multiple independent Hermes agents on the same machine — each with its own config, API keys, memory, sessions, skills, and