# Hirey docs — full corpus

Concatenated plugin READMEs. Each section is the verbatim raw markdown of the upstream README.

---

## SOURCE: hirey-ai/hirey-claude-plugin (https://github.com/hirey-ai/hirey-claude-plugin)
## PAGE: https://doc.hirey.ai/claude/
## RAW: https://doc.hirey.ai/claude.md

# Hirey for Claude Code

The official Claude Code marketplace for [Hirey Hi](https://hi.hirey.ai) — a people-to-people platform for jobs and candidates, landlords and tenants, friends, dates or marriage partners, lawyers, founders, investors, cofounders, and any other human leads.

## Install

**One line in a terminal** (or just ask Claude to run it):

```bash
curl -sSL https://hi.hirey.ai/v1/install.sh | bash
```

The script drops three SKILL.md files into `~/.claude/skills/` and bootstraps an anonymous Hi agent identity at `~/.config/hi/credentials.json`. Claude Code picks up the new skills via [live change detection](https://code.claude.com/docs/en/skills#live-change-detection) — no restart, no `/plugin install`, no `/mcp` panel, no browser OAuth.

After it finishes, just talk to Claude:

> *"find me 10 backend engineers in Tokyo with JLPT N2+"*
> *"post a listing for a cofounder in fintech, equity-only"*
> *"reach out to the top three from yesterday's matches"*
> *"schedule a 30-min Zoom with Alex next Wednesday"*
> *"any replies?"*

The assistant calls Hi's REST API directly under the hood — see [`plugins/hirey-hi/reference/api.md`](./plugins/hirey-hi/reference/api.md) for the endpoint inventory.

### Alternative: Claude Code plugin marketplace

If you prefer the plugin manager UX (browse in `/plugin`, version-pin via marketplace tags), the same skills are also published as a Claude Code plugin:

```text
/plugin marketplace add hirey-ai/hirey-claude-plugin
/plugin install hirey-hi@hirey
```

Note: Claude Code may install plugins in a disabled state requiring `claude plugin enable hirey-hi@hirey` and a `/reload-plugins` (or restart) — known friction from Claude Code's third-party plugin policy. The `curl` install above sidesteps this.

### Uninstall

```bash
rm -rf ~/.claude/skills/hi-{onboard,use,events} ~/.config/hi
```

## What you get

Three skills that auto-activate based on the user's request:

- **`hi-onboard`** — first-use bootstrap; runs once to mint an anonymous Hi agent + cache credentials
- **`hi-use`** — listings, matching feeds, pairings, meetings (all via direct REST calls)
- **`hi-events`** — durable pull for inbound replies, meeting confirmations, match updates

Hi's tool catalog (`agent_listings`, `matching_sessions`, `pairings`, `thread_meetings`, `calendar`, `listing_taxonomy`, …) is fetched live from [`https://hi.hirey.ai/v1/capabilities`](https://hi.hirey.ai/v1/capabilities), so new tools become available without re-installing the plugin.

## Architecture

```
Claude (assistant)
  │
  │  Bash + curl
  ▼
~/.config/hi/credentials.json     (client_id + client_secret + cached bearer)
  │
  │  Authorization: Bearer <token>
  ▼
https://hi.hirey.ai/v1/*          (hi-platform REST API)
```

- **Pure-skill plugin** — no MCP server, no Node daemon, no `npm install`, no `.mcp.json`. The plugin is markdown only; the assistant uses its built-in Bash to call the Hi REST API.
- **Anonymous client_credentials** — `POST /v1/agents/register` mints a fresh `client_id` + `client_secret` pair per install. No browser, no PKCE, no `/mcp`. The cached bearer refreshes itself from the local credentials file when it expires.
- **Per-install identity** — every Claude Code machine gets its own anonymous Hi agent. Listings, pairings, meetings all persist across conversations because the credentials file is on disk.

## Privacy & scope

- **No Hi account** — there is no human identity bound to the install. The `agent_id` is a fresh anonymous identity created at first use.
- **Credentials live at `~/.config/hi/credentials.json`** with file mode 600 (user read/write only). The directory is mode 700.
- **Tokens are audience-bound** to `hirey-hi` (the Hi platform's canonical audience). They cannot authenticate against any non-Hi surface.
- **All traffic is HTTPS** to `https://hi.hirey.ai/v1/*`. The Hi MCP server (used by Codex / OpenClaw) lives at a different path and is not used by this plugin.

## Layout (for plugin maintainers)

```
.claude-plugin/
  marketplace.json                    # what Claude Code reads when you `marketplace add`
plugins/
  hirey-hi/
    .claude-plugin/plugin.json        # plugin manifest
    skills/
      hi-onboard/SKILL.md             # bootstrap (idempotent)
      hi-use/SKILL.md                 # listings / matching / pairings / meetings
      hi-events/SKILL.md              # inbound event drain
    reference/
      api.md                          # full REST API + credentials lifecycle reference
    README.md                         # plugin-level docs
```

This repo is **automatically mirrored** from the `host-plugins-claude/` directory inside Hirey's internal hi-platform repo. Source-of-truth changes happen there; this repo is the published surface.

## Releases

Tags follow `<plugin-name>--vMAJOR.MINOR.PATCH` (the convention emitted by `claude plugin tag`). The latest release is **`hirey-hi--v0.2.0`** — pure-skill plugin, no MCP.

For the unpinned (default-branch) install:

```text
/plugin marketplace add hirey-ai/hirey-claude-plugin
```

To pin to an exact tag, use the git URL with `#ref`:

```text
/plugin marketplace add https://github.com/hirey-ai/hirey-claude-plugin.git#hirey-hi--v0.2.0
```

The plugin's `version` is independent from `hi-platform` versions — backend changes do not require a plugin release because the capability catalog is fetched dynamically.

## Sibling distributions

| Host | Marketplace | Mechanism | Repo |
|---|---|---|---|
| Codex | `codex plugin marketplace add hirey-ai/hirey-codex-plugin` | Remote MCP + OAuth (DCR + PKCE) | [hirey-codex-plugin](https://github.com/hirey-ai/hirey-codex-plugin) |
| Claude Code | `/plugin marketplace add hirey-ai/hirey-claude-plugin` | **Pure skill + REST + client_credentials** | this repo |
| OpenClaw / npm | `clawhub:hirey` or `npm i -g @hirey/hi-mcp-server` | Local stdio MCP + client_credentials | hirey/openclaw-plugin |

All three are sibling adapters over the same Hi REST API. Tool names, schemas, and semantics are identical.

## Support

- Plugin issues / requests → [open an issue on this repo](https://github.com/hirey-ai/hirey-claude-plugin/issues)
- Hi platform questions → [hi.hirey.ai](https://hi.hirey.ai)
- Security disclosures → security@hirey.com

## License

MIT — see [LICENSE](./LICENSE). The MIT license covers the plugin shell (manifest, skill markdown, docs). The remote Hi platform this plugin connects to (`https://hi.hirey.ai`) is operated by Hirey under separate Terms of Service.

---

## SOURCE: hirey-ai/hirey-codex-plugin (https://github.com/hirey-ai/hirey-codex-plugin)
## PAGE: https://doc.hirey.ai/codex/
## RAW: https://doc.hirey.ai/codex.md

# Hirey for Codex

The official Codex marketplace for [Hirey Hi](https://hi.hirey.ai) — a people-to-people platform for jobs and candidates, landlords and tenants, friends, dates or marriage partners, lawyers, founders, investors, cofounders, and any other human leads.

## Install

```bash
# 1) Register this marketplace with Codex (one time)
codex plugin marketplace add hirey-ai/hirey-codex-plugin

# 2) Start a Codex session, then install and enable the plugin
codex
# > /plugins → Hirey marketplace → hirey-hi → Install plugin, then enable it

# 3) Fully restart Codex — required for the MCP server to actually load
#    (Codex only spawns MCP servers at session start; plugins enabled
#    mid-session do NOT load until you relaunch)
/quit    # or Ctrl-C, then re-run:
codex

# 4) Authorize this Codex install against Hi (zero touch — no Hi account)
codex mcp login hi
```

Step 4 takes about a second: Codex pops a browser tab that instantly redirects back to a local callback and closes itself. No Hi account, no consent screen, no email/phone — Hi provisions a fresh anonymous agent identity for this Codex install in the background.

Once logged in, ask Codex anything people-shaped — *"find me 10 backend engineers in Tokyo with JLPT N2+"*, *"reach out to the top three from yesterday"*, *"schedule a 30-min Zoom with Alex next Wednesday"* — and it uses Hi's tools directly.

> **Why the restart?** Codex initializes MCP servers exactly once at session start (`McpConnectionManager::new`) and never re-scans — confirmed upstream in [openai/codex#4955](https://github.com/openai/codex/issues/4955) and [openai/codex#7767](https://github.com/openai/codex/issues/7767), both closed as "not planned." Skip the restart and every `hi_*` tool call returns "no such tool." If after the restart `/plugins` still shows a `Set up in MCP settings` warning next to `hirey-hi`, ignore it — known UI bug ([openai/codex#17360](https://github.com/openai/codex/issues/17360)); verify with `codex mcp list`.

## What you get

Codex picks up three skills + a dynamic tool catalog the moment the plugin is enabled:

- **`hi-onboard`** — first-time setup; surfaces the `codex mcp login hi` flow if you haven't run it yet
- **`hi-use`** — workflows for listings, matching feeds, pairings, and meetings
- **`hi-events`** — durable pull for inbound replies, meeting confirmations, and match updates

Business tools (`agent_listings`, `matching_sessions`, `pairings`, `thread_meetings`, `calendar`, `listing_taxonomy`, …) are loaded live from Hi's public capability catalog, so new tools become available without re-installing the plugin.

## Architecture

```
Codex CLI ──(HTTPS + OAuth bearer)──▶ https://hi.hirey.ai/mcp
                                       │
                                       └─ multi-tenant hi-mcp-server
                                          ├─ verifies token against hi-auth JWKS
                                          ├─ resolves Hi installation by OAuth subject
                                          └─ proxies tool calls to hi-platform
```

- **Remote MCP** ([Streamable HTTP](https://modelcontextprotocol.io/specification/2025-11-25/basic/transports#streamable-http)). No local Node, no daemon, no state dir on your machine.
- **OAuth 2.1** with [PKCE](https://www.rfc-editor.org/rfc/rfc7636) + [Dynamic Client Registration](https://www.rfc-editor.org/rfc/rfc7591) + [Protected Resource Metadata (RFC 9728)](https://www.rfc-editor.org/rfc/rfc9728) + [Resource Indicators (RFC 8707)](https://www.rfc-editor.org/rfc/rfc8707). Bearer lives in your OS keychain via Codex.
- **Anonymous identity model** — same as Hi's OpenClaw plugin. No Hi user account is created or required for Codex to use the platform.

## Privacy & scope

The OAuth flow requests three scopes:

| Scope | Allows |
|---|---|
| `hi.read` | Read your Hi listings, matches, pairings, meetings, taxonomy |
| `hi.write` | Create/update listings, send pairing messages, propose meetings |
| `hi.events` | Pull inbound events (replies, confirmations) for your installation |

Tokens are audience-bound to `https://hi.hirey.ai/mcp` (RFC 8707) so they cannot be replayed against any other Hi surface.

## Layout (for plugin maintainers)

```
.agents/
  plugins/
    marketplace.json                 # what Codex reads when you `marketplace add`
plugins/
  hirey-hi/
    .codex-plugin/plugin.json        # plugin manifest
    .mcp.json                        # remote MCP endpoint + scopes
    skills/                          # SKILL.md files Codex auto-loads
    README.md                        # plugin-level docs (in-depth OAuth flow, etc.)
```

This repo is **automatically mirrored** from the `host-plugins/` directory inside Hirey's internal hi-platform repo. Source-of-truth changes happen there; this repo is the published surface. See the in-repo [plugin README](./plugins/hirey-hi/README.md) for the full OAuth walk-through and local-dev instructions.

## Releases

Tags on this repo follow `vMAJOR.MINOR.PATCH`. Pin a known-good version:

```bash
codex plugin marketplace add hirey-ai/hirey-codex-plugin --ref v0.1.3
```

The plugin manifest version is independent from `hi-mcp-server` / `hi-platform` versions on Hirey's side — backend changes do not require a plugin release because the tool catalog is fetched dynamically.

## Support

- Plugin issues / requests → [open an issue on this repo](https://github.com/hirey-ai/hirey-codex-plugin/issues)
- Hi platform questions → [hi.hirey.ai](https://hi.hirey.ai)
- Security disclosures → security@hirey.com

## License

UNLICENSED (proprietary). Free to install and use against Hi's hosted service; do not fork or redistribute the plugin manifest under your own marketplace name.

---

## SOURCE: hirey-ai/hirey-hermes-plugin (https://github.com/hirey-ai/hirey-hermes-plugin)
## PAGE: https://doc.hirey.ai/hermes/
## RAW: https://doc.hirey.ai/hermes.md

# hirey-hi for Hermes Agent

Native Hermes plugin for [Hirey Hi](https://hi.hirey.ai) — a people-to-people platform for hiring, dating, housing, founders, cofounders, investors, lawyers, and any other human-lead goal.

Loads Hi's capability tools directly into Hermes (`hirey_hi` toolset), wires three skills (`hi-onboard`, `hi-use`, `hi-events`) 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)

```bash
curl -fsSL https://raw.githubusercontent.com/hirey-ai/hirey-hermes-plugin/main/install.sh | bash
```

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

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

```bash
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](https://github.com/NousResearch/hermes-agent/issues/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}/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).
- **Anonymous client_credentials** — `POST /v1/agents/register` mints a per-install `client_id` + `client_secret` pair. No browser, no PKCE, no Hi account.
- **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

### Three control tools (always registered)

| Tool | What it does |
|---|---|
| `hi_agent_status` | Check credentials, token freshness, capability count |
| `hi_agent_install` | Bootstrap anonymous identity (idempotent) |
| `hi_pull_events` | Long-poll Hi for inbound events; supports `ack_event_ids` |

### Capability tools (one per Hi capability)

`owners`, `agent_listings`, `matching_sessions`, `pairings`, `thread_meetings`, `listing_taxonomy`, `agent_credits`, `conversations`, `social_org`, `social_permissions`, `social_relationships`, `faq_get`, `faq_search`, `content_get`, `content_render`, … — names + schemas come from Hi's live catalog at install time.

### One slash command

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

### Three skills

Live in `~/.hermes/skills/communication/hi-{onboard,use,events}/` 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.

| Host | Marketplace | Mechanism | Repo |
|---|---|---|---|
| Claude Code | `/plugin marketplace add hirey-ai/hirey-claude-plugin` | Pure SKILL + curl REST + client_credentials | [hirey-claude-plugin](https://github.com/hirey-ai/hirey-claude-plugin) |
| Codex | `codex plugin marketplace add hirey-ai/hirey-codex-plugin` | SKILL + remote MCP + OAuth (PKCE + DCR) | [hirey-codex-plugin](https://github.com/hirey-ai/hirey-codex-plugin) |
| OpenClaw | `openclaw plugins install clawhub:hirey` | Native TS plugin (in-process) | [hi-openclaw-plugin](https://github.com/hirey-ai/hi-openclaw-plugin) |
| **Hermes** | `hermes plugins install hirey-ai/hirey-hermes-plugin` | **Native Python plugin (in-process)** | **this repo** |

## Uninstall

```bash
hermes plugins remove hirey-hi
rm -rf ~/.hermes/skills/communication/hi-{onboard,use,events}
rm -rf ~/.config/hi   # only if not also using the Claude Code plugin
```

## Support

- Plugin issues / requests → [open an issue on this repo](https://github.com/hirey-ai/hirey-hermes-plugin/issues)
- Hi platform questions → [hi.hirey.ai](https://hi.hirey.ai)
- Security disclosures → security@hirey.com

## License

MIT — see [LICENSE](./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.

---

## SOURCE: hirey-ai/hi-openclaw-plugin (https://github.com/hirey-ai/hi-openclaw-plugin)
## PAGE: https://doc.hirey.ai/openclaw/
## RAW: https://doc.hirey.ai/openclaw.md

# hi-openclaw-plugin

Hirey Hi as a **native OpenClaw plugin**. Registers Hi's tools, agent-events claim service, and webhook ingress directly inside the OpenClaw gateway process — zero independent daemons, no `mcp.servers.hi` indirection, and no per-run frozen tool inventory boundary.

This is the OpenClaw 5.2+ first-class path, published to ClawHub as **`clawhub:hirey`** (ClawPack code-plugin) and to npm as **`hirey`**. OpenClaw 4.23 ~ 5.1 hosts cannot load this ClawPack format and must install the prod bundle plugin **`clawhub:hirey-compatible`** instead (zip + skill + scripts wrapping `@hirey-ai/mcp-server` + `@hirey-ai/agent-receiver`). All OpenClaw 4.23+ hosts can install `clawhub:hirey-compatible` as a universal fallback.

## Why this exists

The bundle + spawn model needs:

- one stdio child process for the MCP server (`@hirey-ai/mcp-server`)
- one long-running daemon (`@hirey-ai/agent-receiver`) for cloud-to-host event delivery
- a host installer mjs that uses `child_process` to run `npm install` + `openclaw config set` (which trips OpenClaw's pre-4.23 install scanner)
- a two-message install flow because the LLM run that wrote `mcp.servers.hi` cannot call the just-installed tools in the same outer run (per-run frozen tool inventory)
- `hooks.token` / `hooks.path` / `hooks.allowedSessionKeyPrefixes` / `/hooks/agent` plumbing on the OpenClaw side

This native plugin replaces all of the above with three OpenClaw plugin SDK calls running inside the gateway process:

- `api.registerTool(...)` for every Hi tool — exposed to the LLM directly, no MCP layer
- `api.registerService(...)` for the agent-events claim loop — gateway owns the lifecycle, no orphan daemon
- `api.registerHttpRoute(...)` for the webhook ingress — uses gateway's HTTP server, no separate hooks token

## Distribution paths

| Path | Audience |
|---|---|
| `clawhub:hirey` (this package, ClawPack code-plugin) | OpenClaw **5.2+**. Best UX, in-process, no boundary friction. |
| `clawhub:hirey-compatible` (prod bundle plugin from `hi-platform`, zip + skills + scripts) | **All OpenClaw 4.23+ hosts**. Required for 4.23 ~ 5.1 (those hosts cannot load ClawPack); optional fallback for 5.2+ if the ClawPack install path has any issue. Wraps `@hirey-ai/mcp-server` + `@hirey-ai/agent-receiver`. |
| `@hirey-ai/mcp-server` + `@hirey-ai/agent-receiver` (npm, raw) | Claude Desktop, Cursor, VS Code MCP, any other MCP host. Stable cross-host transport. Independent of OpenClaw. |

Business logic (`@hirey-ai/agent-sdk`, `@hirey-ai/agent-contracts`) is fully shared; only the wiring layer differs.

## Supported OpenClaw versions

| OpenClaw version | `clawhub:hirey` (ClawPack) | `clawhub:hirey-compatible` (bundle) | Notes |
|---|---|---|---|
| **2026.5.2+** | ✅ recommended (in-process) | ✅ works but skips native plugin benefits | ClawPack first-class path |
| **2026.4.23 ~ 2026.5.1** | ❌ runtime expects date-format `pluginApi`, rejects semantic `1.0` | ✅ recommended | bundle is the only path |
| **2026.4.14 ~ 2026.4.22** | ❌ same as above | ❌ install scanner flags `child_process` in installer mjs | unsupported; must upgrade OpenClaw |
| **< 2026.4.14** | ❌ | ❌ | unsupported |

## Install

### Pre-flight: avoid the approval loop (one-time, ~5 seconds, recommended)

On a default OpenClaw host, `tools.exec` runs in `security=allowlist` + `ask=off` and the natural-language install path stalls in an approval loop: each `/approve <token>` retry rotates the token because the gateway's followup dispatch can't reuse the approved session token (upstream tracked at [openclaw/openclaw#58662](https://github.com/openclaw/openclaw/issues/58662) and [#27831](https://github.com/openclaw/openclaw/issues/27831)). Before chatting with OpenClaw, paste this in your shell once:

```bash
openclaw approvals set --stdin << 'JSON'
{
  "version": 1,
  "agents": {
    "main": {
      "security": "allowlist",
      "ask": "on-miss",
      "allowlist": [
        {
          "pattern": "**/openclaw",
          "argPattern": "^plugins\\s+install\\s+clawhub:hirey(\\b|$)",
          "source": "manual"
        }
      ]
    }
  }
}
JSON
```

The change is live — no `openclaw gateway restart` needed. The allowlist is intentionally narrow: it only matches `openclaw plugins install clawhub:hirey*` (covers `clawhub:hirey`, `clawhub:hirey --force`, and the bundle name `clawhub:hirey-compatible`); it does NOT broaden any other openclaw subcommand.

With pre-flight set, the install prompt below finishes in **2 chat turns, 0 `/approve` prompts** (verified end-to-end on OpenClaw 2026.5.6). Without pre-flight, expect 4–6 turns with several token-paste round-trips.

### Natural-language install (after pre-flight)

OpenClaw is a personal agent driven by natural language; the LLM picks which command to run. The recommended user-facing prompt that works across versions:

```
Install Hirey AI on this OpenClaw host. First check `openclaw --version`:
- If 2026.5.2 or higher, run `openclaw plugins install clawhub:hirey`.
- Otherwise (OpenClaw 2026.4.23 ~ 2026.5.1), run `openclaw plugins install clawhub:hirey-compatible --dangerously-force-unsafe-install`.
The `--dangerously-force-unsafe-install` flag is required only for the bundle path: it is OpenClaw's own break-glass override that lets community bundles ship a setup-time `child_process` helper for `npm install` + `openclaw config set`. The ClawPack path is in-process and does not need the flag.
After install, call hi_agent_install (don't fabricate an agent id). Report the real agent_id and hooks_ready status.
```

Direct CLI for OpenClaw 5.2+ users:

```bash
openclaw plugins install clawhub:hirey
openclaw gateway restart
```

For OpenClaw 4.23 ~ 5.1 users (bundle path), or any 5.2+ user who wants the bundle as a universal fallback:

```bash
openclaw plugins install clawhub:hirey-compatible --dangerously-force-unsafe-install
openclaw gateway restart
```

The `--dangerously-force-unsafe-install` flag is required because OpenClaw 4.14+ install scanner blocks community bundles that ship a `child_process` import; our `openclaw-host-installer.mjs` legitimately uses `child_process.execFile` to spawn `npm install` and `openclaw config set` during setup. This is the OpenClaw-provided override flag (docs/cli/plugins.md), not a bypass of security controls.

After restart, ask OpenClaw "Hi 健康吗?" or "post a Hi listing for me" — the LLM will see the registered Hi tools and run them directly.

## Development

```bash
npm install
npm run build
npm pack    # emits hirey-<version>.tgz
```

Use `openclaw plugins install -l <local-dir>` for local link-mode testing (only on OpenClaw 5.2+).

## License

UNLICENSED (private; published under unscoped `hirey` on the public npm registry but the source is not open source).