agora.yaml 3.4 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. name: agora
  2. repo: https://github.com/yzy806806/agora
  3. sha: 3ddd556e542b826498a90cc383c9020ae55897a9
  4. description: >-
  5. Self-driving multi-agent development team. Role-based workers (architect, developer,
  6. reviewer, tester, researcher, writer, devops) are each a real Hermes profile with its
  7. own SOUL.md and skills; they discuss and vote on decisions, and the adopted conclusion
  8. is executed by the same team. A "leader" profile chairs the discussions and a heartbeat
  9. cron wakes it to assess state, unblock workers and plan the next phase. Discussion and
  10. execution share one board: a motion is a sub-task of a per-project team channel task,
  11. speech and votes are `[agora:msg]` comments, the conclusion is written to task.result,
  12. and an adopted conclusion becomes execution tasks parented to the motion so context
  13. reaches workers through Hermes' own parent handoff. Ships 20 tools, 3 kanban lifecycle
  14. hooks, a dashboard tab and an `hermes agora` CLI; installing writes nothing — the three
  15. bundled skills are deployed by an explicit `hermes agora setup`. Disclosure — creates a
  16. Hermes profile per worker by asking core to provision it (`hermes profile create
  17. --clone`, which copies config.yaml and .env into the new profile as owner-only files,
  18. never symlinks to the real credentials); spawns
  19. `hermes -p <profile> chat -Q -q` subprocesses to speak in
  20. discussions (explicit toolset list: no kanban/clarify/cron; override via AGORA_SPEAKER_TOOLSETS)
  21. and to run dispatched tasks, which execute as full agents with that profile's toolset,
  22. including terminal and file writes inside the project workdir. Those subprocesses
  23. receive `--yolo --accept-hooks` ONLY when the project opted in via
  24. `agora_start_project(allow_unattended=True)`; the default is off, so a freshly installed
  25. team can read, discuss and plan but its flagged writes and shell commands fail closed.
  26. Also reads and writes the kanban database (tasks, task_comments, task_events, task_runs,
  27. task_links) restricted to its own project boards, including a persistent team-channel task
  28. pinned in `scheduled` status, and deletes a project's own tasks when it stops or completes;
  29. registers one recurring cron job and writes its runner script to
  30. HERMES_HOME/scripts/leader_heartbeat.sh; writes AGENTS.md into the configured project
  31. workdir; deploys three bundled skills into HERMES_HOME/skills/collaboration/; and serves a
  32. dashboard tab plus REST routes through the Hermes dashboard. No network egress of its own —
  33. model calls happen inside the spawned Hermes subprocesses under the operator's own provider
  34. credentials.
  35. maintainer: yzy806806
  36. tier: community
  37. category: automation
  38. requires_hermes: '>=0.20'
  39. docs_url: https://github.com/yzy806806/agora#readme
  40. version: "2.0.13"
  41. platforms: []
  42. readme: true
  43. capabilities:
  44. provides_tools:
  45. - agora_start_project
  46. - agora_stop_project
  47. - agora_project_status
  48. - agora_update_project
  49. - agora_create_task
  50. - agora_close_task
  51. - agora_raise_motion
  52. - agora_get_messages
  53. - agora_get_result
  54. - agora_list_motions
  55. - agora_close_motion
  56. - agora_message
  57. - agora_read_chat
  58. - agora_create_worker
  59. - agora_list_workers
  60. - agora_remove_worker
  61. - agora_list_templates
  62. - agora_create_team
  63. - agora_list_teams
  64. - agora_remove_team
  65. provides_hooks:
  66. - kanban_task_completed
  67. - kanban_task_claimed
  68. - kanban_task_blocked
  69. provides_middleware: []
  70. requires_env: []