Skip to content

auto-claude 1.5.0: a free session of the repository takes over an orphaned run - #45

Merged
unohee merged 1 commit into
mainfrom
auto-claude/adopt-orphan
Nov 18, 2026
Merged

unohee merged 1 commit into
mainfrom
auto-claude/adopt-orphan

Conversation

@unohee

@unohee unohee commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

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.sh green (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.

…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).
@unohee
unohee merged commit b713a7c into main Nov 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant