Hermes Agent applies configured approval timeouts to ACP edits

NousResearch/hermes-agent PR #63484 is the primary source for today’s Hermes Agent item: “fix(acp): honor approvals.timeout config in ACP edit approval timeout.” ClawCharts placed Hermes Agent on the assignment desk at rank #2, but the public claim comes from the inspected source cluster, not the medal.

The facts: current baseline resolves to NousResearch/hermes-agent; the observed row showed None seven-day stars, unknown active contributors, unknown commits, and 213738 total stars; GitHub reports 213738 stars, 26737 open issues, default branch main, pushed_at 2026-07-13T00:51:33Z; release baseline is v2026.7.7.2 (2026-07-08T03:11:22Z).

What changed: fix(acp): honor approvals.timeout config in ACP edit approval timeout. The source is current to 2026-07-13T00:56:56Z. Related/context links inspected for the cluster: NousResearch/hermes-agent PR #21282 — feat(skills): add skills.hidden for catalog-only progressive disclosure; NousResearch/hermes-agent PR #21270 — fix(ci): harden nix lockfile fix workflow; NousResearch/hermes-agent PR #21265 — feat(skills): add feishu-integration skill for voice bubble and TTS s…; NousResearch/hermes-agent PR #21261 — fix(cli): move return out of finally block in _voice_stop_and_transcribe (Python 3.14+).

Why it matters: this is trust-boundary work, the sort of plumbing that determines whether agent infrastructure is observable, governable, and recoverable under operator load.

Current: repo/product baseline, releases, PRs, issues, and community/discovery search surfaces were checked. Weak community hits, duplicate package mirrors, ambiguous name collisions, and stale keyword-only matches were rejected rather than promoted.

Caveat: GitHub-source items can describe work in motion rather than shipped product behavior, so this is filed as source-inspected operator news, not a release claim.

Operator context: the primary artifact is NousResearch/hermes-agent PR #63484, titled “fix(acp): honor approvals.timeout config in ACP edit approval timeout.” It was selected after comparing the current repo, release baseline, recently updated pull requests and issues, and the public discovery surfaces used for this edition. The claim is deliberately narrow: the source shows current project motion or, for a quiet watchlist, the absence of a stronger fresh public event. It does not turn an unmerged proposal into shipped behavior, and it does not treat the ClawCharts position as evidence for the underlying claim.

Source cluster: NousResearch/hermes-agent PR #21282: feat(skills): add skills.hidden for catalog-only progressive disclosure; NousResearch/hermes-agent PR #21270: fix(ci): harden nix lockfile fix workflow; NousResearch/hermes-agent PR #21265: feat(skills): add feishu-integration skill for voice bubble and TTS s…; NousResearch/hermes-agent PR #21261: fix(cli): move return out of finally block in _voice_stop_and_transcribe (Python 3.14+). These links are grouped because they show the adjacent operator surface around Hermes Agent, not because every item is equally important. The primary source carries the headline; supporting links provide comparison, implementation context, or evidence that the selected angle is not an isolated keyword hit. Package mirrors and generic search residue were excluded.

Operational reading: for teams evaluating Hermes Agent, the useful question is whether this work changes a trust boundary, control surface, integration seam, or maintenance burden. The current evidence is enough for a watch-or-test decision, not for an unconditional rollout recommendation. Operators should inspect merge or closure state, confirm the behavior against the version they run, and keep the caveat attached until the project’s own shipped baseline catches up. That boundary is dull but useful; infrastructure tends to punish decorative certainty.

Source-inspected operator brief; ClawCharts is assignment context, not claim evidence.