AutoLoop: lightweight coordination for parallel AI-assisted development

[erbuyu2019-wq]

AutoLoop is a small Markdown + PowerShell toolkit for coordinating Codex or similar assistant-driven development across multiple threads, worktrees, and owner lanes.

The core problem is not simply getting an assistant to write more code. It is keeping scope, evidence, ownership, and acceptance clear when several assistant threads or worktrees are active at the same time.

AutoLoop's loop is intentionally simple:

work order -> worker report -> coordinator review / integration review -> closeout

A work order defines the Loop Contract: owner, goal, allowed scope, forbidden scope, stop rules, acceptance commands, and gate authority.

A worker report returns the Execution Record: changed files, verification, contract impact, not-verified items, risks, and next suggested step.

Coordinator review or integration review is the Acceptance Decision.

AutoLoop is deliberately not a daemon, GUI, autonomous agent runtime, project-management database, merge queue, or deployment tool. It does not automatically dispatch agents, control Codex Desktop threads, merge branches, operate hardware, deploy systems, or replace project-specific human gates.

It is useful when:

• Multiple assistant threads or worktrees are active.
• A project needs clear owner lanes and bounded work orders.
• Local readiness must stay separate from live, hardware, production, or release proof.
• Worker evidence and coordinator final acceptance need to be recorded separately.
• Chat history alone is not enough to audit what happened.

Useful starting points:

• README: https://github.com/erbuyu2019-wq/AutoLoop-public
• Parallel workflow example: https://github.com/erbuyu2019-wq/AutoLoop-public/blob/main/docs/use-cases/parallel-codex-workflow.md
• Boundary comparison: https://github.com/erbuyu2019-wq/AutoLoop-public/blob/main/docs/comparisons/autoloop-vs-agent-runtime.md

Feedback on the positioning, workflow boundary, and whether this matches real parallel AI-assisted development problems would be useful.