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
I've been a long-time user of Conductor, an app that I have a severe love-hate relationship with, and I've been meaning to migrate over to Paseo for quite some time. I love everything that Paseo is doing, but there is a small number of gaps that in the past have blocked me from making the switch for good. Only one of them is truly critical (at least for my workflow), and I'd like to discuss it here to find out if a PR for this would get accepted.
Luckily, it's not a terribly complicated gap!
Conductor has a feature where, after working on and merging a PR, it lets me continue to use the existing workspace, worktree, and existing agent conversations, to work on more PRs. I'd say 80% of my changes happen in single-PR workspaces, but sometimes I do have longer sessions where I work on multiple PRs in a row with the agent. This is where this becomes useful.
Conductor facilitates this with two features that Paseo, unless I've been catastrophically "holding it wrong" in some fashion, seems to be lacking at the moment:
An explicit "Continue" button next to its "Archive Workspace" button. Clicking this will essentially execute a git fetch, then move the worktree to a fresh branch off of the upstream branch (eg. origin/main).
Even when not going through this button, its worktree state monitoring will automatically pick up if my agent (or I myself) performed the git actions described above.
The latter is probably the more critical gap in Paseo right now; even if after merging a PR I manually/agentically move the worktree to a fresh branch, Paseo's Git workflow button will remain stuck on "Archive workspace", and not allow me to make more commits, push, or open a PR. The behavior I'd love to see here is that Paseo picks up that the worktree's branch is no longer linked to the previous PR the workspace was tracking, and let me stay in that loop. The cherry on top would be an additional "Continue workspace" action in the workflow management dropdown as an alternative to "Archive workspace".
I'd be more than happy to contribute a PR for these, just wanted to check in first.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I've been a long-time user of Conductor, an app that I have a severe love-hate relationship with, and I've been meaning to migrate over to Paseo for quite some time. I love everything that Paseo is doing, but there is a small number of gaps that in the past have blocked me from making the switch for good. Only one of them is truly critical (at least for my workflow), and I'd like to discuss it here to find out if a PR for this would get accepted.
Luckily, it's not a terribly complicated gap!
Conductor has a feature where, after working on and merging a PR, it lets me continue to use the existing workspace, worktree, and existing agent conversations, to work on more PRs. I'd say 80% of my changes happen in single-PR workspaces, but sometimes I do have longer sessions where I work on multiple PRs in a row with the agent. This is where this becomes useful.
Conductor facilitates this with two features that Paseo, unless I've been catastrophically "holding it wrong" in some fashion, seems to be lacking at the moment:
An explicit "Continue" button next to its "Archive Workspace" button. Clicking this will essentially execute a
git fetch, then move the worktree to a fresh branch off of the upstream branch (eg.origin/main).Even when not going through this button, its worktree state monitoring will automatically pick up if my agent (or I myself) performed the git actions described above.
The latter is probably the more critical gap in Paseo right now; even if after merging a PR I manually/agentically move the worktree to a fresh branch, Paseo's Git workflow button will remain stuck on "Archive workspace", and not allow me to make more commits, push, or open a PR. The behavior I'd love to see here is that Paseo picks up that the worktree's branch is no longer linked to the previous PR the workspace was tracking, and let me stay in that loop. The cherry on top would be an additional "Continue workspace" action in the workflow management dropdown as an alternative to "Archive workspace".
I'd be more than happy to contribute a PR for these, just wanted to check in first.
Either way, huge thanks for your work on Paseo!
Hendrik
All reactions