docs: backups fire at session start, not just end - #10
Merged
Conversation
The claim 'backups happen automatically at session end' is misleading: a worktree/pane manager (Orca) SIGKILLs the process group on close, and a SIGKILL runs no SessionEnd hook. Since 0.2.6 the SessionStart hook takes the same throttled backup and always runs, so it — not SessionEnd — is what keeps backups current. Correct README and docs/backup.md to say 'session boundaries' and call out the force-kill case. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NnaQwZUSDRbVUNh8fsdksD
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.
The README/backup docs said backups happen "automatically at session end (~once a day)". That's the one case that fails: a worktree/pane manager (Orca) SIGKILLs the process group on close, and a
SIGKILLruns noSessionEndhook (verified this session).Since 0.2.6 the
SessionStarthook takes the same throttled backup (--if-stale 20) and always runs — so it, notSessionEnd, is what keeps backups current. Reword README and docs/backup.md to say backups fire at session boundaries (start reliably, end on a clean exit) and to name the force-kill case. Docs-only; no version change.🤖 Generated with Claude Code