Repository navigation
feat(autosync): RILL_AUTOSYNC_START=0 turns off hook-start only - #108
Merged
Merged
Conversation
A caller that opens a Claude Code conversation just to show it (the Rill GUI resuming a past conversation without a prompt) waited for a full fetch, rebase and push before the conversation appeared: 1.5-2.5 s with nothing to push, up to the 60 s lock wait while another run holds the lock. The GUI already keeps the vault in step on its own timer, so that wait buys nothing there. RILL_AUTOSYNC=0 cannot be used: it also turns off hook-stop, and a process's environment cannot change after spawn. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why
A GUI that resumes a past Claude Code conversation only to show it waited for a full
rill autosyncrun (fetch, rebase, push) in the SessionStart hook before the conversation appeared: 1.5–2.5 s with nothing to push, up to the 60 s lock wait while another run holds the lock (for example the GUI's own one-minute sync). That GUI keeps the vault in step on its own timer, so the wait buys nothing there.RILL_AUTOSYNC=0is not usable for this: it also turns offhook-stop, and a process's environment cannot change after spawn, so the conversation's later turns would never be pushed by the hook.What
rill autosync hook-startdoes nothing whenRILL_AUTOSYNC_START=0.hook-stop,run,checkare unaffected.test/cli/test-autosync.sh: hook-start with the variable commits and pushes nothing; hook-stop with the variable still pushes. 55/55 pass.Codex review: no findings.
🤖 Generated with Claude Code