/dev/null
Sign in

Commit

de8b287

Nik Spyratos@nikspyratos
What do you use for multi-agent work in a repo to manage environments? Main challenge I've found with wanting to set up something like Polyscope or Jetbrains Air is that they focus on worktrees for agent parallelization, but some projects have lengthy setup times just for…
  • Worktrees (full environment setup)50%, 1 vote
  • Worktrees (minimal setup just for writing code)0%, 0 votes
  • Separate copies of the repo0%, 0 votes
  • Yolo agents on lots of work in the same checkout50%, 1 vote

2 votesFinal results

Bernardo@bhulsman
Tried worktrees, but that became a mess pretty quickly. I've been using Ampcode for a but, which just does it as a seperate copy I think? With option to merge/rebase/etc. Not gotten to the point of multiple changes conflicting though. So far locally it's not been possible (for…
Nik Spyratos@nikspyratos
I've had Claude figure out and use worktrees by itself sometimes, but otherwise I made a point to retrofit the local dev env to support multiple checkouts on the same host (no db/cache/etc service conflicts). But I agree it feels messy, I don't get the hype if your project isn't made of literally only unit tests.

commit de8b287