All plugins

wow

Chat with a Hermes agent from inside World of Warcraft: Forever. The plugin registers a kind: platform gateway adapter that serves a local HTTP endpoint (/v1/wow/message, /v1/wow/outbox, /v1/wow/health) authenticated with a bearer token; one character (Name-Realm) is one Hermes DM session. A companion bridge runs on a Windows 11 PC next to the game client: it captures a 1600x400 pixel strip from the game window with the Windows Graphics Capture API (mss/GDI fallback), decodes chat, POSTs lines to the adapter and long-polls the outbox. It also writes reply/state files into the WoW AddOns tree and reads SavedVariables for reload mode, and plays silent doorbell WAVs. The adapter binds 127.0.0.1 by default and can be bound to a LAN address explicitly; the bridge then makes outbound HTTP requests to that configured Hermes host. Adds five WoW-only tools (wow_addon_search, wow_addon_guide, wow_addon_install, wow_addon_uninstall, wow_quest_help), three per-character toolsets selected with /mode (standard, wow, full; full needs an in-game confirmation and expires after 60 minutes), and a bundled wow-player-guide skill. Disclosure - the plugin opens a local HTTP listener guarded by a shared bearer secret (WOW_BRIDGE_TOKEN, auto-generated in memory when unset, so the bridge cannot pair until it is set); it makes CurseForge API calls (api.curseforge.com) with the player's own CurseForge Core API key, stored as a profile-scoped Hermes secret (WOW_CURSEFORGE_API_KEY in the selected profile) with no plugin-managed credential file; addon installs and uninstalls are queued to the bridge, which writes or moves files under the WoW AddOns directory only after the player confirms in game and keeps a removal backup instead of deleting permanently; a desktop setup page creates or updates a dedicated Hermes profile (wow), writes its .env, config.yaml, SOUL.md and a profile skill, and can hot-serve that profile through a running gateway multiplexer. The bridge is a separate long-running background process (screen pixels plus files only); the plugin does not read the game process or its memory, does not inject input, and does not automate gameplay. Chat text and tool results are sent to the model provider configured for the WoW Hermes profile (cloud or local), with that provider's data-handling terms and the usual token cost. Requires Hermes >=0.22.7, Windows 11 for the bridge, WoW: Forever (Interface 16001), and uv/Python downloaded for the bridge; a CurseForge key is needed only for one-click addon installs (without one the addon tools return a guided CurseForge link). Disclosure — the plugin opens a local HTTP listener (127.0.0.1 by default, plain HTTP if bound to a LAN address) guarded only by a shared bearer token (WOW_BRIDGE_TOKEN); whoever holds that token can chat as any character and, after the in-game /mode full confirm step, use terminal, file and code tools on the Hermes host for 60 minutes. It calls the CurseForge API (api.curseforge.com) with the player's own CurseForge key, stored as a Hermes secret in the selected profile. The Desktop setup page creates or updates a dedicated Hermes profile: it copies this plugin into that profile, writes the profile's .env, config.yaml (including turning off tool deferral for that profile), SOUL.md and a profile skill, and can hot-serve it through a running gateway. A separate long-running Windows bridge reads a strip of the game window's pixels, writes reply and state files and installs or backs up addons under the WoW AddOns folder only after an in-game confirmation, opens links the agent sends in the default browser, and downloads a checksum-pinned uv release and Python on setup; it never reads game memory, injects input or automates play. Chat text and tool results go to the model provider configured for the WoW profile.

c-pompaPlatformv0.2.1Updated 7 days ago

About

Chat with a Hermes agent from inside World of Warcraft: Forever. The plugin registers a kind: platform gateway adapter that serves a local HTTP endpoint (/v1/wow/message, /v1/wow/outbox, /v1/wow/health) authenticated with a bearer token; one character (Name-Realm) is one Hermes DM session. A companion bridge runs on a Windows 11 PC next to the game client: it captures a 1600x400 pixel strip from the game window with the Windows Graphics Capture API (mss/GDI fallback), decodes chat, POSTs lines to the adapter and long-polls the outbox. It also writes reply/state files into the WoW AddOns tree and reads SavedVariables for reload mode, and plays silent doorbell WAVs. The adapter binds 127.0.0.1 by default and can be bound to a LAN address explicitly; the bridge then makes outbound HTTP requests to that configured Hermes host. Adds five WoW-only tools (wow_addon_search, wow_addon_guide, wow_addon_install, wow_addon_uninstall, wow_quest_help), three per-character toolsets selected with /mode (standard, wow, full; full needs an in-game confirmation and expires after 60 minutes), and a bundled wow-player-guide skill. Disclosure - the plugin opens a local HTTP listener guarded by a shared bearer secret (WOW_BRIDGE_TOKEN, auto-generated in memory when unset, so the bridge cannot pair until it is set); it makes CurseForge API calls (api.curseforge.com) with the player's own CurseForge Core API key, stored as a profile-scoped Hermes secret (WOW_CURSEFORGE_API_KEY in the selected profile) with no plugin-managed credential file; addon installs and uninstalls are queued to the bridge, which writes or moves files under the WoW AddOns directory only after the player confirms in game and keeps a removal backup instead of deleting permanently; a desktop setup page creates or updates a dedicated Hermes profile (wow), writes its .env, config.yaml, SOUL.md and a profile skill, and can hot-serve that profile through a running gateway multiplexer. The bridge is a separate long-running background process (screen pixels plus files only); the plugin does not read the game process or its memory, does not inject input, and does not automate gameplay. Chat text and tool results are sent to the model provider configured for the WoW Hermes profile (cloud or local), with that provider's data-handling terms and the usual token cost. Requires Hermes >=0.22.7, Windows 11 for the bridge, WoW: Forever (Interface 16001), and uv/Python downloaded for the bridge; a CurseForge key is needed only for one-click addon installs (without one the addon tools return a guided CurseForge link). Disclosure — the plugin opens a local HTTP listener (127.0.0.1 by default, plain HTTP if bound to a LAN address) guarded only by a shared bearer token (WOW_BRIDGE_TOKEN); whoever holds that token can chat as any character and, after the in-game /mode full confirm step, use terminal, file and code tools on the Hermes host for 60 minutes. It calls the CurseForge API (api.curseforge.com) with the player's own CurseForge key, stored as a Hermes secret in the selected profile. The Desktop setup page creates or updates a dedicated Hermes profile: it copies this plugin into that profile, writes the profile's .env, config.yaml (including turning off tool deferral for that profile), SOUL.md and a profile skill, and can hot-serve it through a running gateway. A separate long-running Windows bridge reads a strip of the game window's pixels, writes reply and state files and installs or backs up addons under the WoW AddOns folder only after an in-game confirmation, opens links the agent sends in the default browser, and downloads a checksum-pinned uv release and Python on setup; it never reads game memory, injects input or automates play. Chat text and tool results go to the model provider configured for the WoW profile.

WoW Hermes

Talk to a Hermes agent from inside World of Warcraft: Forever.

WoW Hermes connects the game chat to a Hermes profile: a companion bridge next to
the game captures your chat lines and writes the agent's replies back into the
client through the addon. One character (Name-Realm) is one Hermes DM session.

This repository is the public release mirror of the project. It is a
sanitized snapshot of a private development tree, not that tree's history. The
Hermes catalog entry for this plugin has been prepared but is not listed yet;
until a maintainer merges it, install from this repository at a pinned commit as
shown below.

Quick links: v0.2.1 release ·
Hermes catalog PR #154256 ·
CurseForge listing/setup text · Issues

What you get

  • In-game chat platform for Hermes — kind: platform gateway adapter with a
    local HTTP endpoint (/v1/wow/message, /v1/wow/outbox, /v1/wow/health),
    bearer-token authentication, one DM session per character.
  • Three per-character toolsets selected with /mode:
    • standard — everyday Hermes tools, including quest and addon help.
    • wow — WoW-only tools plus web search; the small surface for play.
    • full — the whole Hermes toolset. Requires an in-game confirmation and
      lapses back to standard after 60 minutes.
  • Five WoW tools — wow_addon_search, wow_addon_guide,
    wow_addon_install, wow_addon_uninstall, wow_quest_help.
  • Bundled skill — wow-player-guide explains the modes, the in-game channel
    rules, and the addon workflows.
  • Desktop setup page — creates or updates a dedicated Hermes profile
    (wow), writes its environment and gateway config, renders SOUL.md and a
    profile skill, and shows adapter status and the one-time bridge token.
  • Addon management — search CurseForge for Forever-compatible addons,
    queue an install for the bridge, and uninstall by moving the folder to a
    removal backup. The player confirms every write in game.

In-game evidence

WoW Hermes minimap button in World of Warcraft: Forever

This is a real, unretouched pre-release capture of the WoW: Forever minimap area.
It shows the button's former placeholder icon; the shipped addon uses the Hermes
portrait icon. No finished-window screenshot is claimed from this older capture.

Requirements

PartRequirement
Hermes0.22.7 or newer (validated on 0.22.7). The catalog entry declares the same floor.
GameWorld of Warcraft: Forever, Interface 16001 (build 1.60.1.70862).
Bridge hostWindows 11, on the same PC as the game or on the same trusted network. uv downloads a private Python for the bridge.
NetworkThe Windows bridge must reach the Hermes listener over HTTP. Loopback when both run on the same PC; otherwise a LAN/VPN address you choose and firewall.
CurseForge (optional)Your own CurseForge Core API key, only for one-click addon installs. Without it the addon tools return a CurseForge deep link.

macOS and Linux can host Hermes and the plugin; the bridge itself is
Windows-only.

Install the Hermes plugin

Choose a commit in this repository and install its plugin/ subdirectory:

hermes plugins install c-pompa/wow-hermes/plugin --ref <40-hex-commit-sha> --enable

--ref takes the full 40-character SHA; branches and short SHAs are refused.
--enable selects the plugin in the active profile. After a catalog listing is
merged, hermes plugins install wow will install the reviewed pin instead.

To validate a checkout before installing:

hermes plugins validate plugin/

Set up the profile

Desktop (recommended). Open Hermes Desktop → Plugins → WoW Hermes.
Fill in your character (Name-Realm, e.g. Thrall-Area52), the profile to
create (wow by default), the starting mode, the listener host and port, and
optionally your CurseForge key. Save. The page creates the profile, writes its
.env and config.yaml, renders SOUL.md and a profile skill, and shows the
gateway URL and a one-time bridge token. If the profile's gateway is already
running under a multiplexer it may be hot-served; otherwise start it:

hermes -p wow gateway start

CLI. The same result without Desktop:

hermes profile create wow
hermes -p wow plugins enable wow

# Values live in this profile's .env (ask Hermes for the path):
hermes -p wow config env-path

Add to that file:

WOW_BRIDGE_TOKEN=<64 hex characters>
WOW_HOST=127.0.0.1
WOW_PORT=8791
WOW_ALLOWED_USERS=Thrall-Area52
WOW_HOME_CHANNEL=Thrall-Area52

WOW_HOST defaults to 127.0.0.1. Set it to the address the Windows bridge
will dial only if the bridge runs on another machine, and firewall the port to
that machine. Then enable the platform and start the gateway:

hermes -p wow config set gateway.platforms.wow.enabled true
hermes -p wow gateway start
curl -s http://127.0.0.1:8791/v1/wow/health

Expected: {"ok": true, "platform": "wow", "version": 1, ...}. A second
gateway cannot bind the same host:port; give each profile its own WOW_PORT.

WOW_BRIDGE_TOKEN is the shared secret the bridge sends as
Authorization: Bearer $WOW_BRIDGE_TOKEN. If it is unset the adapter generates
one in memory at startup and the bridge cannot know it, so set it explicitly.
The character name is asserted by the bridge, not by Blizzard; the token is the
only real authentication boundary.

Install the addon and the bridge

The bridge is a separate program. It captures a 1600×400 pixel strip from the
game window, decodes chat, forwards it to Hermes, and writes replies back into
the addon's slot files in the WoW AddOns tree. It also installs the addon and
its 256 load-on-demand slot addons.

Download wowhermes-bridge-v0.2.1.zip
from the v0.2.1 release and extract it. The
bundle includes the addon, locked bridge source and a PowerShell bootstrap. From
the extracted directory, run:

powershell -ExecutionPolicy Bypass -File .\bootstrap\install.ps1 `
    -WowDir "D:\Games\World of Warcraft\_forever_" `
    -GatewayUrl "http://192.0.2.10:8791"

The installer prompts for the one-time bridge token without echoing it. It finds
or downloads a checksum-verified uv, installs a private Python 3.12, creates a
locked virtual environment, installs the addon and slot addons, writes UTF-8
(no-BOM) configuration, and can register a per-user AtLogOn task. No Git,
preinstalled Python, SSH or administrator rights are required. Use -LocalGateway
instead of -GatewayUrl when Hermes runs on the same PC, -DryRun to preview,
and -NoAutostart for manual-only startup.

For a source-only alternative, uv run wowhermes-bridge install --wow <path>
and uv run wowhermes-bridge run work from bridge/ after uv sync --frozen.
The bridge must be running whenever you use chat in game. Verify release files
against SHA256SUMS before installing. Nothing in the plugin downloads or
replaces the bridge for you.

CurseForge addon availability is separate from this repository and from the
Hermes plugin: the addon tools query CurseForge, and an addon installs only when
its author allows third-party distribution and a Forever-compatible file
exists. Otherwise the tool returns a curseforge:// link for the player to
finish in the CurseForge app.

Security and privacy

Read this before installing. The full disclosure is also in the Hermes catalog
entry and the upstream pull request.

  • Local HTTP listener. The plugin opens WOW_HOST:WOW_PORT (loopback by
    default; optionally a LAN address) with plain HTTP. /v1/wow/message and
    /v1/wow/outbox require Authorization: Bearer $WOW_BRIDGE_TOKEN;
    /v1/wow/health needs no token on loopback. There is no TLS: use loopback, a
    trusted LAN/VPN, and a firewall rule that admits only the bridge host.
  • Bearer token. A wrong or missing token is 401. The token is never
    logged or returned by the status page. The character name is bridge-asserted
    (WOW_ALLOWED_USERS is attribution/convenience, not authentication).
  • Screen capture. The Windows bridge captures pixels from the game window
    with the Windows Graphics Capture API (mss/GDI fallback). It is restricted to
    the addon's chat strip; it does not read the game process or its memory,
    inject input, or automate gameplay.
  • Files outside the plugin's data directory. The bridge writes the addon
    and slot files under the WoW AddOns directory and reads SavedVariables for
    reload mode. Uninstall moves the addon folder into a removal backup; it does
    not permanently delete it.
  • Outbound network. The bridge makes HTTP requests to the Hermes host you
    configure. The plugin makes CurseForge API calls (api.curseforge.com) with
    your key. The key is stored as a profile-scoped Hermes secret
    (WOW_CURSEFORGE_API_KEY in the selected profile's secret store); there is no
    plugin-managed credential file. It is never returned to the model or logged.
    Upgrading from 0.2.0: the retired machine-wide curseforge.key file is
    neither read nor deleted; re-enter the key once in the selected profile's setup.
  • Model provider. Chat text and tool results from the game go to whichever
    model provider the wow Hermes profile is configured to use — cloud or
    local. That provider's data-handling terms apply, and token spend is yours.
    Tool results can include addon metadata and quest text.
  • Local tools and modes. standard and wow keep the surface small;
    full exposes the whole Hermes toolset (terminal, files, desktop control)
    until it expires. full requires an in-game confirmation.
  • Background process. The bridge is a long-running process next to the
    game; it must stay running for chat to work.
  • One-time setup writes. The desktop setup page creates/updates the wow
    profile, its .env, config.yaml, SOUL.md, and a profile skill, and may
    ask a running gateway multiplexer to serve the new profile. It does not
    restart the game or the Hermes gateway.
  • No telemetry. The plugin and bridge send nothing to the project author.
  • Compatibility. Requires Hermes 0.22.7+, Windows 11 for the bridge, and
    WoW: Forever (Interface 16001). Other clients/versions are not supported.

Known limitations

  • The game must run windowed or borderless-windowed; exclusive fullscreen
    exposes no capturable window.
  • One character = one Hermes session; the bridge reports the character name.
  • Addon installation depends on CurseForge metadata and the author's
    distribution setting, and is never silent: the player confirms in game.
  • The public repository is a release mirror; older development commits and
    internal notes are not published.
  • Cron/notification delivery to wow needs a live adapter in the same gateway
    process; the outbox is in memory.

License

MIT. See LICENSE. Third-party design credits and prior art are in
the bridge package's NOTICE file.

README from the reviewed commit bb4e047; it updates when the author re-pins.

More by c-pompa

3 plugins by c-pompa in the catalog.

c-pompaoperationsA Hermes Desktop page for running a fleet - topology, model traffic, handoffs, traces, merge requests and conformance checks in one place. Disclosure — reads hermes-metrics-dash's <hermes root>/metrics/metrics.db, the kanban board, every profile's config.yaml (plugin enable state, rolectl-mcp entries, default model) and plugin-data/gitlab-mr/device-aliases.json, all read-only; calls your GitLab (host and token from the plugin settings or GITLAB_HOST/GITLAB_TOKEN), the local model router (MODEL_ROUTER_URL, default 127.0.0.1:8867) and LM Studio (LMSTUDIO_URL, default 127.0.0.1:1234); runs git status/rev-parse/ls-files in the project folders it checks and shows matching lines (including any keys found) on the page. Page buttons create, assign, schedule, unblock and close kanban cards and start their workers at once, write <hermes root>/conformance/conformance.yaml, and "Propose a rule" pushes a branch and opens a merge request on the standard's GitLab project. A hook on every kanban dispatcher tick starts cards scheduled from the page; with alert_target set it posts new attention items through hermes send; with drift_action: automatic it files and starts a fix card for drift_profile for each drifting host with a verified report (at most daily) carrying the standard's remediate commands. With Activity summaries on (off by default), Activity sentences and each "Explain this session" click send log lines and trace details to the model set for the operations_summary auxiliary task. From the setup checklist's Connect GitLab step it can also adopt this profile's own login - its environment read through Hermes' secret scope, or the host the gitlab-mr plugin names - or take a host and token typed on the page; the host goes through the plugin-settings writer and the token through Hermes' .env credential route as OPERATIONS_GITLAB_TOKEN, and the token is never sent back to the page. No other credential store is read: a login that exists only in another profile's .env or in the glab CLI's config is typed in instead. Since 0.3.5 the plugin keeps its own metrics store: it tails <hermes root>/metrics/requests.jsonl and moa-refs.jsonl, guardrail lines in logs/agent.log, logs/model-router-requests.jsonl and clientgate/clientgate-usage.jsonl (all read-only, offset-tracked) plus its own host probes (CPU and memory via sysctl/vm_stat or PowerShell, LM Studio's lms ps, and every five minutes the local conformance.yaml's install-stamp, launchd/scheduled-task, loopback-port and key-name checks), and reads session titles and costs from <hermes root>/state.db and every profile's gateway_state.json (read-only), into <hermes root>/metrics/operations.db, which this plugin alone writes and prunes to the metrics_retention_days setting (30/60/90 days or forever, chosen on the page and written through Hermes' plugin-settings writer); hermes-metrics-dash's metrics.db is then only a read-only fallback until the own store holds data. It probes the local metrics dashboard's /api/about (METRICS_DASH_URL, default 127.0.0.1:8899, cached five minutes) to link to it rather than duplicate it, and every Hermes process that loads the plugin starts a daemon timer: when no kanban dispatcher tick has arrived for two minutes it runs the same sweep itself every 30 seconds (collection, alerts and, with drift_action: automatic, the fix cards), and the page says so; OPERATIONS_HEARTBEAT_TIMER=0 turns that timer off. Since 0.3.4 a failed model call is classified with the host app's own error classifier and shown with its cause and remedy commands; no new outbound call is made for that.CommunityDesktop app1c-pompas2docsSource 2 documentation and mod tooling for CS2 and Deadlock from a local index of Valve's own game data: convars, Hammer entities with their inputs and outputs, schema classes and enums, game events, the cs_script and Pulse APIs and Source2Wiki pages, plus the mod pipeline — scaffold addons, validate scripts and .cfg files, start map builds on a registered Windows host over SSH, deploy and verify hashes, and record evidence, test runs and job state. Needs uv and an index built with s2docs sync; every write-capable call asks for approval. Disclosure — runs its MCP server with uvx from the pinned git commit, resolving its PyPI dependencies on first start as of a fixed 2026-10-10 snapshot; nothing is sent to a third party, but SSH/scp go to any host registered through register_host, build_start runs agent-written shell commands on that host and its builds keep running after the session ends, deploy_push and job_attach copy local files the agent names, and it writes its own index and addon workspace; write tools ask for approval through the package's untrusted server trust.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section