Add driftless to Orchestrators & autonomous loops#102
Open
mizan0515 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds driftless to Orchestrators & autonomous loops (placed last, ⭐ 0 — day-one project, sorted per the star convention).
It fits the category: an autonomous "keep running until done" loop that drives both Claude Code and Codex from one source of truth — surveys open issues, runs parallel workers, self-recovers, and opens/merges PRs behind human-only gates. It is non-developer-operable (you give a goal in plain language) and runs in a repo-local isolated home (
CLAUDE_CONFIG_DIR/CODEX_HOMEinside the repo) so it never touches host-global config. Containment + mirror-parity gates and an exhaustion-ledger keep "done" honest.Thanks for curating this list!