Cairn
NousResearch/hermes-agent

Cron jobs and MCP tools with enabled_toolsets handling

Cluster 23997 · agent. Data as of

1 open item. Fix merged in #50117 on 22 Jun 2026. Check it covers your case.

The short answer

0open issues
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #50117. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #50117. That is separate from the fix event.
Still open
0 issues and 1 PR.

Most members concern MCP server tools being missing or filtered in cron-triggered sessions when a job sets enabled_toolsets, with several PRs proposing ways to keep or layer MCP servers. One member is adjacent, about logging a warning for unknown toolset names, and one title suggests MCP tools should respect enabled_toolsets, which may point in a different direction.

Open issues0

No open issues.

Open PRs1

  • PR#53422fix(cron): MCP tools must respect enabled_toolsets on cron jobs

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #50117 fix(cron): layer enabled MCP servers onto per-job enabled_toolsets (#23997)

    merged to main

    files: cron/scheduler.py, hermes_cli/tools_config.py, scripts/release.py, tests/cron/test_scheduler.py

3 PRs closed without merging

From the close comments: PR volume cleanup 1 · done elsewhere 1 · other 1

  • #24095 fix(model_tools): log warning when enabled/disabled toolset is unknown · PR volume cleanup
  • #32788 fix(cron): keep MCP servers when a job sets enabled_toolsets (#23997) · other → #50117
  • #57898 fix: cron sessions now properly inherit MCP tools from platform config (#57861) · done elsewhere → 0491834, 62f8aa9
Closed issues · 2
  • Closed#23997[Bug] enabled_toolsets silently rejects MCP server names — MCP tools absent in cron sessions
  • Closed#57861Cron-triggered sessions never get Composio MCP tools attached (works fine in Telegram/TUI sessions)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Merged PRs
#50117
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
22 Jun 2026

For your agent

The same facts, typed.

cluster/23997.json
cluster/23997.md