Skip to content

auto-claude 1.4.1: a reload in a removed worktree keeps the run ticking - #44

Merged
unohee merged 1 commit into
mainfrom
auto-claude/vanished-cwd
Nov 18, 2026
Merged

unohee merged 1 commit into
mainfrom
auto-claude/vanished-cwd

Conversation

@unohee

@unohee unohee commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

session.start resolved the repository from the session's directory as is. A session left in a milestone worktree that the driver removed after its merge got no root on /reload-plugins, so every tick returned at once and the run stood still without a notice (kyte-portal on vela: 2026-11-17 05:08Z, 18 h).

session.start now walks up to the nearest existing directory, as the commands already did (existingDir, shared with sessionRoot).

Test: a reload while the session sits in a removed worktree keeps ticking the run fails without the fix and passes with it. scripts/ci.sh green.

session.start resolved the repository from the session's directory as is.
A session left in a milestone worktree the driver had removed after its
merge got no root on /reload-plugins, so every tick returned at once and
the run stood still without a notice (kyte-portal on vela, 2026-11-17
05:08Z, 18 h). session.start now walks up to the nearest existing
directory, as the commands already did.
@unohee
unohee merged commit 354b3a7 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