Languages: English | 日本語 | 简体中文
Experimental Codex plugin that bridges Codex App tasks to the local Hermes CLI, then lets Codex review the returned answer before continuing.
The goal is simple: install this repo as a Codex plugin, run a Hermes task from any Codex workspace, and see a Hermes reply come back.
The demo shows the difference between plain hermes and Codex Hermes: plain
Hermes returns a model answer directly, while Codex Hermes treats that answer as
untrusted data, checks it against the local repository, and returns a reviewed
final answer.
- v0.1.2 - Public metadata cleanup for installable-first distribution
- v0.1.1 - Initial verified Codex App <-> Hermes CLI bridge
- No binary or bundle is attached yet; use the repository source directly.
- Codex App
hermesCLI installed and available onPATH- This repository cloned locally
- Make sure Hermes works from a terminal first.
hermes --help
If that command fails, fix Hermes before continuing. This plugin cannot talk to Hermes without the CLI.
- Install the plugin into your Codex plugin directory.
$pluginRoot = "$env:USERPROFILE\.codex\plugins\codex-hermes"
Remove-Item -Recurse -Force $pluginRoot -ErrorAction SilentlyContinue
New-Item -ItemType Directory -Force -Path $pluginRoot | Out-Null
Copy-Item -Recurse -Force .codex-plugin, skills, commands, scripts, assets, README.md, README.ja.md, README.zh-CN.md, LICENSE $pluginRoot-
Restart Codex App, or open a new thread, so the plugin skill list is refreshed.
-
Run the validator from this repository.
python scripts/validate-plugin.py
- Optional, but recommended for development in this repository:
git config core.hooksPath .githooks
When this repository is the active Codex workspace, Codex can also discover the
repo-local skill at .agents/skills/hermes/SKILL.md. That is useful while
developing the plugin, but it is not enough for other folders.
For use from other workspaces, install the plugin so Codex can load:
%USERPROFILE%\.codex\plugins\codex-hermes\skills\hermes\SKILL.md
- In Codex, invoke the Hermes skill with a short task from any workspace.
$hermes say hello
- Wait for the run to finish.
- Confirm the output contains:
MODEL=...SESSION_ID=...RESPONSE_BEGIN- a Hermes reply after
RESPONSE_BEGIN
If you see Hermes CLI was not found on PATH, the CLI is not installed or the shell cannot see it yet.
If you see no SESSION_ID, Hermes did not return a session marker, but the reply can still be valid.

