---
title: jleechanorg/agent-orchestrator Repository
slug: jleechanorg-agent-orchestrator-repo
type: source
created: 2026-06-17
updated: 2026-06-17
status: active
tags:
  - source
  - repository
  - orchestration
  - worktrees
  - agents
sources:
  - https://github.com/jleechanorg/agent-orchestrator
related:
  - agent-orchestrator
  - agentic-pipeline-runner
  - code-review-vs-validation
  - tool-nodes-vs-llm-nodes
confidence: high
contradictions:
  - The fork is framed as zero-touch automation, but the README still reserves review/merge and portability decisions for human judgment.
bead_refs:
  - dark-factory-rr4
---

# jleechanorg/agent-orchestrator Repository

Source URL: [jleechanorg/agent-orchestrator](https://github.com/jleechanorg/agent-orchestrator)

Captured: 2026-06-17. Observed `main` HEAD: `3923e3cce815b541af59c2756945d184fde4ac25`. Provenance: public GitHub repository README, `ARCHITECTURE.md`, and local shallow clone inspection.

## Compact Takeaways

- Agent Orchestrator manages fleets of AI coding agents, giving each issue an isolated worktree, branch, session, and PR workflow.
- The jleechanorg fork is explicitly not a portable baseline; it targets the maintainer's own workflow and adds fork-specific plugins, CI gates, OpenClaw integration, Beads, Antigravity, MiniMax/Wafer adapters, evidence gates, and skeptic verification.
- The operating loop is: start dashboard/orchestrator, spawn workers, route CI/review feedback back to workers, and escalate when human judgment is needed.
- `ARCHITECTURE.md` emphasizes a repo-local config file as source of truth and deterministic runtime state under `~/.agent-orchestrator/`, with hash-based namespacing for sessions and worktrees.
- The README positions this fork as autonomous coding pipeline infrastructure, while upstream AgentWrapper/agent-orchestrator is a broader orchestration tool.

## Wiki Implications

- [[agent-orchestrator]] is a lower-level worker/session/PR orchestration layer that can serve as a backend or adjacent execution substrate for [[agentic-pipeline-runner]].
- [[code-review-vs-validation]] should include external review routing, CI remediation, evidence gates, and skeptic agents as validation infrastructure.
- [[dark-factory]] and [[software-factory]] should distinguish process graph execution from fleet/session management.

## Caveats

- This source is a fork README plus architecture doc, not a stable API contract.
- The fork has environment-specific assumptions; future agents should not copy its defaults without checking portability.