Use --command flag executable for VSCode extension sync in mila code

[Copilot]

When mila code syncs VSCode extensions to a remote cluster, it was hard-coded to use code as the local executable regardless of the --command flag value. Users running code-insiders or a custom binary would have their extensions listed/installed using the wrong executable.

Changes

• vscode_utils.py: Thread a new code_command: str | None = None parameter through:
  • sync_vscode_extensions → _get_vscode_extensions (for reading source extensions)
  • sync_vscode_extensions → _install_vscode_extensions_task_function (for installing to LocalV2 destinations)
  • Both ultimately pass code_command to _get_local_vscode_executable_path(), which already accepted it
• code.py: Pass command (from --command flag) into sync_vscode_extensions as code_command

All new parameters default to None (falls back to get_code_command() / $MILATOOLS_CODE_COMMAND), preserving backward compatibility.

# Before: always used "code" (or $MILATOOLS_CODE_COMMAND) regardless of --command
sync_vscode_extensions(LocalV2(), [login_node])

# After: uses the executable specified via --command
sync_vscode_extensions(LocalV2(), [login_node], code_command=command)

Original prompt

in mila code, also use the executable from the --command flag to install vscode extensions. currently it is hard-coded to be code.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.