⌘K
Anshuman Bhardwaj This is superb! Thanks for sharing the step by step guide here 
Can't wait to try
Jonoroboto Tell us how you get on. One thing we haven’t figured out yet, *that I would love to solve*, is agent orchestration ***with*** git worktrees and how best to fire something off like that in one go. Think a *less* destructive Gastown, that you’d be comfortable throwing at a production repo. This is a simplified workflow, but should give you the idea.
dan-lee Running into the same issue. With corepack enabled, I'd have expected Vercel to pick up the pinned pnpm version automatically.
Holmlab Developer Setting `ENABLE_EXPERIMENTAL_COREPACK=1` env var in Vercel UI worked for me.
dan-lee Edit: Ok weird, in another project it seems to work just fine 🤨 Edit 2: **Found the issue**: It's a monorepo that had a sub-package that defined a pnpm@10 version. The error message picked up the root `package.json` hence my confusion. [details="Error message"] Are you sure? This is what I see: ```bash > Detected ENABLE_EXPERIMENTAL_COREPACK=1 and "pnpm@11.6.0" in package.json Running "install" command: `pnpm install`... ! Corepack is about to download https://registry.npmjs.org/pnpm/-/pnpm-10.10.0.tgz ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version) Your pnpm version is incompatible with "/vercel/path0". Expected version: >=11 Got: 10.10.0 ``` [/details]