feat: add Hermes Agent support

[cobaltstark-bot]

What

Adds Hermes Agent (NousResearch) as a supported tool.

Changes

• src/core/config.ts — new hermes entry in AI_TOOLS with skillsDir: '.hermes' and detection paths for HERMES.md, .hermes.md, and CONTEXT.md (Hermes's standard project-context files)
• docs/supported-tools.md — new row in the tool table, footnote explaining the external_dirs wiring required for project-local skills, hermes added to the --tools ID list

How Hermes loads skills

Hermes reads skills from ~/.hermes/skills/ by default. Project-local skill directories are supported via skills.external_dirs in ~/.hermes/config.yaml. The footnote in the docs covers the one-time config step needed to wire .hermes/skills/ into Hermes.

Hermes uses a skill-first invocation model (skill_view('openspec-propose')), so no command adapter is needed — skills alone are sufficient.

Notes

• Tested against Hermes Agent v0.13.x
• No command adapter added (Hermes resolves skills natively, no slash-command file format to target)
• CONTEXT.md detection path is the Hermes-conventional per-project context file

Summary by CodeRabbit

• New Features

  • Added Hermes Agent as a selectable tool with automatic project detection and configurable skills directory support

• Documentation

  • Updated supported tools documentation to include Hermes Agent with detailed setup information, including skills directory configuration and supported detection file patterns for project identification

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 91390a8b-94d6-463b-b32c-b32ff0a12f0c

📥 Commits

Reviewing files that changed from the base of the PR and between 8498042 and d79d3ef.

📒 Files selected for processing (2)

• docs/supported-tools.md
• src/core/config.ts

---

📝 Walkthrough

Walkthrough

This pull request adds Hermes Agent support to OpenSpec by registering it as an available tool option. The configuration exports a new Hermes Agent entry with a .hermes skills directory and three detection file paths (HERMES.md, .hermes.md, CONTEXT.md). The supported tools documentation is updated to list Hermes in the tool directory, explain its default and project-local skills configuration, and include it in the valid --tools option reference.

Changes

Hermes Agent Configuration and Documentation

Layer / File(s)	Summary
Hermes Agent registration and documentation src/core/config.ts, docs/supported-tools.md	Hermes Agent is added to AI_TOOLS with .hermes as the skills directory and HERMES.md/.hermes.md/CONTEXT.md as detection paths. Documentation includes a table entry describing the skills path, a footnote explaining default and project-local skills configuration via skills.external_dirs, and a reference in the valid --tools ID list.

Possibly related PRs

• Fission-AI/OpenSpec#1027: Modifies tool-ID documentation surfaces to reflect AI_TOOLS configuration, following the same pattern of docs-sync with the registry.
• Fission-AI/OpenSpec#941: Extends AI_TOOLS registry with a new tool option entry and aligns corresponding documentation in docs/supported-tools.md.

Suggested reviewers

• TabishB

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A speedy hop through tools we go,
Hermes joins the registry show,
Skills in .hermes directories bright,
Detection files guide the sight,
Documentation clear and tight! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: add Hermes Agent support' directly and clearly summarizes the main change—adding support for a new AI tool (Hermes Agent). It aligns with the core objective documented in the PR.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alfred-openspec]

Thanks for adding this. I checked the Hermes docs/source and the skill-directory piece looks real, but I think this needs one tightening pass before merge.

Blocking bits:

• Please drop CONTEXT.md from detectionPaths unless there is a current Hermes source/docs reference for it. Hermes' docs list .hermes.md / HERMES.md, then AGENTS.md, CLAUDE.md, .cursorrules, and .cursor/rules/*.mdc; CONTEXT.md is generic enough that this would false-detect Hermes in unrelated repos.
• Add a small available-tools test for Hermes detection, especially asserting a plain CONTEXT.md does not select hermes if we remove it.

Non-blocking but worth fixing while here: the docs row should probably show the user-facing Hermes skill invocation (/openspec-propose) or explain that skill_view('openspec-propose') is the internal/tool call path, since Hermes' user docs present installed skills as slash commands.