Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Kanban (Multi-Agent Board)

Kanban — Multi Agent Profile Collaboration Want a walkthrough? Read the Kanban tutorial — four user stories (solo dev, fleet farming, role pipeline with retry,

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/kanban

Kanban — Multi Agent Profile Collaboration Want a walkthrough? Read the Kanban tutorial — four user stories (solo dev, fleet farming, role pipeline with retry,

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Two surfaces: the model talks through tools, you talk through the CLI
  2. Kanban vs. delegate_task
  3. Core concepts
  4. Boards (multi-project)
  5. Managing boards from the CLI
  6. Managing boards from the dashboard
  7. File attachments
  8. Quick start
  9. Gateway-embedded dispatcher (default)
  10. Idempotent create (for automation / webhooks)
  11. Bulk CLI verbs
  12. How workers interact with the board
  13. Why tools instead of shelling to hermes kanban
  14. Recommended handoff evidence

Section map

Two surfaces: the model talks through tools, you talk through the CLI

Maps two surfaces: the model talks through tools, you talk through the cli to the Core Features documentation path, with the source page reserved for exact commands and updates.

Kanban vs. delegate_task

Maps kanban vs. delegate_task to the Core Features documentation path, with the source page reserved for exact commands and updates.

Core concepts

Maps core concepts to the Core Features documentation path, with the source page reserved for exact commands and updates.

Boards (multi-project)

Maps boards (multi-project) to the Core Features documentation path, with the source page reserved for exact commands and updates.

Managing boards from the CLI

Maps managing boards from the cli to the Core Features documentation path, with the source page reserved for exact commands and updates.

Managing boards from the dashboard

Maps managing boards from the dashboard to the Core Features documentation path, with the source page reserved for exact commands and updates.

File attachments

Maps file attachments to the Core Features documentation path, with the source page reserved for exact commands and updates.

Quick start

Maps quick start to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Two surfaces: the model talks through tools, you talk through the CLI, Kanban vs. delegate_task, Core concepts, Boards (multi-project), Managing boards from the CLI. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: kanban, multi-agent, board, multi, profile. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for kanban (multi-agent board) before applying exact upstream commands.

Verify firstTwo surfaces: the model talks through tools, you talk through the CLI

Open the source anchor for Two surfaces: the model talks through tools, you talk through the CLI and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Two surfaces: the model talks through tools, you talk through the CLI; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Kanban vs. delegate_task if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page