mozilla/sccache

You should have set up https://github.com/mozilla/sccache at minimum. Setting up compiler caching is routine for people coming from older compiled language backgrounds but it's often missed by people coming from languages like JS/TS who have never been exposed to these ideas. There's a new project called kache https://github.com/kunobi-ninja/kache that takes this even further and handles more edge cases with worktrees, but it's newer. If you were pulling the entire project fresh and rebuilding everything in every worktree all the time without any caching then it would be frustrating. You could have asked your agent to set up basic caching and solved most of your problem in minutes.

Most of that time was probably compiling dependencies. If you give it another go, I would recommend a shared sccache. https://github.com/mozilla/sccache

…he relevant version of the relevant module to the project tree. This will save a lot of space when multiple worktrees are used. In the python ecosystem, only conda[2] seems to provide this ability. The sccache project [3] provides similar advantages to C, C++, Rust and CUDA projects. It caches the binary artifacts of compilation, so that can be used to speed up even first compilation of projects. By default, these caches can be shared between different projects on the same system. But with networked storage backends, sccache can be used to share build artifacts across a network and even enable parallel builds on multiple builds. (Added: Cargo seems to globally cache sources and deal with i…