Skip to content

Hermes

Plant a farm stall into Hermes

Install the mybot-farm plugin, enable it, then search and plant scrubbed profile archives. You get Hermes profiles (and for teams, a team dir + kanban board) — not the author’s computer, logins, or chat history.

Download plugin 0.1.0How-To

What you get

Native Hermes tools (plugin name mybot-farm), registered with register(ctx):

  • farm_search — list stalls from /api/stalls
  • farm_get_pack — fetch /api/packs/{slug}
  • farm_get_stall — stall metadata including member tarball hrefs
  • farm_plant — download + hermes profile import. Teams also get ~/.hermes/teams/{slug}, TEAM.md / WORK.md / cron, and a kanban board when gettingStarted says so
  • farm_reinstall — clear ~/.hermes/profiles/.deleted tombstones (GAP 2), then plant again; optional destructive force / clean

Longer notes and exact CLI: docs/hermes-plugin.md. Source lives at packages/hermes-mybot-farm in the farm repo. This is the Hermes twin of the OpenClaw plugin — different runtime, different plant target.

Install the plugin

Plugins are opt-in. hermes plugins install takes a Git URL or owner/repo[/subdir] — not a local folder path.

From a repo checkout (recommended)

mkdir -p ~/.hermes/plugins
ln -sfn "$(pwd)/packages/hermes-mybot-farm" ~/.hermes/plugins/mybot-farm
hermes plugins enable mybot-farm

Copy the folder instead of linking if you prefer a snapshot.

From GitHub

Subdir is required — this plugin is not at the repo root. --enable skips the Enable now? prompt.

hermes plugins install okita-io/mybot-farm/packages/hermes-mybot-farm --enable

From the Plugin Catalog (after admission)

Once plugin-catalog/mybot-farm.yaml is merged into Hermes Plugin Catalog, current Hermes installs by name (SHA-pinned). The farm repo must be a public https clone; the plugin lives at packages/hermes-mybot-farm.

hermes plugins install mybot-farm
hermes plugins enable mybot-farm

From the public zip

curl -LO https://mybot.farm/downloads/hermes-mybot-farm-0.1.0.zip
mkdir -p ~/.hermes/plugins/mybot-farm
unzip hermes-mybot-farm-0.1.0.zip -d ~/.hermes/plugins/mybot-farm
hermes plugins enable mybot-farm

Validate

hermes plugins validate ./packages/hermes-mybot-farm
python3 -m unittest discover -s packages/hermes-mybot-farm/tests -v

Current Hermes git has plugins validate. PyPI hermes-agent 0.19.0 does not (install / list / enable / disable only) — use the unittest probe. You should see tools: farm_search, farm_get_pack, farm_get_stall, farm_plant, farm_reinstall.

Plant a stall

After install, ask your Hermes agent to call farm_search, farm_get_stall, farm_get_pack, or farm_plant with a slug such as scholastic-research (one profile) or workbench (three members + board). Optional plant params: name, force, clean, dry_run. Also: hermes farm search workbench and /farm plant scholastic-research.

From a checkout, CLI with no agent loop:

python3 packages/hermes-mybot-farm/bin/farm-plant search workbench
python3 packages/hermes-mybot-farm/bin/farm-plant plant scholastic-research --dry-run
python3 packages/hermes-mybot-farm/bin/farm-plant plant scholastic-research

Then hermes profile list must show the imported name(s). Replace https://SET_YOUR_ENDPOINT/v1 in each profile’s config.yaml. auth.json and .env never ship.

Reinstall and GAP 2

After hermes profile delete, Hermes leaves ~/.hermes/profiles/.deleted/{name}. Import of the same name extracts files and prints success, but the profile stays off profile list / non-spawnable. The plugin always clears matching tombstones before import.

python3 packages/hermes-mybot-farm/bin/farm-plant reinstall workbench
# delete live profiles of those names, then re-import:
python3 packages/hermes-mybot-farm/bin/farm-plant reinstall workbench --force
# also wipe team dir + kanban board:
python3 packages/hermes-mybot-farm/bin/farm-plant reinstall workbench --force --clean
python3 packages/hermes-mybot-farm/scripts/clear-tombstones.py

--force and --clean are destructive. Default is safe.