Repository navigation
auto-claude 1.5.0: a free session of the repository takes over an orphaned run - #45
Merged
Merged
Conversation
…haned run A run was bound to the session that started it. When that session exited, was replaced after a reboot, or the person moved on in another session, the run only reported itself orphaned and stood still until someone typed /auto-claude resume (de-artifact on vela, 2026-11-16). - A session of the same repository takes the run over by itself, with the milestone being built, once the owner has been quiet for 10 min and this session has had no turn for 2 min. Not past 12 h of quiet, not with a .claude/auto-claude.stop in place. - The claim is written, then read back after 3 s; the claim still there wins. - Quiet is seen on two ticks in a row of this session, the last one recent, so a session waking from sleep does not take a live run. - The owner pulses on every timer fire under its own store key, so a long tick (deploy, CodeQL) does not look dead; a tick over 30 min stops it. - A session whose run was taken stops judging and guarding its milestone. - Taken over, the run keeps its deploy brake and time cap (minus the gap).
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
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.
Runs were bound to the session that started them; when it went away the run stood still until
/auto-claude resume. Now any free session of the same repository takes it over (see README table and commit message for the rules: 10 min quiet owner, 2 min free session, ≤12 h, no stop file, claim + 3 s read-back, sleep guard, separate owner pulse, demoted owner stands down, counters kept).Verified:
scripts/ci.shgreen (auto-claude 165 tests; the pulse test fails without the pulse). Real sessions on a scratch repo: session A started a queue run and was killed mid-milestone; session B took it over 10 min later (resume ... taken over from session 45ae5ce5, quiet 10 min), met the milestone and started the next.