We’re planning to build a VS Code plugin for our tool, and our proposed structure is as follows:

1. We currently have a command-line CLI written in Go, which we’ve provided to our developers and is functioning well.
2. Since we primarily use VS Code for development, we’ve decided to create a VS Code 3. plugin to enhance our development workflow.
3. As VS Code extensions are developed in TypeScript, we prefer not to rewrite our Go logic entirely. Instead, we plan to integrate our Go CLI within the VS Code extension, executing commands through the CLI.
4. Our extension will perform extensive file processing, as it’s intended to be a development tool.
5. The extension’s launch process includes the following steps:
   *. Clone the code from an open-source Git repository into a designated folder under
   the ./vscode plugin directory.
   *. Build the Go binary.
   *. Open the cloned repository in a new window with the extension active, allowing users to explore the extension’s features. Each time the plugin is launched, it will perform these steps.

I have a few questions:

1. Does this design approach seem appropriate?
2. Is there a more efficient or better way to handle this?