hermes - 💡(How to fix) Fix [Feature]: Be pass custom temperature to subagents

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…

Fix Action

Fix / Workaround

It would be nice if you could dispatch subagents with different temperatures (e.g. low for precise roles and high for creative roles)

RAW_BUFFERClick to expand / collapse

Problem or Use Case

It would be nice if you could dispatch subagents with different temperatures (e.g. low for precise roles and high for creative roles)

delegation in config has: model, provider, base_url, api_key, reasoning_effort, max_iterations, child_timeout_seconds but no temperature Related to: github.com/NousResearch/hermes-agent/issues/18732

Proposed Solution

Add a delegation.temperature config field (similar to reasoning_effort or others) and pass the through _build_child_agent() to the subagent.

The main agents could learn specific temperatures for specific subagents

Alternatives Considered

No response

Feature Type

Configuration option

Scope

Small (single file, < 50 lines)

Contribution

  • I'd like to implement this myself and submit a PR

Debug Report (optional)

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