Contributing Overview
Agirunner is a multi-repo public project.
Use this split as your guide:
agirunnerfor product docs, roadmap, and top-level project guidanceagirunner-platformfor the dashboard, API, and control planeagirunner-runtimefor the execution runtimeagirunner-playbooksfor the shared community catalog of importable playbooks, specialists, and skills
Start With The Right Surface
Section titled “Start With The Right Surface”For most outside contributors, the first step is picking the correct repository and the correct layer:
- product docs and information architecture work usually belongs here in
agirunner - operator UX, API, control-plane logic, and workflow records belong in
agirunner-platform - execution behavior, tools, containers, workspace handling, and runtime observability belong in
agirunner-runtime - curated catalog content and playbook-authoring guidance belong in
agirunner-playbooks
Good First Contribution Shapes
Section titled “Good First Contribution Shapes”Both first-time and experienced contributors are useful here.
Examples:
- clarify docs or fix broken guidance
- tighten configuration examples
- improve tests around supported behavior
- improve control-plane contracts in platform
- improve execution boundaries or tooling in runtime