Open source · SDLC orchestrator

Operator

Run the closed loop from issue discovery through a verified pull request. Operator schedules external coding agents across registered repositories while protected branches and human approval remain the delivery boundary.

Explore Operator on GitHub Compare All Products

From Issue to Gated Pull Request

Autonomous execution stays bounded by repository scope, verification and a visible delivery boundary.

Discover: Scheduled stages inspect registered repositories and turn findings into tracked work.
Execute: One generic stage loop builds context, invokes an external coding-agent CLI, runs verification and routes the reviewer verdict.
Deliver: Approved output is committed to a scoped branch and exposed through a pull request with its audit trail intact.
Gate: Code changes wait for human merge approval. Operator never pushes master, main, develop or another protected default branch.

The Control Surface

Delivery boundary

Every Change Arrives as a Pull Request

Operator commits artifacts and code to scoped branches, then opens or updates a pull request. Protected default and integration branches receive no direct agent push.

Branch-scoped work
Pull request audit trail
Human merge gate

Observability

See State and Execution History

The web UI reads the same state store as the engine. A work item or pull request leads to execution events, reviewer verdicts, summaries and full logs.

Work-item state
Execution events
Verifier summaries and logs

Repository fleet

Run the Same Loop Across Repositories

Registered repositories share the same stage loop. Per-repository configuration selects the schedules, agents, verification commands and merge conditions.