[nullbio]

One thing I don't understand with all of these, is how they're handling different worktree infrastructure spin-up?

For example, if I have a webapp, I want each of the worktrees to spin up its own infrastructure, and be accessible on its own unique local url, so that I can see the changes locally for each worktree, or I can have agents automate visual checks using something like agent-browser.

Currently I use docker for my infrastructure, each service running in its own container. I have a script that has a ./app worktree create worktreename. That creates a worktree as "worktreename" and spins up all of my docker infrastructure with prefixes for things like "WORKTREENAME", and I can access all my urls at worktreename.myapp.test (or just myapp.test for the main worktree).

This is working fine for now, but it'd be cool if one of these apps was compatible with this concept so I could move over to that.

[dbbk]

You just enter a setup script that it runs on worktree creation

[igor47]

"just" is doing a lot of heavy lifting here. I always automate my repo setup, usually with mise tasks, but there's often assumptions baked in, eg around which ports the app will listen on. It's also still hard to get the agents to use "mise run test" instead of invoking pytest directly. This sounds harder to deal with when you have multiple copies of the test or dev stack running together on the same machine.

[dbbk]

I mean I'm not sure what your issue is. There has to be a setup script of some kind. What are you saying, that your setup script is too... dynamic?

[sharts]

this is not hard