hermes-teammates.yaml 3.8 KB

12345678910111213141516171819202122232425262728293031
  1. name: hermes-teammates
  2. repo: https://github.com/100yenadmin/hermes-teammates
  3. sha: de85f5d4793e122cde98342bddd6e1bf3cd53459
  4. description: "Give your agent a team: named subagents with their own instructions, tools and model, which it assigns work to, checks on and steers mid-task. The operator defines the roster; the agent follows up with a digest of earlier results and can work a Kanban teammates lane with a review handoff. Launches subagents only through the public ctx.subagent_lifecycle API. Stock Hermes; no patched core. Disclosure — adds six tools (teammates_roster, teammate_assign, teammate_check, teammate_wait, teammate_message, teammate_stop) and a /teammates command; the model picks only a teammate name, and the operator's config decides what it means. Teammates run as in-process Hermes subagents using credentials selected by Hermes from the parent, delegation settings or an operator-configured teammate route where supported. Toolsets narrow the parent's tools at toolset granularity only (the file toolset includes write_file and patch); Hermes can add inherited MCP toolsets back unless delegation.inherit_mcp_toolsets is false. A teammate with invalid settings refuses to launch. A delegated child cannot start teammates. Steering uses the lifecycle steer where Hermes provides it, otherwise delegate_task's steer action with the turn-bound parent. Under plugins.isolation: host every tool except the roster refuses. Optionally the roster is read from an operator-named YAML file (roster_file, relative to the profile home or absolute, so several profiles can share one); the plugin never writes it. It keeps a per-profile SQLite run ledger in its plugin-data folder (goals, statuses, clipped summaries, role hashes and available token receipts; no full transcripts). It does not read credential stores. Where supported in-process, subagent_start and post_api_request hooks collect token receipts for mapped child sessions. For a card assigned to its non-profile lane, it claims the card through the Kanban DB, heartbeats the claim and its worker, then moves the card to review without a reviewer, or blocks it on failure, a stop or an unavailable result; it never completes a card. It runs one in-process monitor thread per run to retain finished results and, for lane runs, keep the claim alive; no network calls, child processes or self-updates of its own. Completion-notice code exists but never injects on current Hermes because the host cannot bind notices to the receiving session; use teammate_wait instead. Includes a report-a-problem skill: the agent drafts a bug report and files it to this repository with gh only after the user approves the draft."
  5. maintainer: 100yenadmin
  6. tier: community
  7. category: automation
  8. requires_hermes: ">=0.21.4"
  9. docs_url: https://github.com/100yenadmin/hermes-teammates#readme
  10. version: "1.1.0"
  11. image: https://raw.githubusercontent.com/100yenadmin/hermes-teammates/de85f5d4793e122cde98342bddd6e1bf3cd53459/docs/media/banner.png
  12. screenshots:
  13. - https://raw.githubusercontent.com/100yenadmin/hermes-teammates/de85f5d4793e122cde98342bddd6e1bf3cd53459/docs/media/screenshot-roster.png
  14. - https://raw.githubusercontent.com/100yenadmin/hermes-teammates/de85f5d4793e122cde98342bddd6e1bf3cd53459/docs/media/screenshot-assign.png
  15. - https://raw.githubusercontent.com/100yenadmin/hermes-teammates/de85f5d4793e122cde98342bddd6e1bf3cd53459/docs/media/screenshot-results.png
  16. - https://raw.githubusercontent.com/100yenadmin/hermes-teammates/de85f5d4793e122cde98342bddd6e1bf3cd53459/docs/media/screenshot-slash-command.png
  17. readme: true
  18. platforms: []
  19. capabilities:
  20. provides_tools:
  21. - teammates_roster
  22. - teammate_assign
  23. - teammate_check
  24. - teammate_wait
  25. - teammate_message
  26. - teammate_stop
  27. provides_hooks:
  28. - subagent_start
  29. - post_api_request
  30. provides_middleware: []
  31. requires_env: []