v2.1.0 changes

.github/workflows/build.yml

@@ -109,7 +109,7 @@ jobs:
                 elif [ "${{ inputs.checked }}" = "false" ]; then
                   export PUBLIC_NEXT=true
                 fi
-                PUBLIC_VERSION=$(npm show ./ version) pnpm build
+                PUBLIC_CLIENT_VERSION=$(npm show ./ version) pnpm build
 
             - name: Upload GitHub Pages Artifact
               uses: actions/upload-pages-artifact@2d163be3ddce01512f3eea7ac5b7023b5d643ce1 # Pinning to SHA because that thing hasn't updated in a year it seems

src/components/Footer.astro

@@ -60,7 +60,7 @@ if (currentPath !== import.meta.env.BASE_URL + "/") {
     {
     currentTopic === "ui"
         ?
-    <a href={`https://github.com/VSC-NeuroPilot/neuropilot/tree/${clientVersion}`}>The tag's commit can be found here.</a> <Icon name="github" class="inline-icon" />
+    clientVersion ? <a href={`https://github.com/VSC-NeuroPilot/neuropilot/tree/${clientVersion}`}>The tag's commit can be found here.</a> <Icon name="github" class="inline-icon" /> : ""
         :
     currentTopic === "containers"
         ?

src/content/docs/client/guides/sandboxing.mdx

@@ -52,7 +52,7 @@ If you're comfortable with not having internet access in the VM, you can stay in
 
 4. On your host machine, open your console and run `ipconfig /all` (Windows) or `ip a` (macOS/Linux).
 
-5. Take note of the IP listed there. If you're on Windows and ran `ipconfig /all`, note down the IPv4 address that has `(Preferred)` next to it.
+5. Take note of the IP listed there. If you're on Windows and ran `ipconfig /all`, note down the IPv4 address for the VirtualBox network adapter.
 
 6. Start your Neuro API server on that address. If you're using one of the testing tools on the official API repo's README, you should be able to pass a CLI flag to spawn it on a certain host. If you're Vedal and you're using Neuro, uhhh good luck :thumbsup:
 
@@ -66,12 +66,12 @@ If you're comfortable with not having internet access in the VM, you can stay in
 
 ## Web environment
 
-As of v2.2.0, NeuroPilot now has a separate Web build. It acts partially the same as the desktop mode, but loses access to certain features that cannot be ran in the Web environment.
+As of v2.1.0, NeuroPilot now has a separate Web build. It acts partially the same as the desktop mode, but loses access to certain features that cannot be ran in the Web environment.
 
 This includes:
 
 - Terminals & tasks
-- Git access (it *is* activated in certain situations, but debugging this in a test environment is impossible and also it functions slightly differently, therefore, for stability, it has been disabled.)
+- Git access (the dependency extension *is* activated in certain situations, but debugging this in a test environment is impossible and it also functions slightly differently, therefore, for stability, it has been disabled.)
 - Copilot Chat window & inline completions (dependency extension can't be ran in the web environment)
 
 To use the web version, go to [vscode.dev](https://vscode.dev) (or any web build of VS Code, such as `github.dev`), and install NeuroPilot.

src/content/docs/client/guides/setup.mdx

@@ -86,7 +86,7 @@ export const DEV_STREAM_TERMINAL_SETTINGS = `{
     "neuropilot.permission.rename": "Copilot",
     "neuropilot.permission.runTasks": "Copilot",
     "neuropilot.permission.terminalAccess": "Copilot", // You can approve/deny the command she wants to run
-    "neuropilot.requestExpiryTimeout": 60000, // Extra time to contemplate (set to 0 for infinite time)
+    "neuropilot.requestExpiryTimeout": 60000, // Extra time to contemplate your choices (set to 0 for infinite time)
     "neuropilot.sendNewLintingProblemsOn": "inCurrentFile",
     // Modify / add terminals depending on what you want her to be able to use
     "neuropilot.terminals": [
@@ -165,23 +165,23 @@ export const TERMINAL_ACCESS_SETTINGS = `{
 }`
 
 <Tabs>
-    <TabItem label="Dev Stream">
+    <TabItem label="Basic Dev Stream">
         Meant for coding together with Vedal.
         Basically what we already saw on the dev stream, plus a few Copilot-mode permissions.
         <Code code={DEV_STREAM_SETTINGS} title='.vscode/settings.json' lang="json" />
     </TabItem>
-    <TabItem label="Chill Stream">
+    <TabItem label="Solo/Chill Stream">
         Meant for coding without supervision.
         Enables basic Git commands.
         <Code code={CHILL_STREAM_SETTINGS} title='.vscode/settings.json' lang="json" />
     </TabItem>
-    <TabItem label="Dev Stream (Limited terminal access)">
+    <TabItem label="Dev Stream w/ limited terminal access">
         Meant for coding together with Vedal.
         This will additionally give Neuro access to the terminal, but you can approve/deny every command she wants to run.
         Still, **be careful with this.**
         <Code code={DEV_STREAM_TERMINAL_SETTINGS} title='.vscode/settings.json' lang="json" />
     </TabItem>
-    <TabItem label="Full terminal access">
+    <TabItem label="System takeover themed stream">
         Meant for watching Neuro delete System32.
         This gives Neuro permission to run all actions (including terminal access) and disables all safety features.
         <Aside type='danger'>Only use this on a (virtual) machine you're not afraid to lose.</Aside>

src/content/docs/client/reference/features/file-actions.mdx

@@ -16,11 +16,13 @@ export const attribs = {
 
 <CenterIcon Icon={NeuroFiles} credits="File actions icon by KTrain5369" attribs={attribs} />
 
-## Get/open workspace files
+## Get/open/read workspace files
 
 Neuro can get or open files within the workspace. This will either get the list of Neuro-safe files in the workspace, or open files as specified (assuming the path is Neuro-safe).
 If a file is already opened, its tab will be focused.
 
+Reading a file (using `read_file`) will not open the file in the editor or reveal Neuro's cursor position in that file (if there was one already).
+
 When opening a file, Neuro will be sent the current file as well as her cursor position.
 
 ## Create/Delete/Rename files and folders