You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and then close the window that opens (eg say `"window close"`). This step is necessary to create the [VSCode settings profile](https://code.visualstudio.com/updates/v1_72#_settings-profiles) that acts as a sandbox containing a specific set of VSCode extensions that will be run alongside Cursorless when you launch Cursorless in debug or test mode. Once https://github.com/microsoft/vscode/issues/172046 is resolved, we will be able to remove this step, as the profile can then automatically be created.
45
41
46
42
5. Run the following in the terminal:
47
43
48
44
<TabsgroupId="vsx">
49
-
<TabItemvalue="vscode"label="VSCode">
50
-
```bash
51
-
pnpm init-vscode-sandbox
52
-
```
53
-
</TabItem>
54
-
<TabItemvalue="vscodium"label="VSCodium">
55
-
```bash
56
-
pnpm init-vscode-sandbox --codium
57
-
```
58
-
VSCodium users will also need to manually download and install the `jrieken:vscode-tree-sitter-query` extension, as it is [currently not avalible](https://github.com/jrieken/vscode-tree-sitter-query/issues/28) on the OpenVSX Marketplace.
59
-
Instructions on how to manually download the extension can be found [in this Stack Overflow post](https://stackoverflow.com/a/79565372) ([archived](https://web.archive.org/web/20250421130639/https://stackoverflow.com/questions/79359919/how-can-i-manually-download-vsix-files-now-that-the-vs-code-marketplace-no-long/79565372#79565372)), while manual installation instructions can be found directly below—replace `some.extension` with the acquired `.vsix` file's path instead of an extension id.
60
-
</TabItem>
45
+
<TabItemvalue="vscode"label="VSCode">
46
+
```bash pnpm init-vscode-sandbox ```
47
+
</TabItem>
48
+
<TabItemvalue="vscodium"label="VSCodium">
49
+
```bash pnpm init-vscode-sandbox --codium ``` VSCodium users will also
50
+
need to manually download and install the
51
+
`jrieken:vscode-tree-sitter-query` extension, as it is [currently not
while manual installation instructions can be found directly
58
+
below—replace `some.extension` with the acquired `.vsix` file's path
59
+
instead of an extension id.
60
+
</TabItem>
61
61
</Tabs>
62
62
63
63
Said command adds extensions to the aforementioned settings profile that acts as a sandbox containing a specific set of VSCode extensions that will be run alongside Cursorless when you launch Cursorless in debug or test mode. This approach is [suggested](https://code.visualstudio.com/updates/v1_72#_extension-debugging-in-a-clean-environment) by the VSCode documentation. If you need to update any of the extension dependencies in the sandbox, you can add `--force` to the command. If you'd like to use additional extensions when debugging locally, you can use the following command:
0 commit comments