Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix hermes cron create missing --toolsets flag [1 pull requests]

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…

The top-level hermes command supports -t TOOLSETS to specify which MCP toolsets to use, but hermes cron create has no equivalent flag. Scheduled cron jobs always run with the default toolset configuration and cannot be configured to use specific MCP servers.

Steps to reproduce

hermes cron create --help | grep -i toolsets
# No output — flag doesn't exist

Expected behavior

hermes cron create should accept --toolsets:

hermes cron create --toolsets "tdx-custom,agentmemory" "0 9 * * *" "run daily sync"

Use case

A cron job running data sync scripts needs access to specific MCP toolsets but shouldn't have access to all.

Version

Hermes Agent v0.13.0 (2026.5.7)

Root Cause

The top-level hermes command supports -t TOOLSETS to specify which MCP toolsets to use, but hermes cron create has no equivalent flag. Scheduled cron jobs always run with the default toolset configuration and cannot be configured to use specific MCP servers.

Steps to reproduce

hermes cron create --help | grep -i toolsets
# No output — flag doesn't exist

Expected behavior

hermes cron create should accept --toolsets:

hermes cron create --toolsets "tdx-custom,agentmemory" "0 9 * * *" "run daily sync"

Use case

A cron job running data sync scripts needs access to specific MCP toolsets but shouldn't have access to all.

Version

Hermes Agent v0.13.0 (2026.5.7)

Fix Action

Fixed

Code Example

hermes cron create --help | grep -i toolsets
  # No output — flag doesn't exist

---

hermes cron create --toolsets "tdx-custom,agentmemory" "0 9 * * *" "run daily sync"
RAW_BUFFERClick to expand / collapse

Description

The top-level hermes command supports -t TOOLSETS to specify which MCP toolsets to use, but hermes cron create has no equivalent flag. Scheduled cron jobs always run with the default toolset configuration and cannot be configured to use specific MCP servers.

Steps to reproduce

hermes cron create --help | grep -i toolsets
# No output — flag doesn't exist

Expected behavior

hermes cron create should accept --toolsets:

hermes cron create --toolsets "tdx-custom,agentmemory" "0 9 * * *" "run daily sync"

Use case

A cron job running data sync scripts needs access to specific MCP toolsets but shouldn't have access to all.

Version

Hermes Agent v0.13.0 (2026.5.7)

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…
#prompt formatting#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix hermes cron create missing --toolsets flag [1 pull requests]