hermes - 💡(How to fix) Fix Safe Executor Registry [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#24979Fetched 2026-05-14 03:50:00
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Participants
Timeline (top)
labeled ×3cross-referenced ×2
RAW_BUFFERClick to expand / collapse

What to build

Introduce a small executor registry for L that separates safe read-only executors from approval-gated or write-capable actions. This should make it easier to add new executors without scattering source checks and safety policy through command handling.

Acceptance criteria

  • Existing read-only executors are registered through a common interface or mapping.
  • The registry records executor id, supported work metadata, read-only status, and whether approval is required.
  • /lexecute routes through the registry while preserving existing behavior for gateway, LINE webhook, Cloudflare, service, and Docker status checks.
  • Unregistered work still blocks with a clear reason and no unsafe action.

Blocked by

  • #24975
  • #24977

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING