forgeo

About

forgeo serves maintainers who accumulate more well-specified tasks than attention: it reads a backlog from a JSON file or a Jira/GitHub/GitLab/HTTP tracker, selects the oldest OPEN task whose dependencies are complete, and runs the configured agent CLI on it — optionally inside a Docker sandbox with the network off by default — committing the result directly to main. When the backlog empties, the daemon switches to refactoring passes instead of idling. Transient agent failures retry automatically while persistent failures and genuine human decisions escalate via BLOCKER.md. Operationally it stays lightweight: forgeo validate dry-runs the configuration, backlogs are snapshotted automatically, multiple instances per repository feed one aggregate web dashboard, and a token-protected web UI exposes run status for solo maintainers and small teams.