You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very handy to be able to import existing branches when adding workspaces. My use case is the following:
I work from multiple workstations (e.g., laptop when I'm on the move, and a Mac mini when I'm working from home), and sometimes I need to work on the same branch from both workstations. I've not been able to make this workflow work, because worktrees lifecycle are fully managed by superset, and even If I manually create worktrees based on an existing branch, superset will not find/recognize them.
Ideally, this workflow would work:
from my Mac mini, start working on a new feature A by adding a new workspace: this will create a new branch and worktree
finish work on the feature for the day and push changes: this would commit changes and push to remote branch
from my laptop, add a new workspace based on the remote branch to continue working
@dnlopes I think that's reasonable, I need the same feature for checking out and reviewing PR as well. For the UX, would it make sense to add that to advanced options for your workflow? Perhaps a check to create a new branch vs checking out an existing branch.
Please feel free to open a PR and I can take a look as well :)
@dnlopes Looking at it now, existing does make more sense. If you could open the PR with your ideal flow, we can take a look and update it with a finalized UX. Would that work?
@Kitenite Happy to pick this up if it is not in progress - got a WIP most of the way thought it is a checkbox on the new branch but can easily be moved to existing. Wasn't really sure if the intent if that tab. It reads as it would allow you to open worktrees not in SuperSet but all of the worktrees I remove from superset get deleted, so not sure when this would actually have content in the current state.
@Kitenite apologies for the radio silence. I know I volunteered to open the PR upstream, but a lot of stuff happened in between, and was unable to. Sorry.
I have the PR on my fork here, but it's not yet polished to open the final one here. I will be in PTO until next Wednesday, so I won't be able to progress until I come back.
@dnlopes no worries just checking in since I needed to do this as well. will get this over the line!
@chasemcdo existing should also allow you to open from other existing worktrees. I think the future of that tab is for anything reusing an existing branch, even remote.
Do you want to pick that up otherwise I can as well
Activity
dnlopes commentedon Jan 9, 2026
I already have a branch in my fork with this change implemented. I'm just wondering whether or not you find this enhancement reasonable or not.
Kitenite commentedon Jan 9, 2026
@dnlopes I think that's reasonable, I need the same feature for checking out and reviewing PR as well. For the UX, would it make sense to add that to advanced options for your workflow? Perhaps a check to create a new branch vs checking out an existing branch.
Please feel free to open a PR and I can take a look as well :)
dnlopes commentedon Jan 12, 2026
@Kitenite I had actually used the "Existing" tab, intuitively it made more sense to me, but I can see good arguments for both sides.
I updated to use the "New" tab, something like this:
Default state, same behavior:

Picker disabled (branch name input becomes greyed out):

Existing branch selected (input updated with branch name but still greyed out):

Let me know what you think, and I can prepare a PR.
Thanks.
Kitenite commentedon Jan 12, 2026
@dnlopes Looking at it now, existing does make more sense. If you could open the PR with your ideal flow, we can take a look and update it with a finalized UX. Would that work?
@AviPeltz for visibility
dnlopes commentedon Jan 13, 2026
@Kitenite I was not able to open the PR today, but the branch is ready on my local. I will open the PR tomorrow.
Kitenite commentedon Jan 13, 2026
Sounds great let me know how I can help @dnlopes !
Kitenite commentedon Jan 20, 2026
Any luck on this otherwise I can prioriztize this as well
chasemcdo commentedon Jan 22, 2026
@Kitenite Happy to pick this up if it is not in progress - got a WIP most of the way thought it is a checkbox on the new branch but can easily be moved to existing. Wasn't really sure if the intent if that tab. It reads as it would allow you to open worktrees not in SuperSet but all of the worktrees I remove from superset get deleted, so not sure when this would actually have content in the current state.
dnlopes commentedon Jan 22, 2026
@Kitenite apologies for the radio silence. I know I volunteered to open the PR upstream, but a lot of stuff happened in between, and was unable to. Sorry.
I have the PR on my fork here, but it's not yet polished to open the final one here. I will be in PTO until next Wednesday, so I won't be able to progress until I come back.
Kitenite commentedon Jan 22, 2026
@dnlopes no worries just checking in since I needed to do this as well. will get this over the line!
@chasemcdo existing should also allow you to open from other existing worktrees. I think the future of that tab is for anything reusing an existing branch, even remote.
Do you want to pick that up otherwise I can as well
chasemcdo commentedon Jan 23, 2026
Done ;)