Kanban tool visibility for orchestrator profiles and toolsets

Fixes on record

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

• #19427 fix(kanban): drop worker identity claim from KANBAN_GUIDANCE

  merged to main

  files: agent/prompt_builder.py

  Show the diff

  • agent/prompt_builder.py

    @@ -183,8 +183,8 @@ def _strip_yaml_frontmatter(content: str) -> str:
     )
     
     KANBAN_GUIDANCE = (
    -    "# You are a Kanban worker\n"
    -    "You were spawned by the Hermes Kanban dispatcher to execute ONE task from "
    +    "# Kanban task execution protocol\n"
    +    "You have been assigned ONE task from "
         "the shared board at `~/.hermes/kanban.db`. Your task id is in "
         "`$HERMES_KANBAN_TASK`; your workspace is `$HERMES_KANBAN_WORKSPACE`. "
         "The `kanban_*` tools in your schema are your primary coordination surface — "

• #19606 fix(kanban): allow orchestrator profiles to see kanban tools via toolsets config

  merged to main

  files: tests/tools/test_kanban_tools.py, tools/kanban_tools.py

  Show the diff

  • tests/tools/test_kanban_tools.py

    @@ -467,8 +467,8 @@ def test_kanban_guidance_in_worker_prompt(monkeypatch, tmp_path):
             skip_memory=True,
         )
         prompt = a._build_system_prompt()
    -    # Header phrase
    -    assert "You are a Kanban worker" in prompt
    +    # Header phrase (identity-free — SOUL.md owns identity, layer 3 is protocol)
    +    assert "Kanban task execution protocol" in prompt
         # Lifecycle signals
         assert "kanban_show()" in prompt
         assert "kanban_complete" in prompt

  • tools/kanban_tools.py

    @@ -40,13 +40,31 @@
     # ---------------------------------------------------------------------------
     
     def _check_kanban_mode() -> bool:
    -    """Tools are available iff the current process has ``HERMES_KANBAN_TASK``
    -    set in its env, which the dispatcher sets when spawning a worker.
    +    """Tools are available when:
     
    -    Humans running ``hermes chat`` see zero kanban tools. Workers spawned
    -    by the kanban dispatcher (gateway-embedded by default) see all seven.
    +    1. ``HERMES_KANBAN_TASK`` is set (dispatcher-spawned worker), OR
    +    2. The current profile has ``kanban`` in its toolsets config
    +       (orchestrator profiles like techlead that route work via Kanban).
    +
    +    Humans running ``hermes chat`` without the kanban toolset see zero
    +    kanban tools. Workers spawned by the kanban dispatcher (gateway-
    +    embedded by default) and orchestrator profiles with the kanban
    +    toolset enabled see all seven.
         """
    -    return bool(os.environ.get("HERMES_KANBAN_TASK"))
    +    if os.environ.get("HERMES_KANBAN_TASK"):
    +        return True
    +
    +    # Check if the current profile has the kanban toolset enabled.
    +    # Uses load_config() which has mtime-based caching, so this adds
    +    # negligible overhead. The check_fn results are further TTL-cached
    +    # (~30s) by the tool registry.
    +    try:
    +        from hermes_cli.config import load_config
    +        cfg = load_config()
    +        toolsets = cfg.get("toolsets", [])
    +        return "kanban" in toolsets
    +    except Exception:
    +        return False
     
     
     # ---------------------------------------------------------------------------

• #35729 docs(toolsets): clarify all/* wildcard does not enable kanban

  merged to main

  files: website/docs/reference/toolsets-reference.md