Repository navigation
fix(handoff-sync): move the local handoff folder to ~/.local/state - #15
Merged
Merged
Conversation
The Claude Code sandbox denies writes under ~/.claude, so on a host with no Drive mount, prepare-handoff cannot create ~/.claude/handoffs. The default local folder is now ~/.local/state/claude-handoffs, which the sandbox allows. HANDOFF_LOCAL_DIR still overrides it. A new test pins the default. It fails against main's copy. TILSIT needs a one-time migration after this merges, because rclone bisync keys its state on the local/remote path pair: 1. git -C ~/Developer/scripts pull 2. mv ~/.claude/handoffs ~/.local/state/claude-handoffs 3. rclone bisync ~/.local/state/claude-handoffs 'gdrive:Claude Handoff' --resync --drive-skip-gdocs 4. Check the next cron run in ~/.local/state/rclone/handoff-sync.log The handoff skills in claude-config move to the same folder in a second PR, after this migration, so TILSIT never writes a handoff that cron does not sync. Advances smartwatermelon/claude-config#779 (item 3).
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.
Problem
The Claude Code sandbox denies writes under
~/.claude. On a host with no Drive mount, prepare-handoff writes to~/.claude/handoffs, so a sandboxed session cannot save a handoff there. This is item 3 of smartwatermelon/claude-config#779.Change
handoff-sync.sh: the default local folder is now~/.local/state/claude-handoffs, which the sandbox allows.HANDOFF_LOCAL_DIRstill overrides it.README.md: thehandoff-sync.shrow names the new folder.tests/handoff-sync.bats: a new test pins the default. It fails against main's copy.TILSIT migration (after merge, before the skills PR)
rclone bisync keys its state on the local/remote path pair, so the new folder needs one
--resync. The order matters:git -C ~/Developer/scripts pullfirst. If the folder moved first, the next cron run would run the old script, create an empty~/.claude/handoffs, and bisync it against the full remote. With the new script in place, cron fails harmlessly on "no prior listing" until step 4.mv ~/.claude/handoffs ~/.local/state/claude-handoffsrclone bisync ~/.local/state/claude-handoffs 'gdrive:Claude Handoff' --resync --drive-skip-gdocs --dry-run, and read the output.--dry-run.~/.local/state/rclone/handoff-sync.log.The handoff skills in claude-config move to the same folder in a second PR, after this migration. If the skills moved first, TILSIT would write handoffs to a folder that cron does not sync.
Advances smartwatermelon/claude-config#779 (item 3).