fix(resume): isolate resume store keys by cwd hash to prevent cross-session contamination - #103
Open
wiliancolomboo-tech wants to merge 1 commit into
Conversation
… cross-session collision (getpipher#102)
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.
Resolves #102
Summary
When multiple parent sessions or parallel worktrees run in different working directories, subagents sharing the same
sessionKey(such as the defaultgeneral-purpose) collided in the global resume cache (~/.pi/agent/cache/fleet-resume/<backendId>.json). This caused child subagents in one directory to resume and poll transcripts from a completely different repository/session.Solution
${cwdHash}:${sessionKey}) when acwd(or default cwd) is provided.test/resume-store.test.mtsvalidating cwd isolation.🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 5 noreply@anthropic.com