Documentation
MaintainerOS Docs
Connect a repo, understand route decisions, and wire Greptile verification plus Clustly bounties into your maintainer workflow.
Quickstart
Connect your repo
Authorize read access via GitHub. This flow does not request private-repo scopes or write access. MaintainerOS imports issues and stores the routing artifacts separately from your repository.
Classify the backlog
CLOD routes issues into AI, DEV, CLUSTLY, or CLARIFY with a confidence score and written rationale.
Review and override
Maintainers can override any route. Every decision is logged so future automation remains inspectable.
The Four Lanes
AI
Well-scoped, reproducible issues safe for an autonomous coding agent.
DEV
Architecture, security, or product decisions that need maintainer judgment.
CLUSTLY
Work that should be packaged for an outside contributor and bounty flow.
CLARIFY
Reports missing reproduction detail, scope, or acceptance criteria.
Greptile Verification
When a PR is submitted for a routed issue, Greptile checks the diff against the original issue and CLOD rationale before merge.
PR covers the issue spec and route rationale. No blocking gaps detected. Merge approved.
Clustly Bounty Integration
CLUSTLY-lane issues are packaged with a suggested reward, proof requirements, and a payout gate.
Route as CLUSTLY
Post bounty package
Release after proof