fix(scheduled): use project path identity for task bindings - #820
Merged
Merged
Conversation
Use the project storage identity when reading and writing scheduled bindings so Windows path aliases do not hide tasks from their sessions. Preserve legacy unbound and explicitly projectless tasks.
This was referenced Sep 21, 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
2 participants
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.
On Windows, a task created in the Scheduled page can be missing from an AI conversation in the same project. The page still shows the task, but the conversation cannot list, update or delete it because the saved paths use different spellings.
Use PI-Desktop's existing project path normalization when reading and saving task bindings. Same-project conversations can manage the task after restart; other projects remain isolated. Legacy unbound tasks and tasks explicitly created without a project keep their existing behavior.
Before and after — actual Windows desktop (1200 × 800, isolated profiles). A deterministic local model fixture calls the real tools and summarizes their results; no live model is used.
Before:
After:
Regression tests reproduce the visibility failure and cover Windows path aliases, cross-project rejection, all four cadences and reopening SQLite.
Validation details
0111e306cand the corresponding fix; focused checks were rerun after refreshing the candidates to46d4ee4ee.