hermes - 💡(How to fix) Fix [Feature]: delegation-per-task-endpoint-overrides [1 comments, 2 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#14974Fetched 2026-04-24 10:43:53
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1referenced ×1

Code Example

{
  "base_url": "http://host:11434/v1",
  "provider": "custom",
  "api_key": "ollama"
}

### Alternatives Considered

_No response_

### Feature Type

Other

### Scope

None

### Contribution

- [ ] I'd like to implement this myself and submit a PR

### Debug Report (optional)
RAW_BUFFERClick to expand / collapse

Problem or Use Case

Expose base_url, provider, and api_key as optional per-task fields in delegate_task, allowing each sub-agent to target a different model endpoint.

This enables true parallel execution across multiple inference servers (e.g. multiple Ollama instances) instead of routing all children to a single backend.

Implementation:

  • Extend delegate_task schema with base_url, provider, api_key
  • Wire task-level overrides into _build_child_agent()
  • Apply precedence: task override → delegation config → parent fallback

This change is fully backward compatible and leverages existing internal override support already present in _build_child_agent().

Proposed Solution

Expose per-task model routing overrides in the delegate_task tool schema, allowing each sub-agent to target a different backend.


1. Extend Task Schema

Add optional fields to each task:

{
  "base_url": "http://host:11434/v1",
  "provider": "custom",
  "api_key": "ollama"
}

### Alternatives Considered

_No response_

### Feature Type

Other

### Scope

None

### Contribution

- [ ] I'd like to implement this myself and submit a PR

### Debug Report (optional)

```shell

extent analysis

TL;DR

Extend the delegate_task schema to include optional base_url, provider, and api_key fields to enable per-task model routing overrides.

Guidance

  • Review the proposed solution to ensure it aligns with the existing internal override support in _build_child_agent().
  • Verify that the extended task schema is properly wired into the _build_child_agent() function to apply task-level overrides.
  • Test the implementation to ensure true parallel execution across multiple inference servers.
  • Consider adding validation for the optional fields to prevent potential errors.

Example

{
  "base_url": "http://host:11434/v1",
  "provider": "custom",
  "api_key": "ollama"
}

This example shows the proposed optional fields for the task schema.

Notes

The implementation should be fully backward compatible, but thorough testing is necessary to ensure that the changes do not introduce any regressions.

Recommendation

Apply the proposed workaround by extending the delegate_task schema and wiring the task-level overrides into _build_child_agent(), as this enables true parallel execution across multiple inference servers.

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

hermes - 💡(How to fix) Fix [Feature]: delegation-per-task-endpoint-overrides [1 comments, 2 participants]