hermes - 💡(How to fix) Fix [Bug]: Kanban dispatcher does not verify assigned profile has required toolsets before spawning worker

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…

When the kanban dispatcher claims a task and spawns a worker for an assigned profile, it does not check whether the profile has the toolsets needed to actually do the work. If a task requires web browsing or terminal access but the assigned profile only has hermes-cli, the worker starts, discovers it cannot access the tools it needs, and either crashes or produces degraded output.

This is the second half of the skills-vs-toolsets confusion: even when skills are correctly specified, the dispatcher makes no effort to verify that the assigned profile has the toolsets those skills depend on.

Error Message

  1. Warn and skip — log a warning and leave the task in ready for a better-equipped worker

Root Cause

When the kanban dispatcher claims a task and spawns a worker for an assigned profile, it does not check whether the profile has the toolsets needed to actually do the work. If a task requires web browsing or terminal access but the assigned profile only has hermes-cli, the worker starts, discovers it cannot access the tools it needs, and either crashes or produces degraded output.

This is the second half of the skills-vs-toolsets confusion: even when skills are correctly specified, the dispatcher makes no effort to verify that the assigned profile has the toolsets those skills depend on.

Fix Action

Fix / Workaround

When the kanban dispatcher claims a task and spawns a worker for an assigned profile, it does not check whether the profile has the toolsets needed to actually do the work. If a task requires web browsing or terminal access but the assigned profile only has hermes-cli, the worker starts, discovers it cannot access the tools it needs, and either crashes or produces degraded output.

This is the second half of the skills-vs-toolsets confusion: even when skills are correctly specified, the dispatcher makes no effort to verify that the assigned profile has the toolsets those skills depend on.

The dispatcher should check the assigned profile's toolsets before claiming and spawning. If the profile lacks toolsets that the task's skills require, the dispatcher should either:

RAW_BUFFERClick to expand / collapse

Summary

When the kanban dispatcher claims a task and spawns a worker for an assigned profile, it does not check whether the profile has the toolsets needed to actually do the work. If a task requires web browsing or terminal access but the assigned profile only has hermes-cli, the worker starts, discovers it cannot access the tools it needs, and either crashes or produces degraded output.

This is the second half of the skills-vs-toolsets confusion: even when skills are correctly specified, the dispatcher makes no effort to verify that the assigned profile has the toolsets those skills depend on.

Steps to Reproduce

  1. Create a profile researcher with only toolsets: [hermes-cli]
  2. Create a kanban task assigned to researcher with skill kanban-worker
  3. The worker starts but has no web, browser, terminal, or file toolsets
  4. Worker cannot search the web, browse pages, or write files — task fails or produces trivial output

Expected Behavior

The dispatcher should check the assigned profile's toolsets before claiming and spawning. If the profile lacks toolsets that the task's skills require, the dispatcher should either:

  1. Warn and skip — log a warning and leave the task in ready for a better-equipped worker
  2. Auto-upgrade — temporarily add the missing toolsets to the spawn command (opt-in behavior)
  3. Block with context — move the task to blocked with a clear reason like "Profile researcher lacks toolsets: web, browser — add them to ~/.hermes/profiles/researcher/config.yaml"

Suggested Fix

Add a toolset-presence check in the dispatcher's claim logic, between selecting a task and spawning the worker process. Read the profile's config.yaml, extract toolsets:, and compare against a minimum set required by the task's skills. The skill manifest could declare required_toolsets: [web, browser] to make this check explicit.

Environment

  • Hermes Agent v2.x
  • Affects all kanban workloads where profiles are created ad-hoc
  • The kanban-orchestrator skill now documents this as a pitfall: "Profile toolsets must be pre-configured"

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 [Bug]: Kanban dispatcher does not verify assigned profile has required toolsets before spawning worker