Hermes plugin uses only part of Hermes's plugin interface; its hooks also run in the gateway
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- developer-experience, tooling
Research direction
Start by reading the docstring at plugin/hermes/__init__.py lines 29-33 and the limitations section at plugin/README.md lines 430-434, then compare them against Hermes's middleware, pre_llm_call, subagent_start and register_command docs linked in the issue. The open question is a maintainer decision: extend plugin/hermes in-tree or link the external adapter DylDigitals/tokeneconomizer-for-hermes. Done means that decision is recorded; only then can a port be scoped, with gateway, sub-agent and cron hook coverage as the target.
Written by the indexing model from the issue text.
Description
Hermes plugin hooks run in both the CLI and the gateway (event hooks: "CLI + Gateway"). plugin/hermes uses only part of that. It follows only classic CLI and one-shot sessions, so gateway sessions (Discord, Telegram, the API server), sub-agents and cron get no micro-skills or loop guard (docstring). Tool pruning, the repository map and /te are not ported (README).
Hermes documents an interface for each missing piece:
- Tool pruning:
llm_requestmiddleware can "replace effective provider kwargs before provider execution", and the request includes the tool definitions. - Repository map: the same
pre_llm_callhook the plugin already uses for micro-skills. - Sub-agents:
subagent_startpassesparent_session_idandchild_session_id. /te:ctx.register_command"adds/namein CLI and gateway sessions" (plugins).
We ported this repository at 7042ea8 with these interfaces: DylDigitals/tokeneconomizer-for-hermes. It runs in gateway sessions and supports 39 of the 41 capabilities in its MATRIX.md, with 131 offline tests and real-session runs on Hermes 0.22.2. It cannot prune tools under the codex_app_server runtime or import old session history.
Related: #85. Would you take a PR that extends plugin/hermes, or would you rather link our adapter from its README section?
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 500
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 124
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/TokenEconomizer
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/TokenEconomizer#264 ·
Maintainers usually reply within 1 day
-
TokenEconomizer: repository-planted code runs in the plugin process; tmp writes follow symlinksPossibly taken @kevinveenbirkenbach claimed this 2 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
microsoft/TokenEconomizer#260 ·
Maintainers usually reply within 1 day
-
CommandCode supportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/TokenEconomizer#205 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/TokenEconomizer#193 ·
Maintainers usually reply within 1 day
All issues in microsoft/TokenEconomizer
Similar issues
-
[Bug]: reme CLI crashes when the running server used a relative config pathPossibly taken @nurlanmnn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/ReMe#770 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
sickn33/agentic-awesome-skills#2437 ·
Maintainers usually reply within 1 day
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ethereum/consensus-specs#5846 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
BrainLesion/BraTS#200 ·