fix(frontend): canonicalize daemon identity paths#2285
Open
anirudh5harma wants to merge 1 commit into
Open
Conversation
This was referenced Jun 29, 2026
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.
Summary
The desktop app now recognizes equivalent checkout paths on macOS instead of showing an empty dashboard when the daemon reports different path casing. Filesystem-backed canonicalization still rejects genuinely different checkouts and preserves Windows case-insensitive identity behavior.
Closes #2279.
This ports aoagents/ReverbCode#415 onto the current supervisor implementation without carrying unrelated changes.
Validation
npm run typechecknpm run packagegit diff --checkPost-Deploy Monitoring & Validation
After the next desktop build, launch the app and daemon from path spellings that differ only by macOS casing. Healthy behavior is a ready daemon and populated board with no wrong-checkout identity message. A false match between genuinely different checkouts is the rollback trigger; the focused boundary tests cover that distinction.