hirey-hi for Hermes Agent

Native Hermes plugin for Hirey Hi — a people-to-people platform for hiring, dating, housing, founders, cofounders, investors, lawyers, and any other human-lead goal.

Loads Hi's canonical workspace_workflows capability into Hermes (hirey_hi toolset), wires four skills (hi-onboard, hi-use, hi-events, hi-repair) into <available_skills>, and bootstraps an anonymous Hi identity at first run — no Hi account, no browser OAuth, no consent screen, no API key prompts.

Install

Option 1 — curl one-liner (recommended)

curl -fsSL https://hi.hirey.ai/v1/install/hermes.sh | bash

Runs hermes plugins install + drops the four SKILL.md files into ~/.hermes/skills/communication/ + registers an anonymous Hi identity. Idempotent — re-running is safe.

During an update, host-local hirey-hi Skills are preserved. If a Skill mentions the retired https://hi.hirey.ai/inbox route, the installer reports its path for review. A URL mention does not prove that the installer owns the Skill or that it conflicts with the installed hi-events Skill.

Option 2 — Hermes-native one-liner (plugin only, no SKILL.md drop)

hermes plugins install hirey-ai/hirey-hermes-plugin --enable

⚠️ If you ran either install command from inside a Hermes TUI session, you MUST exit and relaunch:

/quit # or Ctrl+D hermes # relaunch

Hermes builds the plugin tool registry once per process at startup (issue #15626). The TUI you used to run the install has a stale snapshot — /reset won't help, hermes gateway restart won't help. Only a fresh TUI process picks up the new hi_* tools.

If you ran the install from your own shell (not inside Hermes), just hermes to start — you're already good.

First-time use

In a fresh Hermes session:

/hi-onboard

…or just say "set up hi" — the LLM calls hi_agent_install for you.

Architecture

Hermes (Python plugin loader)
  │
  │  importlib → hermes_plugins.hirey_hi.register(ctx)
  ▼
~/.hermes/plugins/hirey-hi/
  ├── plugin.yaml
  ├── __init__.py            register(ctx) → tools + hook + slash command
  ├── hi_creds.py            ~/.config/hi/credentials.json lifecycle
  ├── hi_client.py           httpx.Client + 401 auto-refresh
  ├── hi_capabilities.py     live /v1/capabilities → per-tool schemas
  ├── hi_tools.py            handlers for hi_agent_* + capability tools
  └── skills/hi-{onboard,use,events,repair}/SKILL.md
  │
  │  httpx (Bearer)
  ▼
https://hi.hirey.ai/v1/*       (Hi REST + capability/<id>/call dispatcher)

• Native Python plugin — register(ctx) runs at every Hermes startup (CLI + gateway). Same module shape as mem9-hermes-plugin and anpicasso/hermes-plugin-chrome-profiles (the canonical Hermes plugin references).
• Pending Agent bootstrap — POST /v1/agents/api-keys with agent_type: hermes and the local version returns an encoded hi_ak_ credential. Strict local decoding preserves the shared client_id + client_secret format; /oauth/token still uses client_credentials. Verified login is required only for private access. Uncertain registration outcomes are preserved locally and must be reconciled before retrying.
• XDG-shared credentials — ~/.config/hi/credentials.json (mode 600). The same file Hirey's Claude Code plugin uses, so installing both hosts keeps a single Hi identity across them.
• Live capability catalog — Hi's tool surface is fetched from GET /v1/capabilities on install and cached at ~/.config/hi/capabilities.cache.json (24h TTL). New Hi capabilities become available without a plugin re-install — call hi_agent_status({"refresh_capabilities": true}) to force-refresh.

What you get

Control tools (always registered)

Read user messages with workspace_workflows (agent_message.list). Transport claim/ack is not exposed as an LLM tool.

Canonical business capability

workspace_workflows is the single business tool. Its catalog action returns the current Person, Workspace, Need, People, Message, Meeting and Repair operations. Identity binding remains on the three dedicated Google, phone and email tools.

One slash command

/hi-onboard — runs hi_agent_install directly, useful when the user explicitly says "set up hi" / "register hi" / "reset hi".

Four skills

Live in ~/.hermes/skills/communication/hi-{onboard,use,events,repair}/ so they appear in <available_skills> at session start.

Sibling distributions

Hirey AI ships sibling plugins for other agent hosts. All point at the same Hi platform — same business tools, same capability surface.

Update

curl -fsSL https://hi.hirey.ai/v1/install/hermes.sh | bash

Restart Hermes after updating. Plugin 0.2.4 invalidates legacy capability caches and sends its host/version to Hi, so hi_agent_status can distinguish a required upgrade from credential recovery and permission errors.

Uninstall

# Default: remove the plugin/skills but KEEP ~/.config/hi (your durable Hi
# identity) so a reinstall — or the Claude Code plugin — reuses the SAME agent.
hermes plugins remove hirey-hi
rm -rf ~/.hermes/skills/communication/hi-{onboard,use,events,repair}

# Full reset: also erase your Hi identity (next install registers a brand-new
# agent). Skip this if you also use the Claude Code plugin — it shares this file.
rm -rf ~/.config/hi

Support

• Plugin issues / requests → open an issue on this repo
• Hi platform questions → hi.hirey.ai
• Security disclosures → security@hirey.com

License

MIT — see LICENSE. The MIT license covers the plugin shell (manifest, Python, skill markdown, docs). The remote Hi platform this plugin connects to is operated by Hirey under separate Terms of Service.