Dependencies that explain the queue
Missing prerequisites can be created or reused. Blocked tasks wait for the work they need, while the control room distinguishes active work, waiting work and previous failures.
Windows app · Source available
A control room for coding agents.
Fletchery turns GitHub issues into a coordinated queue for Claude Code, Codex and OpenCode. Follow work from its prerequisites through coding, checks, review and project-specific build and merge rounds.
One queue. Visible progress.
- Plan
Issues describe the work; dependencies decide what can start.
- Code
Available agents work in separate checkouts, with up to ten workers.
- Check & review
Project checks and configured reviewers assess the proposed changes.
- Build & merge
Eligible changes enter bounded integration rounds with project-specific validation.
Worker count depends on account limits and available resources. Automatic merges depend on settings, eligibility, dependencies and validation. A completed agent task is not itself proof that a change is ready to ship.
Keep the work moving and recoverable.
Repairs with the evidence intact
Concrete fixes get bounded retries. Failed attempts and generated files are preserved so the next attempt can use what was learned, rather than losing the work behind a failure.
Respect the machine
Resource waits survive restarts without consuming repair attempts. Ownership and surviving processes matter when releasing heavy-work reservations. The interface explains why a worker is idle.
Finish integration before adding work
Eligible merges take priority over new coding. Bounded batches and failure isolation keep integration manageable; validation is reused only when the recorded fingerprints match.
Existing agents, coordinated locally.
Fletchery is a coding harness: software that organizes other coding agents. It does not train a new foundation model. Claude Code, Codex and OpenCode use your configured accounts and models; their costs and usage limits still apply.
Routing can be configured, informed by previous outcomes and overridden manually. Cross-provider review is supported when suitable reviewers are configured and available. Your project supplies the checks, build requirements and merge rules.
The Windows control room provides task and worker views, persistent dark mode, current merge progress and explicit waiting reasons. It separates historical failures from live status so an earlier error does not look like a currently broken run.
Merged improvements, with a source trail.
These changes are merged in the public repository. They describe current development, not a newly numbered release.