Local only
On this device
0 / 13 proofs · 0%
Part II · Compounding harness · 12

Own it forever

Backup, update habit, and growth map, without expanding the day-one path.

20 min

What to back up

After mastery
01
Backup files
Copy folders
02
Labs
Optional drills
03
Open Design
Decks · images
04
Roadmap Video
Motion later
  • Hermes home / profile directory (SOUL, memory, config, skills you keep)
  • Obsidian vault and AGENTS.md / project context you rely on
  • .env holds secrets: back up encrypted; never publish
Copy the folders. That is the backup. The harness is portable because it is files.
Sample tree ↘

Stay current

Official docs change often. Run hermes update (or reinstall Desktop) on a cadence you can keep. After updates: doctor or health check, one chat smoke test, gateway still allowlisted. If a flag renames, Installation / Updating docs win over this page.

Updating Hermes ↗ Learning path (official) ↗

When one agent is not enough

Sub-agents: spawn helpers for independent work. Brief them as strangers (failure, paths, definition of done). Least tools. Prefer cheaper children and a strong parent for synthesis. Avoid delegating tightly sequential interactive work.

Profiles: a second Hermes home (own model, memory, gateway, persona) when roles must stay isolated permanently, not a temporary helper.

Kanban / boards: when work must cross agents and survive restarts. Use official multi-agent docs when serial pain is real.

Basics stop at one solid harness. Multi-agent and extra platforms are optional growth, not Part I homework.
Delegation ↗ Kanban multi-agent ↗

Growth map: seven patterns

You already practice tools and approvals. Add the rest when a concrete constraint appears.

  • 1 Tools: day one (done)
  • 2 MCP servers: when work spans external services and APIs
  • 3 Sequential pipeline: multi-step jobs via profiles and wake gates
  • 4 Parallel: research fan-out / batch delegation
  • 5 Routers: assign by type to specialist profiles or board
  • 6 Human in the loop: keep for high-impact actions
  • 7 Dynamic sub-agents: orchestrator spawns help mid-task

Course completion checklist

Checklist · this device0/10

Next ops (optional)

Same product, deeper Settings: Docker terminal backend, remote providers, always-on gateway host, Termux paths. Official docs and Harness Labs (VPS ship, remote shell, session control, prompt budget) cover them after this checklist, not instead of it.

Docker guide ↗ Lab: VPS ship → Lab: remote shell → Lab: Session control → Lab: Prompt budget →

Desktop Kanban (growth)

The first official Hermes Desktop plugin is Kanban: a board in the app for multi-step work across profiles. Enable it only after one profile, tools, and approvals are solid. It is not Part I homework.

  • Plugin can add a page, sidebar entry, hotkeys, and backend endpoints.
  • Multi-profile boards need SOUL + tools working per profile first.
  • Write your own plugin or import via the Desktop plugin SDK when you outgrow defaults.
Lab: Kanban multi-profile → Desktop plugin SDK ↗

Keep going

Official docs are the living manual. Optional labs deepen operations. Open Design is the next live mastery track on Forge.

Hermes docs home ↗ Docs index (llms.txt) ↗ Harness Labs (after mastery) → Open Design → Sample gallery ↘ Contact Delta V ↗ Back to Forge →
Proof of completion

You know which folders to back up, how to brief a sub-agent, and which growth step matches your next constraint.

Proof · this device0/1

Stored on this device only, not sent anywhere.