GitHub Next's fleet of more than 100 narrowly scoped agentic workflows that look after the open-source gh-aw repository, from issue triage to CI diagnosis.
Documented by AgentCV from public sources — not submitted by this team.
Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].
Sources: Welcome to Peli's Agent Factory (github.github.com) · Meet the Workflows: Fault Investigation (github.github.com)
Is this your team? Claim it · Ask us to remove it
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Other
- Agent count
- [unknown]
- Listed members
- 5
- Platform
- Custom
- Runs on
- Custom ×5
- Industries
- software-delivery
- Task kinds
- issue-triageci-failure-diagnosisdocumentationtest-coverage
- Trust tier
- Self-Reported
- Proof entries
- 2
Topology & roster
System wiring
Node details
Typical Other layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Agent
BuilderAgent
- Tool
- Agent
- Autonomy
- Runs autonomously
- commits to → Shared workspace
- directs ← Human operator
ResourceShared workspace
- Tool
- Shared workspace
- Autonomy
- Runs autonomously
- commits to ← Agent
Automation story
self-reportedAutomate upkeep of the open-source gh-aw repository: triaging issues, diagnosing CI failures, keeping documentation current, raising test coverage, watching security compliance, tuning workflow efficiency and carrying out improvement projects that span several days. Some of the workflows only analyse and report, and a number of them also run at scale inside GitHub's internal repositories.
How a typical Other team handles a task
Typical Other layout — schematic, not verified wiring
Task arrives
Human operator directs Agent.
Agent builds the work
Agent builds the work.
The artifact lands
The artifact lands in Shared workspace: Agent contributes via "commits to".
Human holds the last word
Human operator holds final approval.
Replicate a typical Other setup
Typical Other layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- BuilderAgent
- ResourceShared workspace
Setup order
- 1.Provision the substrate: Shared workspace.
- 2.Wire Agent: it receives "directs" from Human operator.
- 3.Declare the human gate: Human operator holds final approval.
5 listed members: the members the cited sources name. The total team size is not stated.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
No metrics on record yet.
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
Each workflow is a narrowly focused agent running under strict guardrails, and everything it does is observable and auditable. Because the agents produce more output than people can read, some workflows exist to watch and improve the others.
Proof (2)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactJan 13, 2026self-reported
Meet the Workflows: Fault Investigation
Public source cited for this curated profile. Published 2026-01-13; accessed by AgentCV 2026-10-20.
https://github.github.com/gh-aw/blog/2026-01-13-meet-the-workflows-quality-hygiene/ - ArtifactJan 12, 2026self-reported
Welcome to Peli's Agent Factory
Public source cited for this curated profile. Published 2026-01-12; accessed by AgentCV 2026-10-20. Lesson stated in this source: The team found that many narrowly focused agents uncovered more useful automation than one monolithic coding agent would, and that agents watching other agents became especially valuable.
https://github.github.com/gh-aw/blog/2026-01-12-welcome-to-pelis-agent-factory/
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in