Is your feature request related to a problem? Please describe.
cq currently installs into 7 hosts (claude, codex, copilot, cursor,
devin-desktop, opencode, pi). Hermes Agent (Nous Research) has become one
of the most widely used open-source harnesses, but there's no
--target hermes, so Hermes users can't join the commons without manual
wiring.
Describe the solution you'd like
Add a TargetHermes adapter in cli/internal/install/, mirroring
opencode.go:
- write the shared SKILL.md into Hermes's skills directory
- add the cq MCP server entry to
~/.hermes/config.yaml under
mcp_servers (Hermes auto-discovers and registers MCP tools from
config, so no host-side code is needed)
- install the
reflect / status command files
- upsert the instruction block into the context file Hermes reads
Scope looks comparable to the existing adapters (~150-200 LOC + tests).
The registry comment says adding an entry extends ValidTarget /
AllowedTargets / SelectHosts, so this should be self-contained.
One design question: cq's auto-query-on-error hooks are Claude-Code
specific. Hermes handles hooks via its Python plugin system, so parity
there would live in a separate Hermes plugin rather than in this repo.
Fine to treat that as out of scope here?
Describe alternatives you've considered
- Manual wiring: users hand-edit
~/.hermes/config.yaml and copy
SKILL.md themselves. Works, but no dry-run, no uninstall, no parity
with the one-command install other hosts get.
- A Hermes-side plugin wrapping the cq CLI without upstream support.
Possible, but discovery suffers and install UX fragments across hosts.
Additional Context
Hermes MCP auto-discovery: https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp
Happy to build and PR this myself if maintainers are open to it.
Self-Checklist
Is your feature request related to a problem? Please describe.
cq currently installs into 7 hosts (claude, codex, copilot, cursor,
devin-desktop, opencode, pi). Hermes Agent (Nous Research) has become one
of the most widely used open-source harnesses, but there's no
--target hermes, so Hermes users can't join the commons without manualwiring.
Describe the solution you'd like
Add a
TargetHermesadapter incli/internal/install/, mirroringopencode.go:~/.hermes/config.yamlundermcp_servers(Hermes auto-discovers and registers MCP tools fromconfig, so no host-side code is needed)
reflect/statuscommand filesScope looks comparable to the existing adapters (~150-200 LOC + tests).
The registry comment says adding an entry extends ValidTarget /
AllowedTargets / SelectHosts, so this should be self-contained.
One design question: cq's auto-query-on-error hooks are Claude-Code
specific. Hermes handles hooks via its Python plugin system, so parity
there would live in a separate Hermes plugin rather than in this repo.
Fine to treat that as out of scope here?
Describe alternatives you've considered
~/.hermes/config.yamland copySKILL.md themselves. Works, but no dry-run, no uninstall, no parity
with the one-command install other hosts get.
Possible, but discovery suffers and install UX fragments across hosts.
Additional Context
Hermes MCP auto-discovery: https://hermes-agent.nousresearch.com/docs/user-guide/features/mcp
Happy to build and PR this myself if maintainers are open to it.
Self-Checklist