feat(agents): PreToolUse nudges for the remaining harnesses, and Hermes skill support

Open
#116 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
Over a week
Newbie friendliness
22/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go
Domain
cli, devtools

Research direction

Start with the existing opt-in nudge in internal/nudge, which covers Claude Code and Codex, and with internal/agents/hermes.go, which currently writes only MCP config. Each harness first needs its hook mechanism verified against primary docs or a live session, so the first step is a verification note per item, not code. Done means each harness either has a capability-table-driven nudge with a recorded live session, or the item is closed as not possible with the evidence attached.

Written by the indexing model from the issue text.

Description

area:agents feature priority:low spec-needed
What problem does this solve?

The opt-in PreToolUse nudge exists only for Claude Code and Codex. Hermes receives an MCP entry only: no skill and no hooks.

What should it do?

Each item first needs the harness's mechanism verified against primary docs or a live session:

  • NUDGE-07 Cursor (.cursor/hooks.json; the non-blocking output shape is unverified)
  • NUDGE-08 Kiro (.kiro/hooks/<id>.json, {"type":"agent"})
  • NUDGE-09 Gemini CLI (.gemini/hooks/)
  • NUDGE-10 opencode, Antigravity (mechanisms [ASSUMED])
  • AGENT-12 Hermes skill and hooks (no public docs found)
  • Codex SessionStart nudge; Codex skill metadata (agents/openai.yaml) and plugin packaging
Which surface does this affect?

Other (agent install)

Is this covered by an existing command or tool today?

Partly. codegraph install --pretool-nudge covers Claude Code and Codex (internal/nudge). internal/agents/hermes.go writes MCP config only.

Acceptance criteria
  • Each harness either gets a nudge driven by the capability table, with a live-session record, or the item is closed as not possible, with the evidence.

Source (GSD planning files, archived at d384473e): .planning/milestones/v0.14.0-REQUIREMENTS.md (v2: NUDGE-07…10, AGENT-12); .planning/ROADMAP.md (Later); .planning/milestones/v0.14.0-phases/07-codex-parity/07-CONTEXT.md (Deferred Ideas)


🤖 Generated with Claude Code

https://claude.ai/code/session_01UNqdnC3q6U362BvyfxuKCF

Dominant language
Go
Stars
0
Forks
0
Avg merge
5h 16m
Merged PRs (30d)
107

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seanb4t/codegraph-go

All issues in seanb4t/codegraph-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.