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
- Section
- Using Hermes
- Source
- hermesbible.com/docs/user-guide/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
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat 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.
Upstream outline
Section map
Why Use Worktrees with Hermes?
Maps why use worktrees with hermes? to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Quick Start: Creating a Worktree
Maps quick start: creating a worktree to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Running Multiple Agents in Parallel
Maps running multiple agents in parallel to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Cleaning Up Worktrees Safely
Maps cleaning up worktrees safely to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Best Practices
Maps best practices to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Using hermes -w (Automatic Worktree Mode)
Maps using hermes -w (automatic worktree mode) to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Putting It All Together
Maps putting it all together 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 Use Worktrees with Hermes?, Quick Start: Creating a Worktree, Running Multiple Agents in Parallel, Cleaning Up Worktrees Safely, Best Practices. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: worktrees, often, large, lived, repositories.. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for git worktrees before applying exact upstream commands.
Open the source anchor for Why Use Worktrees with Hermes? and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
- Start with the source section for Why Use Worktrees with Hermes?; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Quick Start: Creating a Worktree if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
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