This gate was the script's entry point and the only place CLAUDE_CODE_REMOTE was checked. When set, the full bootstrap ran (nvm install, node version enforcement, npm ci with stamp caching, PATH persistence). When unset (local Claude), the script no-op'd. Removing this means remote Claude sessions that previously had automatic environment provisioning now have no bootstrap at all — unless something outside this repo has taken over.
The run_npm fallback chain ends in an unauthenticated npm call when NPM_TOKEN is absent, 1Password is unavailable or fails, and the shell has no npm alias/function. That final fallback carries no error of its own — it just runs npm and lets whatever happens happen. Removing the script removes this silent-failure path along with it, which is a net win for legibility. The flip side: if private npm installs were working through one of the earlier fallback branches, removing the script also removes the auth bridging that made them work.
npm
The PR has been open 5 days with only bot reviews — mendral, coderabbit, nx-cloud, and the batch-change tool. A 216-line deletion of an environment bootstrap that gates on remote sessions has no human sign-off in the thread. That's a process smell, not a code smell, and outside the scope of what I can usefully say here.
What replaced the remote-session bootstrap? setup.sh was the environment provisioning path for remote Claude sessions — it installed nvm, enforced exact node/npm versions, bridged npm auth, cached dependency stamps, and persisted the node PATH into CLAUDE_ENV_FILE. The PR description calls these "legacy" but doesn't say what superseded them. If the answer is that remote Claude sessions are no longer used, or that they now get their environment from a Docker image or a different bootstrap mechanism, that context belongs in the description.