How do I do multiple worktrees within an SSH host?

[bpmct]

I connected to an SSH host and I'm doing things, but it seems like when I press "new chat" it does a local copy or establishes a new ssh connection. It's kind of confusing compared to the worktrees mode. I mean it gives me these nice folders ~/mux/cmux/coder but it's just all a bit strange

[ammario]

Yeah the SSH remote does a local copy to the remote each time. But it also fast-forwards the repo to the origin so any pushed refs should be available to the new workspace.

The main reason we don't use worktrees over SSH is we would have to maintain some kind of "base project" from which worktrees are spawned in the remote host, and there would be additional cognitive overhead for the user in making sure this base project is up-to-date or in sync with the local project.

I like the model where the local project is the "base" and everything else is spawned from it, regardless of runtime.

[ibetitsmike]

The way it works right now is the correct one. We don't need to overcomplicate this one.

[ammario]

Today I merged a change that makes SSH workspaces use worktrees (in a backwards compatible way) in order to speed up forks.