“Current challenge is that all 50 want to run type checks and that just melted my machine immediately, thankfully I was able to change to tsrs drop-in and impose a collaborative queue.”

The contention that bites first here is not files but shared compute: "most time is waiting for inference results. The cost is entirely on builds and tests and tooling." His answer is a dedicated agent staffed to take "type check requests" off a queue, i.e. a shared resource gets a broker. Also a counter-position to worktree-by-default: he argues worktrees waste disk and resources and make collaboration worse, and prefers one shared checkout with a strong collaboration toolkit. A reply from Hudson Griffith (@useprized) pitches one big cloud box so all sessions share the checkout and the 32 vCPU type-check budget. Single-source, self-reported, no numbers beyond '50 sessions, ~8h'.