Patches PR following the 2025-08-25 Evil Dev Stream test!

[KTrain5169]

@KTrain5169's list:

Functional changes

• When switching files by a human, context isn't sent, this is a bit of a problem for "student-pilot" as vedal switching files may not be made clear to the twins & they don't get a refresh on the file's contents (Implemented in fb4aa2c)
• Evil tries to input position parameters in insert text instead of moving the cursor first and then inserting text, this should be allowed and all schemas must now have additionalProperties: false for the schema lib (unless we just add a custom check for that at RCE instead of back-adding that to every schema) (Implemented in b942e11 (position parameters) and 8354ef6 (additionalProperties))
• A different option for regex text should be available as an option for replace/delete - Glob patterns probably weren't tried during stream. Probably should've realised that much earlier but oh well.
• Range options should be specifiable for replace/delete (Implemented in b0d0cb8)
  • This should be used to limit the range to replace and delete text.
• actually while we're at it the cursor should also have the ability to highlight like clicking and dragging text like a range (Implemented in df8dbbb)

Config/context changes

• CNAME shouldn't be neuro-safe by default (currently is because it doesn't start with a dot and lives at root, not a subfolder)
• perhaps should be made clear to evil that binary files like .png are gibberish (is there even a way to tell if a file is binary without trying to parse it?) (Implemented in 8e812ad)

@Pasu4's list:

General changes

• Specify to use newlines and indentation appropriately for insert_text. (Implemented in 5a8cd5d)
• The user should be able to disable specific actions by name. (Implemented in c2644db)
  • VS Code settings UI might get a bit messy if this was implemented, so something like .neuropilot/ #51 and/or a sidebar to contain toggles should be used here instead. @KTrain5169 learned something new and that was array schemas for extension settings.
• The entire file should be sent as context. (Kinda implemented in dbe0f3d)
  • Maybe a max length failsafe would be good in case she does something with regex replace again, but what should happen in that case?
• If an action moves the cursor, it should be mentioned in its description. (Implemented in 8151bb7)
• Show Neuro's last edit using text decorations. (Implemented in 41f8f67)
  • We could use jonTrent/PatienceDiff for this (licensed under The Unlicense)

New actions

• get_content: Get the content of the current file. (Implemented in a2f4fcc)
  • Under the hood, this should just execute the Send Current File as Context command, or use the same code.
• insert_lines: Insert lines of code below the specified line. (Fully implemented in 269136b)
  • Would this be using arrays or \n characters in the action object?
• rewrite_lines: Rewrite everything in the specified line range. (Implemented in Add rewrite_lines action and implement character limit validation #94)
• delete_lines: Delete everything in the specified line range. (Implemented in Add delete_lines action & update replace_lines cursor behavior to be in line with the other actions #95)
• rewrite_all: Rewrite the entire contents of the file. (Implemented in Rewrite all action #93)
• read_file: Send the contents of a file as context without opening / switching to it. (Implemented in 9229cb0)
  • Evil wanted to "look at the placeholders for motivation while i do the css" at one point
  • Not sure if that's possible with the VS Code API but I'll (@Pasu4) look into it

Issues to also resolve with this branch:

• Add a changelog #89 - Add a changelog (in progress by @KTrain5169, test implementation on the dev branch)
  • We can use the changesets package for this.
    • See this discussion for tips on how to set it up with VS Code extension development.

[KTrain5169]

@Pasu4 I'm currently working on adding the position parameters for the editing actions. If you're going to continue making it (probably better rn), my suggestion is to refactor the schema object so that position parameters are deduplicated from the move cursor action and insert text action. Also, parameters should be a separate object inside the schema so that we can mark both line & column as required, but not if she doesn't input position params (unless we don't want to make both required at once and instead just default to cursor, I think I discussed this on Neurocord but I'm not entirely sure if that's a good idea now)

[Pasu4]

Also, parameters should be a separate object inside the schema so that we can mark both line & column as required, but not if she doesn't input position params

Probably better than my current (uncommitted) implementation, so I'll leave this to you if you're already on it. Also, additionalProperties isn't recursive so you need to add it to the inner object (just saying this in case you didn't know).

VS Code settings UI might get a bit messy if this was implemented, so something like #51 and/or a sidebar to contain toggles should be used here instead.

I was more thinking of a string list setting of disabled action names, I don't think that would get messy. I'll try it tomorrow to see if it's really that bad.

[KTrain5169]

Also, additionalProperties isn't recursive so you need to add it to the inner object (just saying this in case you didn't know).

No I remembered earlier today, but I did forget yesterday. I'll make sure to add that to my commits.

I was more thinking of a string list setting of disabled action names, I don't think that would get messy. I'll try it tomorrow to see if it's really that bad.

String lists with \n are something I want to avoid simply because it's not typo-proof, at least with .neuropilot/ we can add a schema that says "hey by the way, this is a non-existent action" but I'll leave that up to you.

[changeset-bot]

🦋 Changeset detected

Latest commit: 7f33ad6

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[KTrain5169]

@Pasu4 I did a bit of looking for you regarding the read_file action, you can read a file, get its Uint8Array value, and parse it using Buffer.from(fileData).toString('utf8');. I've already done the binary file validator (which uses the same sort of logic but looks at the Uint8Array value directly), so you can use that to validate that she isn't going to get a load of binary rubbish first.

I don't think there's a simpler way unless the text editor is already open.