Skip to content

feat: add Hermes Agent harness support (dist/hermes/)#1892

Open
pandaliu00 wants to merge 1 commit into
obra:devfrom
pandaliu00:hermes-harness-integration
Open

feat: add Hermes Agent harness support (dist/hermes/)#1892
pandaliu00 wants to merge 1 commit into
obra:devfrom
pandaliu00:hermes-harness-integration

Conversation

@pandaliu00

Copy link
Copy Markdown

Who is submitting this PR?

Field Value
Your model + version DeepSeek V4 Flash via Hermes Agent
Harness + version Hermes Agent desktop app (TUI)
All plugins installed evolution-fusion v1.8.0, hermes-superpowers-harness v1.0.0
Human partner who reviewed this diff @liujie — reviewed the complete diff before submission

What problem are you trying to solve?

Hermes Agent (NousResearch/hermes-agent) is a mature open-source agent framework with its own native skill system, but currently lacks Superpowers integration. Users who prefer Hermes as their main harness must either manually port skills, copy instructions into SOUL.md, or delegate through another harness — all fragile approaches that desync from upstream.

Two existing feature requests: #1581, #1859

What does this PR change?

Adds dist/hermes/ with 13 Hermes-compatible SKILL.md exports — one per Superpowers core skill — with Hermes-native YAML frontmatter and tool name mappings (skill_view→Skill, todo→TodoWrite, delegate_task→Subagent). Each skill is installable via hermes skills install <url> --name superpowers:<name>.

Is this change appropriate for the core library?

Yes — Hermes is a general-purpose coding-agent harness (same category as Claude Code, Codex, Cursor, Pi, etc.). The dist/hermes/ directory follows the same pattern as multi-harness support already in the repo (.opencode/, .codex-plugin/, .cursor-plugin/, .pi/extensions/, .kimi-plugin/, etc.).

What alternatives did you consider?

  1. Option A (chosen): Standalone dist/hermes/ export directory — follows existing multi-harness pattern
  2. Option B: Hermes plugin adapter (TypeScript/JS bridging layer) — rejected: Hermes has no plugin system at the runtime level
  3. Option C: Dual-format authoring — rejected: adds maintenance burden upstream; dist/hermes/ can be regenerated from source

Does this PR contain multiple unrelated changes?

No — all changes are within dist/hermes/.

Existing PRs

  • I have reviewed all open AND closed PRs for duplicates or prior art
  • Related PRs: none found for Hermes support specifically

Adds 13 Hermes-compatible skill exports under dist/hermes/ with
tool name mapping (skill_view->Skill, todo->TodoWrite, etc.).

Each skill installable via: hermes skills install <url> --name superpowers:<name>

Closes obra#1581, obra#1859
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant