hermes - 💡(How to fix) Fix [Feature]: Kanban task terminal-event callbacks for async orchestration (TUI/WebUI + coordinator workflows)

Problem or Use Case

We use hermes --tui (aka TUI) as our main interface because it is fast, supports file references with @ and avoids the message-length limits we hit in Discord.

After upgrading to v0.15.1, launching Kanban, creating and executing cards works reliably -> cards are decomposed into subtasks with dependency chains across different profiles. That's great.

However, completion notifications are not reliable on our primary local channels, and there is no built-in callback path that lets next steps happen automatically which means we end up doing manual work over and over:

• Check whether a task finished,
• Run kanban show to fetch results,
• Copy that context back into the active workflow
• etc.

Two primary use cases motivate this request:

Interactive TUI delegation

• From TUI, my main orchestrator agent delegates work to a specialist profile via Kanban.
• We keep working with the Orchestrator while the background task completes.
• When the delegated task is done, I'd like a callback to fire that notifies the Orchestrator agent and provides them with enough task context to continue naturally (as if they had performed the work themselves).

Coordinator-driven multi-agent workflows

• A coordinator profile routes work across specialist profiles (e.g. dev-pm creates a card that decomposes coding tasks to dev-coder and dev-qa and receives a callback when dev-qa has completed their review on the assigned work)
• Currently, dev-qa can decompose and assign tasks, but notifications cannot be registered or delivered in TUI or Web-ui and so I need to manually check to see that task is done. This is manageable for one-off tasks but doesn't work well when launching multiple cards.

Without fully understanding the internals of hermes-agent, I assuming that allowing humans and agents to register for a callback on kanban terminal events should enable these use cases.

Proposed Solution

Please consider adding a first-class Kanban callback feature for terminal events (completed, blocked, gave_up, crashed, timed_out, etc.).

What we are asking for (without prescribing implementation details):

• A clear way to register a callback for a task/workflow
• Reliable callback triggering on terminal events
• Callback payloads that include enough task context for meaningful follow-up
• Support for local-first workflows (TUI/WebUI), not only external gateway chat adapters
• Compatibility with existing notification behavior (notifications can remain lightweight pings; callbacks can handle workflow continuation)

Alternatives Considered

Local patching only: We could patch this ourselves, but it would likely be brittle and expensive to maintain. Changing implicit auto-subscribe behavior: This does not fully solve the continuation problem, and may not match upstream direction. Manual polling (kanban show, notify-list, etc.): Works, but adds too much repetitive operator work for daily use.

Feature Type

Gateway / messaging improvement

Scope

Medium (few files, < 300 lines)

Contribution

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

Debug Report (optional)