fix(scheduled): preserve manual task workspace bindings - #803
Merged
Merged
Conversation
Distinguish a saved workspace, including an explicit null binding, from a legacy task without one. Manual runs and editor updates must not retarget the task when the foreground project changes. Cover project and temporary bindings across restart, dispatch and edits, while retaining legacy fallback behavior.
vastsa
added a commit
to yuxino/PI-Desktop
that referenced
this pull request
Sep 21, 2026
Resolve the E2E documentation overlap after PR vastsa#803 landed.
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.
A Manual task created in project A runs in project B if you switch to B before clicking Run now. Editing the task's title can also change its saved project to B.
The fix keeps the task in its original project when running or editing it, even after restarting the app. Tasks created without a project stay that way, and legacy tasks keep their existing behavior.
Before the fix — actual desktop recording with step labels and highlighted results (2624 × 1824, 2× speed; final result at normal speed):
pr803-desktop-annotated-fast-hd.mp4
Regression tests reproduce the original failure and pass with the fix. They cover running and editing tasks after switching projects, including restart and no-project cases.
Validation details
user_skills.rs:921.52ad7affb0a5; base:43a3737352b65. The PR merge candidate has the same tested tree.